jyUdZddlmZddlZddlZddlZddlZddlZddl Z ddl Z ddl m Z ddl mZddlmZmZmZdZdZeed eDZd d iZd Zd ZdZejdZdZdZ dZ!dZ"dZ#dZ$ddddZ%Gdde&Z'Gdde&Z(Gdde&Z)d]d"Z*d^d$Z+e d%&Gd'd(Z,e d%&Gd)d*Z-d_d.Z.d`d0Z/dad3Z0da1d4e2d5<dbd6Z3dcd8Z4e d%&Gd9d:Z5ddd<Z6ded>Z7dfd?Z8dgdBZ9iZ:dCe2dD<dhdEZ; didjdKZdiddRdmdTZ?dndVZ@dodXZAdpd\ZBdS)qaThe release seal: the one file that pairs this core with one engine build. seal.json is generated by scripts/make_seal.py in the Firefox source repo's release pipeline, published as a release asset, and copied verbatim into this package by scripts/roll_seal.py. DO NOT EDIT IT BY HAND. Everything downstream is derived from it: the archive names, the cache directory name, the spoofed User-Agent, this package's pip-visible version, and the launch-time engine check. Two facts about real releases shape the schema, both measured off the five published firefox-18 archives on 2026-07-25: * The legs are independent CI builds, so they carry different application.ini BuildIDs (they do agree, and must agree, on Version). The BuildID therefore lives in the PER-ASSET record: a client verifies the leg it actually runs. A single top-level build_id refused every launch that was not on the platform whose leg happened to be copied into it. * The Linux archives ship the juggler UNPACKED at chrome/juggler/ and carry no omni.ja at all (scripts/linux_release.sh tars the pre-package dist/bin layout). Provenance is therefore read from EITHER layout, and a missing omni.ja is never by itself a pass: the marker count is what decides. ) annotationsN) dataclass)Path)DictOptionalTuple))linuxarm64)r x86_64)win32r c# K|] \}}|V dSN).0p_s CC:\Projects\Muse2API\.venv\Lib\site-packages\invisible_core/seal.py r4s&)G)G1!)G)G)G)G)G)G)r r r )r INVISIBLE_SEAL_FILEz.invisible-seal.jsonz^firefox-(\d+)$z$pip install --upgrade invisible-corez,pip install --force-reinstall invisible-core)z.chrome/juggler/content/protocol/PageHandler.jsz(chrome/juggler/content/TargetRegistry.jsz&chrome/juggler/content/content/main.jsz)chrome/juggler/content/content/Runtime.jszchrome/juggler)s stealthfoxs zoom.stealthz firefox.exefirefoxz"Firefox.app/Contents/MacOS/firefox)r r darwinceZdZdZdS) SealErrorzDThe seal itself is missing, unreadable, or of an unsupported schema.N__name__ __module__ __qualname____doc__rrrrrksNNNNrrceZdZdZdS) SealMismatchz7Something asked for a build this core is not sealed to.Nrrrrr"r"osAAAArr"cFeZdZdZdddddfdZeddZxZS)EngineMismatcha[An on-disk engine does not match the seal. Never launch it. The rendered message is for a human reading a traceback. Every caller that shows a SHORT reason instead - the adoption log line, and until its 2026-08-18 deletion the profile manager's status pill - reads `.summary` or `.problems`, never an index into the rendered text. Two of them used to do `args[0].splitlines()[3]`, which lands on the `engine says: Firefox X build Y` line: an observation that reads like a success, not the problem, and one line away from moving again the next time the layout is edited. rNproblemsentryseal_tagmessagestrr'Tuple[str, ...]r(Optional[Path]r)returnNonect|t||_||_||_dSr)super__init__tupler'r(r))selfr*r'r(r) __class__s rr2zEngineMismatch.__init__s: !!!).x    rc8|js[|jrDt|jddnd}|p |jjSt|jdz }|r|jdd|dn |jdS)z5One line, naming the PROBLEM. Safe to render in a UI.rr%z (+z more))r'argsr+ splitlinesstripr5rlen)r4firstrests rsummaryzEngineMismatch.summarys} 4AERC ! %%002215;;===PRE3DN3 34=!!A%7;Q$-"33t3333qAQQr) r*r+r'r,r(r-r)r+r.r/r.r+)rrrr r2propertyr> __classcell__)r5s@rr$r$ss  EG)-r!!!!!!!!RRRXRRRRRrr$machiner+r.cj|pd}|dvrdS|dvrdStd|)Nr%>amd64r r >r aarch64r zunsupported arch: )lowerNotImplementedError)rBms rnormalize_archrIsP BA x   w <7<< = ==r Optional[str]cf ttjS#t$rYdSwxYwr)rI _platformrBrGrrr _host_archrMs@i/11222 tts " 00T)frozencdeZdZUded<ded<ded<ded<ded<ded<ded <d Zded <d S) Assetr+nameplatformarchsha256intsize entry_rel omni_sha256r%build_idN)rrr__annotations__rYrrrrPrPsg IIIMMM IIIKKK IIINNNHrrPceZdZUded<ded<ded<ded<ded<ded<ded <ded <d Zded <ed dZed!dZed!dZed"dZ dddd#dZ d$dZ d%dZ d"dZ dS)&Sealr+tagupstream_version source_commitplaywright_minplaywright_maxzDict[str, Asset]assetsdigestoriginr%build_id_declaredr.rUct|j}|r"t|dndS)adN of the `firefox-N` release this seal pairs with, or 0 for none. 0 means "not a numbered release contract": a local seal (the `python -m invisible_core seal` default tag is "local"), or any tag that is not firefox-N. It NEVER raises, because constants.py evaluates it at import time: the old `int(self.tag.split("-")[1])` turned the escape hatch this package prints in its own refusal text - generate a local seal, export INVISIBLE_SEAL_FILE - into an IndexError on `import invisible_core`. Following our own documented advice broke the package. r7r)RELEASE_TAG_REmatchr]rUgroup)r4rHs r contract_nzSeal.contract_ns8   * *"#*s1771::*rboolcZtt|jS)zTrue when this seal names a published firefox-N release. The tag test, not the assets test: a seal built by --from-tree against a release checkout can be tagged firefox-N and still carry no assets. )rkrgrhr]r4s r is_releasezSeal.is_releases"N((22333rc|j Sr)rbrms ris_localz Seal.is_locals ;rc|tjt}t |dkr|dS|jp |r|dndS)aThe BuildID for THIS host: display, log lines and the cache-dir name. Informational only. Verification never goes through here, because the tree being verified is not always the host's platform; it uses expected_build_ids() with the tree's own platform.  platform_keyrSr7rr%)expected_build_idssysrRrMr;re)r4idss rrYz Seal.build_idsU%%3z+Seal.expected_build_ids..s???qAJ????rNc*g|]}|jk |Sr)rR)rr{rss rr|z+Seal.expected_build_ids..s%HHHqQZ<-G-G-G-G-Grc*g|]}|jk |Sr)rS)rr{rSs rr|z+Seal.expected_build_ids..s @@@14Qrch|] }|j Srryrzs r z*Seal.expected_build_ids..s777AQZ777r)rbrevaluesr3sorted)r4rsrScands same_platexacts `` rrtzSeal.expected_build_idss{ O040FND*,,B N??DK..00???  #HHHHEHHHI &!#@@@@@@@E& %V7777788999rrBrPct|}|t||ffD]=}||jD]}|j|kr|j|kr|ccS>td|jd|d|)Nzseal z has no asset for platform=z arch=) rI EMULATED_LEGSgetrbrrRrSrGr])r4rsrBrSwantr{s r asset_forzSeal.asset_forsg&&=,,lD-ABBC  D|[''))  :--!&D..HHHHH " SDH S S S ST S SUU Urc|jD]}|j|kr |jcSt|}|t d||S)Nzno binary entry for platform )rbrrRrWDEFAULT_ENTRY_RELrrG)r4rsr{rels r entry_rel_forzSeal.entry_rel_for ss##%% # #Az\)){"""*##L11 ;%&Tl&T&TUU U rc|j}|rd|nd}|jrdnd}|jd|j|d|jdd|dS)N build r%z , local sealz (Firefox , seal ))rYrbr]r^rc)r4bidbuildkinds rdescribez Seal.describes~m#&.#B [4rrn822t'<2e22 CRC(2*.222 3r)r.rU)r.rkr?)rsrJrSrJr.r,)rsr+rBr+r.rP)rsr+r.r+)rrrrZrer@rjrnrprYrtrrrrrrr\r\sk HHHKKKKKK    + + +X +444X4X A A AX ACG15::::::0 U U U U 3 3 3 3 3 3rr\rawbytesrdc  tj|d}n(#t$r}t d|d||d}~wwxYwt |dd}|tvrVddtD}d}|tkrd }t d|d |d |d |d t i}|dpi D]\}} | dpd } | st d|d|dt|| d| d| dt | dpd| d| dpd| ||<|dpd } |s| st d|d|dpi} t|d|d|dpd| dpd| dpd|tj||| S)!Nutf-8zseal at z is not valid JSON: schemar, c34K|]}t|VdSr)r+)rss rrz$_parse_seal_bytes..(s(CCSVVCCCCCCrr%a A schema-1 seal carries one BuildID for every platform leg it covers, and those legs are separate CI builds; it cannot be read forward, because the BuildIDs of the other legs are simply not in it. Regenerate it (scripts/make_seal.py, or `python -m invisible_core seal` for a local one).z has schema z, this invisible-core reads .z Upgrade invisible-core: rbrYz: asset a carries no build_id. Since schema 2 the per-asset BuildID is the authority for the launch-time check (the legs this build publishes are separate CI builds, each with its own BuildID), so an asset without one would verify against nothing. Regenerate the seal with scripts/make_seal.py.rRrSrTrVrWrX)rQrRrSrTrVrWrXrYz has neither assets nor a top-level build_id, so there is no BuildID to verify any engine against. Regenerate it with scripts/make_seal.py. playwrightr]r^r_minmax) r]r^r_r`rarbrcrdre)jsonloadsdecode ExceptionrrUrREADABLE_SEAL_SCHEMASjoinSUPPORTED_SEAL_SCHEMACORE_INSTALL_HINTitemsr:rPr\hashlibrT hexdigest) rrddataerreadablewhyrbrQr{rYdeclaredpws r_parse_seal_bytesr!s%Kz#**W--.. KKKB6BBqBBCCJK (A&& ' 'F ***99CC-BCCCCC ) ) )GC  Lv L L6 L L L L L L8I L LMM MFHHX&&,"3355   aEE*%%+2244 *)6))4)))** * * AfIakQUU6]]'a((AkNm,,2X   t $$*1133H _(_ ^v ^ ^ ^__ _ ,   %2B  K$/A*Bhh//52vve}}*266%==;NBgnS11;;==f"    s'* AA  ArcPttdS)Nz seal.json)r__file__ with_namerrrpackaged_seal_pathrQs >> # #K 0 00rpath'str | os.PathLike[str]'c t|} |}n0#t$r#}td|d|dt|d}~wwxYwt |t |S)Nz cannot read the release seal at z: z<. A packaged invisible-core always ships one; reinstall it: )r read_bytesOSErrorrCORE_REINSTALL_HINTrr+)rrrrs r load_sealrUs T AFllnn FFF >q > >A > >(; > >??DE FF S#a&& ) ))s& AAAOptional[Seal]_ACTIVEc <ttjt}|rLt |}t d|dtd|dtj nt t}|atS)aThe seal this process runs under. Resolved once, at first use. INVISIBLE_SEAL_FILE substitutes a different seal. It is NOT an off switch: the substituted seal drives the User-Agent too, so the claim always moves with the engine. It always announces itself on stderr. Nz,invisible-core: substituted seal in effect: z [=])file) rosenvironr SEAL_FILE_ENVrprintrrustderrr)overriders r active_sealrcs:>>-00  0(##A 222#22&.2228;  D D D D D,..//A Nrr/c dadSr)rrrr_reset_active_seal_for_testsrws GGGrcxeZdZUded<ded<ded<ded<ded<ded<d ed <d ed <d ed<dZded<dS)EngineIdentityrr(rootrJversionrY milestoneplatform_build_idrkjuggler_presentrUmarked_entriesr,notesnoner+juggler_layoutN)rrrrZrrrrrr~sKKKJJJ$$$$!N      rrr(ct|}|j}|jdkr&|jdz r |jdz S|S)asDirectory holding application.ini / platform.ini / omni.ja for `entry`. Flat next to the executable on win32 and linux; Contents/Resources on darwin (browser/installer/Makefile.in sets RESPATH to the Resources dir only for cocoa). Derived from the executable we were handed, so it works for an arbitrary binary_path= tree, not just our cache layout. MacOS Resources)rparentrQis_dir)r(rrs r resource_rootrsM U A XF {g6=;#>"F"F"H"H}{** MrDict[str, Dict[str, str]]cBi}d} |dd}n#t$r|cYSwxYw|D]}|}|r |ddvr#|drH|dr3|d d }||id |vrV|d \}}}|||i|<|S) Nr%rreplace)encodingerrorsrz;#[rr7r) read_textrr9r: startswithendswith setdefault partition) routsecttextrlinekrvs r _parse_inirs.%'C D~~wy~AA    < <yy{{ tAw$  ??3   DMM#$6$6 ":##%%D NN4 $ $ $  $;;nnS))GAq!23''))CNN4 $ $QWWYY / Js  --ct|}|jdkrdS|jjdkr|jjjdkrdS|jdkrdSdS) a"Which platform's leg this tree is, read off the executable we were handed. Needed because the BuildID now lives per leg: verifying a tree means comparing it against ITS leg, which is not always the host's (the release gate checks a Linux tarball from a Windows workbench). z.exer rContentsrrr N)rsuffixrFrrQ)r(rs r_platform_key_for_entryrsg U Ax~~6!!wx}AHO$8J$F$Fxvw 4rrTuple[str, bool, int, list]c g}|dz }|r tj|5 t }t d|D}d}t D], |vr&t fdtDr|dz }- dddn #1swxYwYd|||fS#t$r) | d ddd d|fcYd Sd wwxYw|d z d z }| rd}d}t D]b |t z n#t$rY4wxYw|dz }t fd tDr|dz }c|dkp+t d |dD}d|||fS| dtd|dd d|fS)at(layout, juggler_present, marked_entries, notes) for a tree. Two shipped layouts, one marker semantic. Windows and macOS pack the juggler into omni.ja; the Linux archives ship it loose under the tree root and carry no omni.ja at all. Either way the answer is "how many of the four known entries carry a stealth marker", and no absence is ever a pass. omni.jac3PK|]!}|tdzV"dS)/N)rJUGGLER_DIR_REL)rns rrz+_read_juggler_provenance..s3QQaall?S+@AAQQQQQQrrc3FK|]}|vVdSr)read)rrHrzfs rrz+_read_juggler_provenance..s1)S)Sa!rwwqzz/)S)S)S)S)S)Srr7Nzomni.ja unreadable (rFchromejugglerc3 K|]}|vV dSrr)rrHblobs rrz+_read_juggler_provenance..s'6619666666rc3>K|]}|VdSr)is_file)rrs rrz+_read_juggler_provenance..s*"H"H1199;;"H"H"H"H"H"Hr*loosezno omni.ja and no z/ directory in r)existszipfileZipFilesetnamelistanyJUGGLER_ENTRIESJUGGLER_MARKERSrappendrrrrrglobr) rromninamespresentmarkedjdirfoundrrrs @@@r_read_juggler_provenancersE ) D {{}} 0 0&& $"BKKMM**QQ5QQQQQ($$AEzzc)S)S)S)S)S?)S)S)S&S&Sz! $  $ $ $ $ $ $ $ $ $ $ $ $ $ $ $w6 6 0 0 0 LL4444 5 5 5ua/ / / / / / / 0 (?Y &D {{}} 1   A tAww2244     QJE6666o66666 ! !)Hs"H"H 3"H"H"HHH&%00 LLLoLLdLLMMM E1e $$sSCA1B2& C2B66C9B6:C C6 C1+C61C6#$E EEzDict[tuple, EngineIdentity] _IDENT_CACHEc t|} |}n3#t$r&}td|d|dd|d|df|d}~wwxYwt ||j|jf}t|}||St|}g}t|dz }t|dz } |s| d || s| d |t|\} } } } | | t|||d id |d id | did| did | | t||  }|t|<|S)zWhat the engine says about itself. One ini read plus one zip central directory read (measured 7-12 ms warm on Windows), memoized per process.zno executable at zC (nothing to verify: the path does not exist or is not readable: rz ()r'r(Napplication.ini platform.inizno readable application.ini in zno readable platform.ini in AppVersionBuildIDBuild Milestone) r(rrrYrrrrrr)rstatrr$r+ st_mtime_nsst_sizerrrrrrextendrr3)r(rstrkeyhitrrappplatlayoutrrjnotesidents rread_engine_identityr0s6 U A@ VVXX @@@ V V VQR V V V3!33q3335Q@@@ @@ q662>2: .C   3  C    D E T-- . .C d^+ , ,D ? =t==>>> < :D::;;;.Ft.L.L+FOVV LL dr""&&y11##'' 22((7B''++K88((7B//33I>>'Ell6   EL Ls& A!AAr/sealassetOptional[Asset]r,c||jr|jfSt|jp tj}||S)aBThe BuildIDs `seal` accepts for the tree `ident` describes. Exact when the caller already knows which leg it fetched (every download, adoption and status route does, and passes it). Otherwise resolved from the tree's OWN platform, read off the executable. Deliberately not narrowed by the host's arch: the tree's arch is not knowable from the files being read, and narrowing by the host's would make the same tree verify differently on different machines. The exact-leg answer is available wherever the arch is actually known, through `asset`. N)rs)rYrr(rurRrt)r/r1r2plat_keys rexpected_build_ids_forr6sI U^  &u{33Cs|H  " " " 9 99rlabelgotexpectedc|r||vrdSt|dkr|dndd|z}|d|d|S)Nr7rzone of rz BuildID  != )r;r)r7r8r9rs r_build_id_problemr<-sa shth--1,,8A;;)dii>Q>Q2QD / /c / / / //rlistc  t|j}|j|jkr%|d|jd|jt |||}t d|j|}|r|||j5|j|jkr%|d|jd|j|j -t d|j |}|r||dddd  |j d |j d }|j s"|d td |dnE|jtkr5||d|jdt!t"d|S)Nzapplication.ini Version r;rzplatform.ini Milestone rrzthe unpacked treez'this tree (which has no omni.ja either))rr rzthis tree (layout rzno z/ in z% (Playwright cannot drive this build)z$ carries the stealth marker in only rzP juggler entries (a stock build scores 0): this is not one of our patched builds)r=rrr^rr6r<rYrrrrrrrJUGGLER_MIN_MARKEDr;r)r/r1r2probsr9rwheres rengine_problemsrB4s   E }--- ^ ^^TEZ^^___&eT599H+U^XFFA Q "u$:O'O'O _u__dF[__``` * ne.Ex P P   LLOOO$9   c%  NU5I N N NOO   * ]?]]]]]^^^^   2 2 2  ) )%:N ) )?## ) ) ) * * * Lr)r2sourcec|p t}t|}t|||}|s,ttj|St|||}|rd|nd}dd|j d|d|j pdd|j pdd|j d|d |j d |jd d d |jd g}|dt!|Dz }|ddddddddgz }t#d|t%||j |j )aRefuse to hand back `entry` unless the engine matches `seal`. Called on every route that turns a path into a running Firefox. Returns the path so it can wrap an expression in place. `asset`, when the caller knows which leg it fetched, pins the BuildID comparison to that exact leg. The path handed back is the one the FILE SYSTEM says the executable is at, not the one it was asked about, because that is the path a launch needs. Under an MSIX host (Claude Desktop, the Microsoft Store Python) writes into AppData are silently redirected into the package's own LocalCache folder: the process that downloaded the engine sees it at the AppData path, but nothing is there on disk. CreateProcessW accepts that path and then fails with ERROR_SXS_CANT_GEN_ACTCTX (14001), because Windows resolves the `mozglue` assembly that firefox.exe declares against the directory as it really is, outside the redirection. Retail Firefox fails identically when installed that way, so this is not about our archive. `os.path.realpath` asks the file system through the handle and returns the LocalCache path, from which the same engine starts. Reported as invisible_playwright discussion #256 on 2026-09-25, and issue #22 in May was the same failure under the Store Python. It sits HERE, and not in the downloader, because this is the one function both routes cross: the cached engine from `ensure_binary` and a caller's own `binary_path=`. Anywhere else would need a second copy of the same fact. z or ?z)engine/seal mismatch - refusing to launchz executable : z origin : z engine says: Firefox rz seal says : Firefox z (tag rNrz, from rc4g|]\}}|dkrd|nd|S)rz problem : z r)rirs rr|z!verify_engine..sK,,,!Q()Avv####3HQ3H3H,,,rzO why : the prefs and the spoofed User-Agent this package ships describezK the sealed build. Running a different engine under them is az/ disagreement a page can observe.z4 fix : python -m invisible_core doctor --fixzK (deliberately driving another build? generate a seal for it:zM python -m invisible_core seal --binary -o my.seal.jsonzL and export INVISIBLE_SEAL_FILE=my.seal.json - the User-Agentz? then moves with it, so the pair stays coherent) r&)rr0rBrrrrealpathr6rr(rrYr^r]rcrd enumerater$r3) r(r1rCr2r/r@r9rliness r verify_enginerL[s6  ;==D  ' 'E E4 / /E -BG$$U++,,,%eT599H$, 56;;x #D3'%+''"&""V%-"63VVu~?TQTVV I$"7 I I I I I I!%SbS!1 I I:>+ I I I  E ,,#E**,,,,E YU9 @UWVI#E. 5))E%LL${TX ? ? ??r version_dirc0t|tz Sr)r STAMP_NAMErMs r stamp_pathrQs   z ))rOptional[dict]c tjt|dS#t$rYdSwxYw)Nrr)rrrQrrrPs r read_stamprUsRz*[11;;W;MMNNN tts47 AA asset_sha256adoptedrkcddl}ddlm}|j|}t |j|j|j|r|j ndp|j |||d|| d| d }t|} | d } | tj|d d d t#j| | dS)z@Written LAST, after everything else is in place, and atomically.rNr7) __version__r%zinvisible-core z%Y-%m-%dT%H:%M:%SZ) r seal_digestr]r^rYr2rVrW written_by written_atz.tmpTr ) sort_keysindentrrT)time_versionrYrbrrrcr]r^rYstrftimegmtimerQ with_suffix write_textrdumpsrr) rMr1r2rVrWr_ core_version sealed_assetpayloaddsttmps r write_stamprksKKK555555;??5))L'{x 1.:B\**Tt}$6 66mm$8$++--HH  G [ ! !C //& ! !CNN4:ga@@@7NSSSJsCr)rBr+r.r+)r.rJ)rrrdr+r.r\)r.r)rrr.r\)r.r\)r.r/)r(rr.r)rrr.r)r(rr.rJ)rrr.r)r(rr.rr)r/rr1r\r2r3r.r,)r7r+r8rJr9r,r.rJ)r/rr1r\r2r3r.r=) r(rr1rrCr+r2r3r.r)rMrr.r)rMrr.rR) rMrr1r\r2r+rVrJrWrkr.r/)Cr __future__rrrrrRrLrerur  dataclassesrpathlibrtypingrrrrSUPPORTED_LEGSr3dictfromkeysSUPPORTED_PLATFORMSrrrrOcompilergrrrrrr?r RuntimeErrorrr"r$rIrMrPr\rrrrrZrrrrrrrrr0r6r<rBrLrQrUrkrrrrws.#"""""  !!!!!!(((((((((( PeDMM)G)G)G)G)GGGHH$X. % # .//;D #2 2OOOOO OOOBBBBB<BBBRRRRR\RRR<>>>> $         $n3n3n3n3n3n3n3n3b----`1111****( $ ! ! ! ! ! ! ! !    *"(%(%(%(%V-/ ....&&&&T59:::::&0000.2$$$$$ND?;?D?D?D?D?D?D?R****r