test: qualify original Antelope and reversible worker attempts #321

Part of #288, before #277 capacity accounting; coordinated through eosrio/hyperion-tools#24. Original starting point: merged #320 at 6d2ca5779498f1d60c10a6151ed90b59ecf9e1f7 / tree 1a11d1e7ceefd755da3f714fcb7bee3c777c6a3e. All nine combined-head CI jobs passed. Parent #289 stays draft.

The original managed callback/retained-store cases currently focus on Wire. The managed fixture supplies controlled irreversible authority. The reversible adjudicator unit checks the selection predicate with controlled stores and a synthetic linked worker. Neither demonstrates the complete original builtin Antelope callback, retained fresh result, authentic end and actual master/coordinator source guard together. This is a qualification gap, not an established production defect.

Acceptance:

• Build a short deterministic fixture using the builtin Antelope codec and ABI-correct source bytes, independently specified expected output and explicit source/ABI-deployment/ordinal/producer/runtime pins. Exercise the original emitted MainDS and DS callback paths with actual retained stores and native parent/worker IPC. Preserve all proof, handoff and fresh-result validators; do not relabel Wire bytes or enable plain-proof/plain-handoff bypasses.
• Cover a genuine contract handoff and an explicitly source-derived no-effect/incomplete outcome. Only the same physical attempt's fresh configured-copy receipt, authentic quiescent end and original source/effect membership may establish a private association. Reads, copied ends, primary-visible records and ACK-attempt markers cannot substitute.
• Exercise a reversible source through the actual master authority/coordinator path. Hold required work across source replacement/revocation and current configuration/physical-target checks, including late awaited completion. Avoid an always-successful canonical guard or a boolean-only replacement for the real owner/generation checks. The old scope cannot renew proof, publish effects or become a successful association after revocation.
• Keep physically pending operations owned until real settlement or exact process exit. Preserve unrelated worker progress and raw unknown/failed outcomes. A recovered delivery needs its own fresh write and end under the current source; retained visibility grants no source, readiness or capacity authority.
• Label constructed source, canonical RPC and transport controls explicitly. Such controls are implementation evidence, not live-chain or combined-fork qualification. Reuse existing worker/storage infrastructure and keep original Wire regressions intact.
• Run focused native Node 24/26 cases, complete-project Bun 1.4.4 / TypeScript 7.0.2 checks, native emission, applicable root tests and product CI. Retain exact source/input/emission pins and raw observations, plus independent complete-delta Spec/Standards review. If a real defect appears, retain a tight failing counterexample and scope the smallest fix before claiming the case passes.

No reader grant/credit or prospective count/byte change, default activation, new worker/transport architecture, dependency upgrade, ancestry/durability/budget/deadline increase, or production service mutation. This slice does not replace #288's remaining combined live broker/storage/fork work or #277's unchanged full original 1..1480 Linux Node 24/26 replay and capacity acceptance. Earlier failed replays and shutdown observations remain frozen.

Original Antelope component checkpoint — 2026-10-25

#322 merged as 6667d3a00983ee3b6229d86fd815667987e11973, tree c576e97ba9e91b2c4419cc954b1518d4f4ab16c5, exactly matching reviewed 1626fafb. The pinned fixture and provenance cover original builtin Antelope handoff, encoded-empty traces and missing traces. Actual managed native IPC, historical ABI selection/native decode, two-copy retained writes and the master's own adjudicator remain active. Stale config, target UUID, canonical identity and config replacement during an awaited target read cannot create an association.

All three cases pass on native Node 24.19.0 and 26.4.0. Local full suite: 1,476 pass / 18 optional skips / 0 fail / 10,046 assertions. All nine reviewed-head CI jobs pass; both Node 24/26 build jobs actually execute the new cases and each report 1,493 pass / 1 optional skip / 0 fail / 10,080 assertions across 1,494 tests / 131 files. Independent complete-delta Spec and Standards reviews have zero actionable findings. Copilot did not run because quota was unavailable. All nine separate combined-head jobs also passed at 6667d3a0. The original Antelope handoff/empty/missing cases ran on both native Node legs; each leg reports 1,493 pass / 1 optional skip / 0 fail / 10,080 assertions across 1,494 tests / 131 files.

This issue remains open. The actual reversible master/coordinator reader ownership, source generation/revocation/replacement, late awaited completion, physically pending work and fresh recovered-delivery cases above are still required. Builtin Antelope currently does not attach an extension source selection; its reversible RPC-only negative remains unresolved, not qualified support. Constructed source/service/RPC controls and private associations grant no live-chain, capacity or release acceptance. Parent #289 stays draft, and the original failed full replays remain unchanged.

