Jobs Discovery installed receiver

rc.21 and Alpha 1.41

The rc.21 edition selects Alpha 1.41.0, commit 031bdb5d055c8bad896daa076baea2b5e17b242c, tree 330e0e58268ed32990f04278fc543c71db45fd46. Its catalog has 53 members. The complete captured closure also contains the inspector, license and catalog bytes. The exact-source static review accepts bounded installed Discovery source admission; installed compatibility and publication are separate decisions. The original reviewed615 pin and rc.20 release remain historical evidence.

Use the rc.21 release and its exact qualification receipt. Download jobs-discovery-installed.tar.gz, install-discovery-installed.py, provenance.json and SHA256SUMS.txt; authenticate their identities against that release. Python's standard library installs the archive; no npm installation is required. The designated runtime targets are Linux x64 with Node22.23.3 and Node24.21.0. Other architectures remain unqualified.

Select ARCHIVE_SHA256, ARCHIVE_BYTES and INSTALLED_MANIFEST_SHA256 from the authenticated provenance.json capsule record, not from the extracted directory. Use an absent absolute installation path:

python3 install-discovery-installed.py --archive jobs-discovery-installed.tar.gz \
  --sha256 "$ARCHIVE_SHA256" --manifest-sha256 "$INSTALLED_MANIFEST_SHA256" \
  --output "$INSTALL_ROOT"
node "$INSTALL_ROOT/integrations/alpha-agent/discovery-installed-operator.mjs" \
  status "$INSTALL_ROOT" "$INSTALLED_MANIFEST_SHA256" "$ARCHIVE_SHA256" "$ARCHIVE_BYTES"

A status inspection starts no service. For the original bounded mission, use the byte-checked Jobs workspace and Jobs request. Their exact identities are in the frozen packet custody. Save them as workspace.json and request.json and choose an absent absolute result path:

node "$INSTALL_ROOT/integrations/alpha-agent/discovery-installed-operator.mjs" \
  inspect "$INSTALL_ROOT" "$INSTALLED_MANIFEST_SHA256" "$ARCHIVE_SHA256" "$ARCHIVE_BYTES" \
  workspace.json request.json "$RESULT_JSON"

The installed receiver checks the exact mission/source context and returns a local receipt, preserved workspace and export/reopen docket. It exits after the operation; it starts no background service. Failed or inconclusive work and duplicate imports do not become accepted work. The separate installed native acceptance also exercises all six stages, failed attempts, budget limits and a stronger successor. Actual receipt costs and incomplete system/provider costs remain distinct.

This route is zero-cap AGIALPHA18 local synthetic review. Manager's USDC6 route remains a separate alternative draft. External execution, funding and settlement are unprovisioned. The original packet's Fleet proof is an older un-attested component record; it does not qualify the new Fleet candidate, a four-product installed journey or an automatic successor authority transfer.

Exact transition and evidence reuse

The pin helper retains the original unset transition and permits only the finite reviewed615-to-reviewed031b successor. It verifies the exact predecessor pin/transition, whole source proof, genuine source review and all 56 raw Alpha inputs against actual Git objects. Both current consumers must then qualify their actual saved archive; source review is not installed acceptance.

The original packet is run40076340788, attempt1, workflow366358276 (agent-release.yml), namespaced job120821426397 and artifact12552939436. The finite admission case retains the original source, all three successful step labels, complete metadata snapshots and every transport/source guard. Only that fully bound tuple selects the new workflow/job case; unknown or mixed tuples fail. All eleven original raw members remain unchanged. The common17 transport preserves the complete original253-member inventory and actual attempt metadata; a later associated PR head is not a replacement for the original run source.

For this exact Alpha1.41 release only, the publisher may reuse the accepted original anonymous106-body verification. The original receipt bytes are fixed by SHA-256. Every live asset ID/name/size/digest/public URL must still match the entire106-entry set. Checksums, release manifest, pack manifests and the operator source ZIP receive fresh bodies and the complete source/pack checks. Live release/tag/main/run/asset leases remain mandatory. The report explicitly distinguishes retained body observations from fresh requests; no new installed or connected result is inherited. A missing/tampered receipt, changed asset or unknown Alpha source fails. The historical1.38 profile retains its complete-download behavior.

