jiUdZddlmZddlZddlZddlZddlZddlmZddl m Z m Z m Z m Z mZmZgdZdZdZd Zd Zd d d d d gd Zded<GddeZddddXdZdYdZdZd[dZd\d Zd]d^d$Zd%Zd_d)Zd`d,Z dZdad-Z!d.Z"d/Z#dbd1Z$dcd2Z%ddd5Z&ded7Z'd8Z(dfd;Z)dgd?Z*e ee+ege,fZ- dZdddddd@dhdGZ.didNZ/dOZ0djdQZ1dkdRZ2dldSZ3dZddTdmdUZ4e5dVkr!e6e.ej7dWddS)naThe pre-push policy, once, for every repository that pins this package. Written for three repositories - `invisible_core`, `invisible_playwright` and `invisible_firefox`. The last was deleted on 2026-08-18; the design and the history below are unchanged by that, because the module was already indifferent to how many repositories use it - see WHY HERE below. WHY. The three `.githooks/pre-push` files were 743 lines of shell between them, and 207 of 211 comparable lines were byte-identical between two of them. Measured 2026-07-27: eleven behavioural differences separated the three, and nine were accidental - the signature of copy-paste, where each fix lands in whichever file happened to be open: * `invisible_core` ran no pytest at all, so the one repository the other two depend on was the only one where "never push red" was not enforced. It is also the repository that pushed red (56b2af2, fourteen tests red on main for two hours). CLAUDE.md hard rule 3 names this hook as the thing that stops exactly that; * `NAME_SKIPPED` was assigned in three places in the core's hook and read in none, because the closing summary that reads it only exists in the other two; * the core resolved an interpreter into `$python_bin` and then the pasted name-scan block called bare `python` anyway; * three different ways of locating the same two workbench scripts; * the core asked PyPI over curl whether a version existed, which answers a weaker question than the gate's own `--verify-index` (present on the index versus present AND byte-identical) and answers it with a second source of truth. Two differences were real and are preserved as configuration - whether pytest runs is NOT one of them, see below - and the rest are now one implementation. WHY HERE. Same reason `invisible_core.release` lives here: every consumer pins this package exactly, so a module in it is reachable from all of them, whereas a script in one repository is reachable from one. That asymmetry is what left the consumers with no publish gate when 0.4.4 went out built from the wrong tree. WHAT EACH REPOSITORY DECLARES, in its own pyproject under `[tool.invisible.hooks]`: pytest = true|false run the suite before pushing pin = true|false compare the invisible-core pin (consumers) english = true|false refuse Italian prose in a public repository identity = true|false refuse author/committer/tagger addresses that are not GitHub noreply ones (default true) release_tags = ["v"] tag prefixes that mean "this is a release" The block is REQUIRED. A missing one is a refusal rather than a default, because a default here is a policy nobody chose: the wrong one silently skips a gate, and a skipped gate reads exactly like a passed gate. THE ONE DELIBERATE BEHAVIOUR CHANGE. `pytest = true` in the core, which previously ran none. Everything else below preserves what the three hooks already did, including the two decisions that look inconsistent and are not: * a missing PIN checker REFUSES, while a missing NAME word list carries on with a warning. The pin checker is a maintainer tool that must be beside this checkout and its absence means the workbench moved; the word list deliberately lives outside every public repo, so demanding it would leave every clone red by default, which is how gates get switched off. STDIN. git feeds the refs being pushed on stdin, one line per ref, and it can be read exactly once. Two gates need it, and a `while read` in the first of them starved the second silently for a day - the scan reported "no commit messages scanned" on every push, correctly, and with no coverage. It is read once, here. ) annotationsN)Path)CallableDictListOptionalSequenceTuple) main hook_configrelease_tag_in push_rangeforeign_identitiesoutside_the_hookHOOK_LOCATION_VARIABLESGATE_NOTHING_TO_DOHookConfigErrorzsync_core_pin.pyzcheck_forbidden_names.pyzcheck_internal_disclosure.pyTv)pytestpinenglishidentity release_tagsDict[str, object] _DEFAULTSceZdZdZdS)rzEThe repository did not declare a hook policy, so none can be applied.N)__name__ __module__ __qualname____doc__DC:\Projects\Muse2API\.venv\Lib\site-packages\invisible_core/hooks.pyrrusOOOOr#rF)erroutmsgstrr%boolreturnNonecl||n|r tjn tj}td||ddS)Nz [pre-push] T)fileflush)sysstderrstdoutprint)r'r%r&streams r$_sayr4ys@OSS*K#**F   F$777777r#rootrc \t|dz } |d5}tj|}dddn #1swxYwYnL#t$r}t d||d}~wtj$r}t |d||d}~wwxYw|didid}|t |d td |D}|rNt d d |d d ttdtt}| |t|dtr |dg|d<|S)a`[tool.invisible.hooks]` from the repo's pyproject. Raises rather than defaulting when the block is missing: see the module docstring. Individual keys DO default, so adding a gate later does not require touching every repo's pyproject before the first push can happen. zpyproject.tomlrbNzno pyproject.toml at z does not parse: tool invisiblehooksa- has no [tool.invisible.hooks] block, so this hook does not know which gates this repository wants. Declare it - pytest / pin / english / identity / release_tags - rather than letting a default decide, because the wrong default silently skips a gate and a skipped gate reads exactly like a passed one.c3,K|]}|tv |VdSN)r).0ks r$ zhook_config..s,??1AY,>,>Q,>,>,>,>??r#z [tool.invisible.hooks] declares , z#, which nothing reads. Known keys: zB. A misspelt key is a gate whose author believes it is configured.r)ropentomllibloadFileNotFoundErrorrTOMLDecodeErrorgetsortedjoinrdictupdate isinstancer()r5 pyprojectfhdataexcdeclaredunknowncfgs r$r r ~s6T --IM ^^D ! ! $R<##D $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ LLLAiAABBK  "MMMBBSBBCCLMxx##'' R88<> >???????G O  Ntyy/A/A N N*.))F94E4E*F*F N N NOO O y//CJJx#n%s++4">23N JsEAA  A AAAA B A33BBBc||n tj} ||rdS|S#t$rYdSwxYw)zThe refs git is pushing, or "" when the hook is run by hand. Guarded on a tty so invoking it manually does not hang on input that will never arrive. N)r/stdinisattyread Exception)rUr3s r$read_push_refsrYs_ 'UUSYF >V]]__>2{{}} rrs>> A  A  push_refsc#K|D]W}|}t|dkr*|dd\}}}}|rt|dhkrP|||fVXdS)z(local_sha, remote_ref, remote_sha) per pushed ref, deletions dropped. An all-zero LOCAL sha is a branch or tag deletion: it pushes no content, so there is nothing to scan and nothing to publish. N0) splitlinessplitlenset)rZlineparts _local_ref local_sha remote_ref remote_shas r$ _ref_linesrhs $$&&00  u::>> 8=bqb 5 Iz:  YC500 Z/////00r#rprefixes Sequence[str]cxt|D])\}}}|D] }|d|r|ccS!*dS)z*The first release tag being pushed, or "". refs/tags/rT)rh startswith)rZrj _local_sharf _remote_shaprefixs r$r r sq/9)/D/D""+ J  " "F$$%:&%:%:;; "!!!!!! " " 2r#(4b825dc642cb6eb9a060e54bf8d69288fbee4904revrepoOptional[Path]c |dS tjddt|ddd|gddd}n#t$rYdSwxYw|jd kS) NFgit-C rev-parsez--verifyz--quietTcapture_outputtextcheckr) subprocessrunr(rD returncode)rsrtr&s r$_revision_existsrsy |un D#d))[*i Md%999 uu >Q s,3 AArelistc |gS tjddt|d|ddgddd }n#t$rgcYSwxYw|jrgSd |jDS) z>The commits reachable from `local_sha` that no remote has yet.Nrwrxrev-listz--notz --remotesTFrzcg|]}||Sr"r")r=rs r$ z,_commits_not_on_a_remote..s / / /!Q /A / / /r#)r~rr(rDrr1r_)rertr&s r$_commits_not_on_a_remoters | n D#d))ZG[ Qd%999   ~ / /sz'')) / / //s,3 AAct|D]k\}}}|r[t|dhkrGt||}|sdS|d}t|d|r |d|cStd|cS|d|cSdS)aUN intervallo di revisioni valido per `git diff` e `git rev-list`, o "". The return value is always ONE token, and that is the point. It used to return `f"{local_sha} --not --remotes"` when the remote had never seen the ref: three tokens in a single string. Whoever received it had to guess whether to split it, and the two consumers guessed differently - the name scanner survived, while the disclosure gate handed it to `git diff` as a single revision and got `fatal: bad revision`. The hook then REFUSED the push, correctly but for a fault of its own: measured 2026-08-11 pushing the tag v18.14.0, and the consequence was that a release could not start. The case that triggered it is the ordinary one for a tag: the ref is new on the remote (remote sha all zeroes) while the COMMITS are already published. The right answer there is not a strange range, it is "there is nothing new to read", and that is said with "". `repo` is there so this can ask git instead of deducing. Without it the function behaves as it did for the ordinary case and invents nothing: a range it cannot verify is a range it does not return. r]rT^z^....)rhrarr _EMPTY_TREE)rZrtre _remote_refrgnuovi piu_vecchios r$rrs,/9.C.C,,* ;  1#j//cU22,Y==E rr)K; 1 1 1488 6%55)55555 "00Y00 0 0 0++ +++++ 2r#z@users.noreply.github.comznoreply@github.comemailcL|tp |tkSr<)endswith_PUBLIC_EMAIL_SUFFIX_GITHUB_WEB_FLOW)rs r$ _is_publicr+s >>. / / L5rz tagger of )rarhrrr_addstriprchrrappendrrnr^)rZrtfoundseenrerfrgcommitslistedsharbr_seprrolerbodytag_lines r$rr>s])+ED-7 -B-BYY) :z  -#j//cU22.y$??GGdJ:0L0L0L0LMMF|**,,G > >Cd{{ HHSMMMD%/DcJJPbD'+jjll&<& > e>E!2!2>LL#tWU^^!<=== >   . . Y$ D)<<BIIKKuTTD*dI>>D"D OO-- Y Y**955 **3//2<d|DS)z`env` without the variables that tie a process to the hook's repository. What a gate the hook launches is given, so that its git calls address the repositories IT names and never the one git named to the hook. c,i|]\}}|tv||Sr")r)r=r>rs r$ z$outside_the_hook..s) M M MTQA5L,L,LAq,L,L,Lr#)items)rs r$rrzs! N MSYY[[ M M MMr#cmdcwdintc  tjt|t|t t t jjS#t$rYdSwxYw)N)rr) r~rrr(rrIosenvironrrD)rrs r$_subprocess_runrsn~d3iiSXX"24 3C3C"D"DFFFFP Q sssAA A*)A*)r5rZrrpythonargvOptional[Sequence[str]]rOptional[Runner]Optional[Dict[str, str]]rc t||ntj}t | tjn|}|pt }|p |dp tj }|tn|} t|}n,#t$r} td| dYd} ~ dSd} ~ wwxYwg} g} |jjdz } |drjtd ||d dd d g|r5td dtddtdddS| d|dr|d} | dkr%td| dn| rt| n | t z }|s]td dtddtd|dtd|dtdddSt%|d|||dgdd|}|r|S| d|d} | dkr&td| dn>| rt| n | t&z }| r]|sItd dtd dtd|dtd!ddS|s4td"td#| dn|t)||}|rtd$|d%ntd&td't%|d(||||rd)d*|gnd)gdd+}|r|S| d,|d-} | dkr&td.| d/n | rt| n | t*z }| r]|sItd dtd0dtd|dtd1ddS|s4td2td#| d/nHt)||}t%|d3||||rd)d*|gnd)gdd4}|r|S| d5|d6} |d7s| d8n| dkr%td9| d8ndd:lm} |d;t3|g}nu#t4$r0}td dtd<|dYd}~dSd}~wt6$r0} td dtd=| dYd} ~ dSd} ~ wwxYw|r5td dtd>dtd?ddS| d8|d@} |dAs| dAn,| dkr&tdB| dAn|s%tdC| dAnt;||}|rtd dtdDd|ddED](\}}}tdF|ddGdH|dI|d)t=|dEkr%tdJt=|dEz dKdtdLddS| dAt?||dM}|rt|dN||d dOdPt3|dQdRg|}|t@kr%tdS| dTnP|r9td dtdU|dVdtdWddS| dXtdY| rdZ!| nd[z| rd\dZ!| d]nd zd^S)_a-Run the whole pre-push policy. 0 lets the push through, 1 refuses. Every collaborator is injectable so the policy can be exercised without spawning a test suite or touching a network - the gates that were only ever observed printing PASS are the ones that turned out not to be gates. NINVISIBLE_GATE_PYTHON REFUSED - Tr%scriptsrz%running the test suite before push...z-mz-qz --tb=shortrTzTESTS FAILED - push aborted.z{Fix the failure, or `git push --no-verify` if you really know what you are doing (NEVER for a branch that feeds a release).testsrINVISIBLE_PIN_CHECKskipzWARNING: INVISIBLE_PIN_CHECK=skip. The invisible-core pin was NOT compared against the core. If it is stale, every install of this package resolves a core it was never tested against, and nothing downstream can see it.zpin gatez7REFUSED - the invisible-core pin gate is not reachable.z looked for: z from: zThe workbench moved, or this is a clone at another depth. Point INVISIBLE_PIN_CHECK at sync_core_pin.py, or push with INVISIBLE_PIN_CHECK=skip to state on the record that the pin is going out unchecked.--checkzDthe invisible-core pin does not match the core. Fix it with: python )r require_testsfail_msgINVISIBLE_NAME_CHECKzWARNING: INVISIBLE_NAME_CHECK=skip. Nothing checked this push for vendor or target-site names. If one is in the diff it is public the moment this lands, and a force-push does not remove it - GitHub keeps the object reachable by SHA.z name scanz` PR and cannot merge it itself, so an unmerged one blocks the NEXT release, not its own.z publish gatezpush proceeding - r@zNOTHING was checkedz (SKIPPED: )r)"rrgetcwdresolverIrrrFr/ executablerYr rr4parentr _PIN_CHECKERis_file_run_gate_with_its_own_tests _NAME_CHECKERr_DISCLOSURE_CHECKERrTrr r( SystemExit RuntimeErrorrrr`r rrH)rr5rZrrrpyrefsrRrOranskipped workbenchsettingcheckerrcscannerrngrstopforeignrrmaskedrs r$r r s  (bikk : : B B D DD S[rzzc 2 2C C  E377233 Es~B(0>   iD$  #  T****qqqqqCG "Y.I 8} 4555 3D(D,7 > >       /T : : : : Q    1 7 5z!''/00 f   6 7 7 7 NN: & & & &'.Ld7mmmI 4LG ??$$ RT""""NTXYYYY/g//T::::,d,,$777739=>>>>q-D#["3)033 444B   JJu   gg,--G& 9 : : : {#####*I$w--- M0I  7??,,       OUY Z Z Z Z +'++ 6 6 6 6 AFJ L L L L1   R S S S P Q Q Q NN; ' ' ' 'T4((C QIIIIJJJJBCCCPQQQ-T3.1%z"""" F   9 : : :z""""  xT344BB         EtEE4 P P P P11111         NNN    11111          .37 9 9 9 9 16: < < < <1 : gg011G z?z"""" F   H I I I z"""" ZZ\\    z""""$T400         %) + + + +%,SbS\ A A!T65#crc(55T55V554@@@@@7||b  :#g,,"3:::EEEE CHL N N N N1 : s>2 3 3C "'  C C CDDD S"d46FD +-.244 # # # M N N N JJ- . . . .  '      IrIII     )/3 4 4 4 41 JJ~ & & & 3!Q35$D 9D9)-D : : ::r#crt|ddd}|jdkr|jndS)z?This clone's `core.hooksPath`, or "" if unset / not a checkout.configz--getcore.hooksPathrrT)r rr1r)r5ps r$ hooks_pathr s9 T8W&677A |q0018>>   b8r#ct|ddd}tt |t z dd}|t dt |fvS)N\/z./)rreplacerstripr(rHOOKS_DIR_NAME)r5curwanteds r$is_armedrsp T   " "4 - - 4 4S 9 9C dn, - - 5 5dC @ @F >#8#8#8&A AAr#)r5clddl}t||ntj}|dd}|ddd ||}|tz d z }| s!td |d tj dSt|ddjdkr!td |dtj dSt|}t!|rtd|dS|jr`tdtj td|pddttj tdtj dS|rDtd|tj tdtdtj dSt|ddt}|jdkr7td|j tj dSddl} ||j|jz|jz|jzn#t2$rYnwxYwtdttd dS)!aArm this clone. 0 armed or already armed, 1 --check and not armed, 2 broken. Refuses to overwrite a hooksPath somebody else chose: a repo with its own hook framework is not ours to hijack, and replacing it would disarm THEIR gates to arm ours. rNzinstall_hooks.pyzarm this clone's pre-push gate)prog descriptionr store_truez2report only; exit 1 if the hooks are not installed)actionhelpzpre-pushzerror: z does not exist)r-rryz --git-dirz> is not a git checkout, so there are no hooks to install here.z*hooks already installed: core.hooksPath = z6HOOKS NOT INSTALLED: the pre-push gates would not run.z core.hooksPath = z(unset)z , wanted z& fix: python scripts/install_hooks.pyrz'refusing to overwrite core.hooksPath = z. Another hook framework owns this clone. Add zB/pre-push to it by hand rather than letting this script disarm it.rrzerror: git config failed: zcore.hooksPath = z,the pre-push gates are armed for this clone.)argparserrrrArgumentParser add_argument parse_argsrexistsr2r/r0r rrrr}rstatchmodst_modeS_IXUSRS_IXGRPS_IXOTHOSError) rr5r"rrhookrrr's r$ install_mainr/s OOO (bikk : : B B D DD%7,L  N NANN9\LNNN <<  D . : -D ;;== ----CJ????q D+{++6!;; %(Z 1 1 1 1q T  C~~ @3@@AAAq z FSZXXXX OC$49OO~OO:     6SZHHHHq  ===CJOOOO ####), 5 5 5 5q T8-~>>A|q =18>>+;+;==CJOOOOqKKK  499;;&5 Dt|STTTT       .n . ./// 8999 1s9AI>> J  J __main__r)r'r(r%r)r*r+)r5rr*rr<)r*r()rZr()ri)rZr(rjrkr*r()rsr(rtrur*r))rer(rtrur*r)rZr(rtrur*r()rr(r*r))rr(r*r()rtrrr(r*r)rZr(rtrr*r)rrr*r)rrkrrr*r)rrr5rurZrrrrrrrr*r)rrrr(rr(r5rrrrrkrr)rr(r*r)r5rrr(r*r )r5rr*r()r5rr*r))rrr5rur*r)8r! __future__rrr~r/rBpathlibrtypingrrrrr r __all__rrrrr__annotations__rXrr4r rYrhr rrrrrrrrrrrrrr(rrr rrr rrr/rrrr"r#r$r6s@@@B#"""""  BBBBBBBBBBBBBBBB   " " * 5+/t,03% I I IIIIPPPPPiPPP#(T888888 ))))X      0 0 0 0 9      0 0 0 0%%%%%\3(MMMM.... 7777****jNNNN 8C=$', -%){  # $( { { { { { { | ) ) ) ) p:::: 9999 BBBB > +/> > > > > > B z *TT#(122,'' ( ((r#