Reversible Wire component checkpoint — 2026-10-25

#323 merged as a808b31755b8e24088b0c62ec6e88e620b40243b, tree 23c32eca58c366f6fe149a321d67924464315582, exactly matching reviewed bccfb1bf. The original master handler/adjudicator, ABI coordinator, source binding/frontier/admission stores and four separate native reader/MainDS/DS processes remain active. The baseline, held-operation revocation/current-source continuation and redelivery, and late canonical RPC cases all pass on native Node 24.19.0 and 26.4.0.

Each revocation run retains four owned pending operations at the fence while an independent current worker and its fresh conditional redelivery complete. The old response settles only afterward; its authentic drained end remains unresolved, with no ACK or post-fence output/storage/cache/stream dispatch. Configuration/physical-target replacement during awaited reads also refuses association. Full retained end descriptions must equal their original physical/native replies. The preserved valid-bundle counterexample demonstrates the old identifier-only consistency gap and corrected rejection, with unchanged attempt IDs and original native transcript.

Complete-project Bun 1.4.4 / TypeScript 7.0.2 checking and native emission pass. The immutable final-head local suite reports 1,479 pass / 18 platform or optional skips / 0 fail / 10,060 assertions across 1,497 tests / 132 files. All nine exact-head CI jobs pass; both Linux Node 24.21.0 / 26.12.1 unit legs execute all three new cases and report 1,496 pass / 1 optional skip / 0 fail / 10,094 assertions. Both full-delta reviews are complete: Standards has zero remaining findings, and Spec identifies the two remaining issue-wide gaps below. Copilot did not run because review quota was unavailable.

Independent read-only custody inspection verifies all 54 payloads / 258,123,917 bytes, exact source/emission/runtime pins, recorded native exits, original IPC/end and full retained-association bindings with no mismatches. Capsule SHA256 fd1ba1db62983298a1b4f6efd2d1eb402d5fc8201d427f5cf74abdabb95fea57; manifest 1a60d9b87c83c7585e1c182c06ad201df77bba1a17e0fcb74e43148a1bf8d194. The audit checks recorded consistency; remote chunk copies were not separately downloaded and no new live process census or authority is inferred. All nine separate combined-head jobs also passed at a808b317. Both native Linux Node 24.21.0 / 26.12.1 unit legs execute the three reversible cases and each report 1,496 pass / 1 optional skip / 0 fail / 10,094 assertions across 1,497 tests / 132 files.

This issue remains open for:

• builtin Antelope reversible selected-source callbacks through the actual master/coordinator/reader path;
• fresh current-source recovery of the revoked original block-33 delivery. The successful block-34 continuation/redelivery establishes unrelated progress.

Constructed head/LIB envelopes preserve original block/trace/delta payload bytes. This component grants no live-chain, combined recovery, capacity or release acceptance. #289 stays draft; #288/#277 and all earlier failed original replay/shutdown observations remain unchanged.

Current recovery checkpoint — 2026-10-25

#326 merged into #289 as ec5a40a73fd89a0bbb9f2da74243b34b83495a00, tree fd432ae366fe2d310162ccdd5e2a1e3e79c71743, exactly matching reviewed 418137f4. Use this integrated head for subsequent #321 work.

The revoked original block-33 Wire delivery now recovers under a distinct current reader selection and physical attempt while the old operation remains held. Its own fresh configured-copy result and complete authentic end establish the association; old ends stay unresolved. Block 34 then continues and redelivers independently. The reader replays the actual requested 1..33 prefix instead of advancing publication progress from ABI coverage. Newly produced source-schema-2 history plans bind the exact retained input; schema-1 identities/read/retry and complete fingerprints/immutable conflicts are preserved. Obsolete publication callbacks are fenced. #324 and #325 are complete within this scoped integration.

The first frozen suite at fbee53aa failed two old ABI-only resume assumptions; both failure records remain preserved. Corrected host fixtures replay the requested canonical suffix and original constructed observation fault before fresh confirmed irreversible publication advances the cursor. Independent Spec review also exposed a saved-report consistency gap. The same report-only counterexample passes the old checker and rejects after correction; all five end-report shapes now require complete association/native equality.

Final-head complete-project checking and native emission pass. Local suite: 1,489 pass / 18 platform or optional skips / 0 fail / 10,105 assertions, 1,507 tests across 133 files. All nine exact-head CI jobs pass; Linux Node 24.21.0 and 26.12.1 each execute the host and native recovery cases and report 1,506 pass / 1 optional skip / 0 fail / 10,139 assertions. Six fresh native Node 24.19.0/26.4.0 cases, fourteen reader controls and fourteen contradictory report-copy rejection paths pass. Full-delta Spec/Standards reviews have no remaining scoped findings. Copilot could not review because quota was unavailable.