Publication still requires exact reviewed source, current-source scanners and case-specific quality decisions, both installed runtime receipts, fresh actual-main qualification, the immutable publication-review record and anonymous verification of the new Jobs release. All original denials, historical scanner records, releases and source-only guards remain intact.

Historical rc.20 engineering and qualification record

The following retained record describes the earlier615-source edition and its original gates. Its inputs and acceptance do not become rc.21 acceptance.

The new jobs-discovery-installed-v1 lane supplies a standalone, source-bound local review receiver and the captured Alpha runtime. The checked-in Alpha pin selects reviewed source 61532fb82621a065e668fd11e57289dcfb65c67b, tree 7814d1bd9dcd3845b349590e0bcac57ba93b3167, with qualification PENDING_FINAL_SOURCE_NATIVE_COMPATIBILITY. Source and browser input selection does not grant installed acceptance: the original final-main producer, both extracted native consumers, exact-source scanners, verified public Alpha release and publication review must satisfy the gates below. The finite source preparation metadata records 2.1.0-rc.20 as an unreserved proposal and grants no publication selection. The rc.16/rc.17 publishers, accepted scanner records, historical96 ledger and existing source-only guards retain their original bytes.

Source and immutable pin transition

The local history combines public main 83065adf with prerequisite 792687d1, retaining publisher d27d752c, and Discovery 5b85af62, retaining the 285/852 ancestry. Their local reconciliation 75d38869, tree fac37bef, remains historical preparation; the verifier does not require its unpublished commit SHA as a public ancestor. Commit c12ce2eb preserves that preparation and its license evidence. Public main ba67d5d1, tree 16c29d93, contains the normal 83065/23b8916a merge and prerequisite owner stack. It was normally merged locally at f3e73ac7 without changing the installed source bytes. The source verifier requires the public 83065, 792 and 5b ancestors plus the complete exact finite raw tree.

The new finite profile reconstructs the complete5190-input prerequisite tree from the fixed5185-input main baseline and exactly41 attributed prerequisite changes. It then validates every actual source input against the separately frozen finite delta and three externally selected SHA-256 values: manifest, source verifier and installed scanner scope verifier. The scope verifier fixes the first two digests; its own selected digest covers that final binding without a circular hash. The old5199-input source-only profile continues to refuse the combined source. A caller cannot hide a source file with a supplied path list.

The complete producer proof traverses bounded expected directory prefixes without following links and rejects nonregular inputs, special filesystem nodes and unexpected empty directories. Source-verifier entry points check direct paths and selected policy digests before compiling the already captured verifier bytes through a fixed standard-library bootstrap. Candidate workflow hashes select an unapproved candidate only. The separately selected immutable publication-review digest binds the exact source commit/tree and all three policy digests outside that candidate's self-selection.

Scanner validation independently enumerates the committed index and checks every tracked raw input plus actual Git tree, index and public ancestry. Generated scanner outputs remain outside that proof. Archive production separately requires the complete actual filesystem inventory before any generated output is written. The rc.18 dispatcher selects this additional scope verifier while retaining the old scope path for historical editions; it does not waive ledger, query, scanner or quality decisions.

freeze-discovery-installed-alpha.py requires a complete source/Git/index/ancestry proof and an independently selected case-specific review record SHA-256. It captures the reviewed Alpha commit/tree, all41 catalog inputs, catalog bytes, installed inspector, license and modes against their raw Git blobs. It only writes an external proposal containing the new pin and a transition from the immutable unset-pin digest. Installing the proposal is a separate reviewed source change with renewed finite policy pins. A changed JSON status alone cannot activate it. The review record and transition do not grant publication, independent organizational validation, external execution or transaction authority.

One saved archive, complete installed bytes

After the reviewed pin is installed, the build subcommand of discovery-installed-package.py verifies complete Jobs source, captures every shipped Jobs input against its selected source inventory, captures Alpha raw inputs against the reviewed Git tree, and validates static dependencies without evaluation. The deterministic archive contains the actual receiver/contract/operator/runtime, native acceptance command, complete Alpha41 inputs plus inspector, source-verification material, immutable per-file digest/mode manifest, MIT license and applicable Apache text/origin notice. It records whole-source provenance separately from the installed subset. Runtime inspection requires no external source checkout, Git, npm installation or network.