Independent recorded-evidence inspection verifies 1,014 payloads / 524,588,921 bytes and all 39 local chunks, with no content mismatch. The six cases retain 24 original child exits, 80,544 service pairs, 348 native ends, ten associations and 334 frame deliveries. Source snapshots explicitly distinguish Windows CRLF from Git LF; emitted files are archived disk snapshots, not in-process module attestation. Capsule SHA256 9ac3e9a67273d1fe3066c30670da20a88c168e03d796d85ef7dec67a02224c12; manifest cf24251fcf8b6eaba7321c26697f6ab4658081997abd6d2c458946c52f4c9fad. Remote index/matrix were retrieved and hash-checked; remote chunks were not separately downloaded. Historical failed/unknown outcomes remain unchanged. All nine separate combined-head CI jobs passed at ec5a40a7. Both Linux Node 24/26 unit legs execute the host/native recovery cases and each reports 1,506 pass / 1 optional skip / 0 fail / 10,139 assertions across 1,507 tests and 133 files. The original pending-state receipt remains unchanged; this is subsequent CI evidence.

This issue remains open for builtin Antelope reversible selected-source integration through the actual master/coordinator/reader path. The previous Wire block-33 recovery gap is complete. Parent #289 stays draft; #288 retains combined live recovery and #277 retains prospective capacity accounting and the complete original 1..1480 Linux Node 24/26 replay. No live-chain, full replay, capacity or release acceptance is inferred from these constructed component controls.

Antelope selected-source component complete — 2026-10-25

#328 merged into #289 as 3d53712e2cefac7d469fb7c0d233d7edb484316c, tree 8212a13506a09aa4ca3e925e849787c1fa2aef11, exactly matching reviewed 3231800d. The builtin provider now emits ABI observations and uses the shared source lifecycle behind the existing engineering admission/live gate. Nonempty component identity comes from the actual bounded host/native-codec/SDK/lock inventory. Antelope keeps native decoding from its original occurrence proof; Wire code and historical/current ABI fallback cannot authorize this gated path. Operator/default activation is unchanged.

Independent constructed Antelope blocks establish ABI state, encoded-empty input, block-2 contract handoff and block-3 continuation. The actual master/coordinator and four separate original native workers cover source revocation while original IO remains held, fresh recovery of that same captured delivery, independent continuation/redelivery, current configuration/target awaits and late canonical RPC. Old scopes/end replies remain unresolved; recovered work supplies its own fresh configured-copy result and authentic end. Explicit grouping modes preserve Antelope receipt fields and notification/identical-inline identities. Original Wire regressions remain active.

Complete-project Bun 1.4.4 / TypeScript 7.0.2 checking and native emission pass. All twelve retained native Node 24.19.0/26.4.0 cases and 34 contradictory report-copy rejection paths pass. Local suite: 1,497 pass / 18 platform or optional skips / 0 fail / 10,144 assertions, across 1,515 tests / 134 files. All nine reviewed-head CI jobs pass; Linux Node 24.21.0 and 26.12.1 each execute the new controls and report 1,514 pass / 1 optional skip / 0 fail / 10,178 assertions. Complete-base Spec/Standards reviews have zero remaining findings. Copilot could not review because its quota was unavailable.

Independent recorded-evidence custody verifies all 1,529 payloads / 616,015,709 bytes, 48 local envelopes, source/runtime/oracle pins, 48 recorded child exits, 87,854 service joins, 386 original ends, 20 retained associations and four original-delivery recoveries. Capsule SHA256 f82f96c3188f07acec1b579acc6d50865e917b5181ff4fdd943236f8395ead46; manifest d0a61f4b3ac6937a34b9264f68c25c3bee2bee4e6ae335f2d552fa648f594f84. Published index/matrix were independently retrieved/hash checked; remote chunk payloads were not separately downloaded. Emissions are disk snapshots, not loaded-module attestation. The earlier d75 captures and 57 historical controls remain unchanged. The supplementary 29-payload final validation bundle is separately root-verified, not independently audited; its PR checkpoint retains hashes and complete review reports.

The scoped #321 original-worker component matrix and #327 bridge are complete. Separate combined-head CI is running at the merged commit; the passing reviewed-head results above are separate. Parent #289 stays draft. #288 retains combined storage/live-fork recovery, and #277 retains prospective count-and-byte coordination and the complete unchanged 1..1480 Linux Node 24/26 replay. Historical failed replays, incomplete holds and unknown settlements remain frozen. No live-chain, full-replay, capacity, deployment or release acceptance follows from these constructed component controls.