The separately published install-discovery-installed.py requires only Python's standard library. Its exact bytes are captured from the selected Jobs source, retained with the saved archive and producer custody, checked by both consumers and published as a checksummed software asset. Authenticate that installer against qualified release provenance before executing it. Its archive and installed-manifest SHA-256 inputs are independently selected. It bounds compressed/expanded/member sizes, checks every path/type/mode/hash and the exact member inventory before writing into a new inactive directory. It retains extraction custody. The source builder's install compatibility subcommand delegates to the same installer. The installed runtime captures the exact immutable input set and serves imported code from owned buffers through a lifetime resolver/load boundary. Static records include side-effect imports and reexports; computed imports are separately constrained by that boundary. The actual Jobs receiver alone may use node:crypto and node:fs to hash its own captured source; Alpha modules receive no builtin allowance.

The earlier prepare subcommand remains an explicitly inert unset-pin source capsule. Its historical results are not installed qualification.

Actual request, same mission and docket

The installed operator provides status ROOT INSTALLED_MANIFEST_SHA256 ARCHIVE_SHA256 ARCHIVE_BYTES and inspect ROOT INSTALLED_MANIFEST_SHA256 ARCHIVE_SHA256 ARCHIVE_BYTES WORKSPACE_JSON REQUEST_TEXT ABSENT_OUTPUT_JSON. Select all three provenance values from the authenticated original producer record. The runtime requires that independent hash/size/manifest selection and compares the entire extraction custody record before reporting capsule provenance; missing selection cannot fall back to the mutable extracted INSTALLATION_CUSTODY.json. The native command requires the same selection through --manifest-sha256, --archive-sha256 and --archive-bytes for both the original mission and the separate constructed regression. It independently replays the retained mission, finds one accepted source-bound campaign, derives its AGIALPHA18 draft commission and typed artifact prefix, checks the original request against that context, and invokes the actual Jobs receiver with the installed Alpha inspector. It validates the returned source-bound receipt, appends its exact raw bytes to the original mission event chain and exports/reopens the canonical docket. Prior events and authority boundaries remain intact.

The source-bound deployment inventory is included and consumed by installed status/inspection. It preserves the recorded Jobs route, token denomination/decimals and operator requirements. Fresh on-chain observation remains NOT_RUN; repository snapshots do not make paused, unavailable or unfunded operations executable. All commission caps remain zero, authority is none and settlement/external execution remain unprovisioned. USDC is a separate alternative route, without currency conversion or a duplicate payment obligation.

Qualification and publication

The separate installed producer workflow builds one saved archive. Two consumers extract those same bytes on the designated Node22.23.3 and Node24.21.0 runtimes and invoke the shipped native command. Both require the actual original browser workspace and AGIALPHA request. The primary path invokes the actual operator once, appends exactly one returned receipt to that same original mission, retains its event prefix and raw input/request/receipt bytes, and exports/reopens its canonical workspace and docket with the receipt costs. Missing primary inputs cannot fall back to a constructed mission.

A separate mission, explicitly labeled constructed regression, exercises all six stages, a budget-limited receipt, failed/rejected/inconclusive work, stronger successor and duplicate refusal. It retains its own complete construction history, raw requests/receipts, workspace, docket and cost ledgers under regression/. Both paths run on both installed runtimes from the same saved candidate. No constructed campaign is added to the original browser workspace; receipts and costs are not imported or aggregated across the two missions. The whole evidence artifact records per-file hashes and byte-identical reopening for each mission. Neither path is remote execution or institutional independence.

Publication requires both consumers to use the same actual browser workspace/request retained in the producer artifact. The checked-in browser input config binds the successful original Alpha61532 push producer 39841271826, attempt1, and artifact 12453756312. It uses the same binding shape as Manager; the shared public packet uses successor/discovery-browser-artifact-custody/v1 at evidence/discovery-browser-inputs-v1/61532fb82621a065e668fd11e57289dcfb65c67b in transport commit e31e74d1a5144973e6a22006dbe29ea628a80386, tree 60823a663933991dc5f703735577a40f07a7d3dc. The packet contains CUSTODY.json, eleven original source/page/workspace/request/journal/proof members and five captured API records under metadata/. The independently selected packet commit/tree, custody Git blob/SHA-256/bytes and complete original archive inventory bind these copied bytes. These input identities do not substitute for native consumer results or final release qualification.

The capture helper rechecks the original successful exact-Alpha-main push run, executed browser job steps, artifact metadata, public packet tree and every retained Git blob. It validates the original source/catalog/page, matching USDC and AGIALPHA drafts from the same unchanged browser workspace, UI export journal and native return proof. The external custody producer must first authenticate the original archive. Both native consumers receive the original Jobs workspace/request aliases from the same saved producer artifact; qualification repeats the common packet authentication and compares all seventeen retained packet members. This public Git transport requires no cross-repository Actions ZIP permission. It does not claim another original archive download, and a constructed mission cannot satisfy the primary gate.

The new qualifier/publisher route requires original successful actual-main workflow attempts, executed steps, raw logs, downloaded archive/member custody, matching producer and two consumer source identities, all inherited contexts and scanner services, and fresh complete current-source case-specific scanner/quality decisions. A separately selected immutable publication review and the explicit new selector are required before release publication. Existing rc.16/rc.17 acceptance rules and accepted review slots are not repurposed.

The Alpha publication helper requires the public release/tag/main ancestry and successful Agent-run API identities, then enumerates the complete public asset inventory and anonymously downloads every asset. It streams and compares each actual byte count and SHA-256 with the API identity, complete checksum inventory and source-bound release manifest. Required software assets include the lock, source archive, normalized source distribution and exactly one version-bound wheel; browser/site bundles and the required historical CI identity must also match. The held downloaded operator bundle must contain the exact authenticated catalog and all41 source bodies with their catalog hashes. Fresh release/tag/main/run/asset metadata checks close the download lease. Missing, changed, incomplete or differently bound assets fail qualification before publication; API metadata or a separately copied catalog cannot satisfy this gate. Actual selected public downloads and exact-source installed qualification remain required evidence.

After the final qualification pass, the publisher downloads and verifies the draft bytes again, refreshes the prerequisite release/tag/tree and immutable asset identities, and checks the exact draft release ID/state/target/body and asset IDs/sizes/digests. It reads current main last and publishes by that leased release ID, then independently downloads and verifies the public assets.

Historical scanner assessments retain their exact source and raw identities. The current4019 PR scan has separate case-specific eight nonsecurity quality acknowledgments and eleven security assessments; neither accepts a later PR or actual final-main scan. All nineteen cases must be reconciled to the actual new raw/query/config/source identities under the existing gate, and no historical accepted metadata or generic review clearance substitutes for that work. Full system, human coordination, heap, energy and provider costs remain incomplete; the docket retains that limitation and all measured native attempts rather than claiming complete savings.

The next publication identity is discovery-v2.1.0-rc.20, selected because the response-bound publisher source and its finite profile have changed. The private rc.18 draft421509220 retains its seven assets, and rc.19 draft421829307 for source ca6cfb74a36c233e5f04bd591a5e2179299774a1 remains empty and unpublished. Original publisher39955023372/attempt1 failed its immediate inventory assertion; its discarded creation response cannot now prove the discrepancy's cause. Neither a later connector inventory nor this correction establishes eventual consistency. The publisher checks complete bounded inventory before creation, performs exactly one POST, retains that response outside the seven release assets, and validates the returned repository/release ID, tag, target, title, notes and empty-draft state. Up to five read-only ID/inventory observations (two seconds between attempts) handle visibility differences. Multiple or mismatched identities fail immediately. Interrupted retries refuse the already reserved tag before new qualification, output, creation or replacement, preserving the original response, draft and assets; historical drafts are never adopted or finalized. An interrupted run is preserved for explicit diagnosis rather than automatically resumed. The internal rc18 dispatcher output remains the installed-suite route name for explicitly enumerated rc.18, rc.19 and rc.20 editions; all run the complete installed checks and cannot select the historical rc.17 publisher.