[EHotwagner]

The published enrollment constructor refused its own release-registration change and treated explicitly archived predecessor cards as missing membership. Restore those supported paths with narrow authenticated source equivalence and complete native membership reconciliation, and prepare the coherent 0.114.5 source cut.

Refs #5263

The source-equivalence case permits only the coordination CLI version change in dist/dotnet/.config/dotnet-tools.json, joined to the actual engine host version, constructor/host source and native coherent-set tag. Other closure or ancestry changes retain their refusals. Archived enrollment uses the maintained exact issue/project/content/item reader and complete bounded pagination; partial, conflicting, foreign, duplicate or unarchived results remain Unknown. Original enrollment rows and custody are preserved, and the transport admits only the fixed read-only query and typed variables.

The producer scalar and registry source version are 0.114.5. Published package-version, tag and canonical tool pin remain 0.114.4. Maintained generators reconcile projections, public Atlas seeds/manifests and census hashes; all 529 protected Atlas records remain, including #5264's record, with the enrollment lesson and accepted HighBar bootstrap capture added.

Validation: independently reviewed original code/control bytes are unchanged; their full projection fixture printed 325 passed, 0 failed, 0 skipped. The pre-repair 9b26667f CLI build printed 0 warnings/errors, version 0.114.5.0, and CLI/GitHub/Core informational versions all match that exact source. The subsequent repair changes only one mutation-spec anchor; those assembly bytes remain evidence for 9b26667f, while changed-head assembly identity belongs to its actual hosted/canonical release build. All three coherent projects evaluate to 0.114.5; release notes fit the enforced budget; five actual CLI project-reference graphs restore locked. Candidate/source-closure controls printed 26 tests each; sealed-route controls, canonical registry preparation, projection and writer-census checks passed. Checks ran within 1 CPU / 3 GiB; original failures and byte joins remain retained. The generic product lock-range checker has the identical 172 implicit-version refusals on protected baseline and candidate; it is not this repository's lock gate, and no new diagnostics or manual lock edits were introduced.

The original hosted edge run exposed a stale CI18 mutation-spec anchor after the guarded observer call changed. Retarget that one find literal while preserving its NotObserved/NotEvaluated replacement and end-to-end leg. The maintained corpus now reports 20/20 runnability assertions; a single-application control confirms the exact call is removed once. This measures runnability, not mutation strength; the original hosted failure remains retained.

The repaired head’s actual hosted checkout is synthetic merge 94010b591d801680207977fb57b375a524b97084 (parents protected f3798576 and reviewed fa06e08d); its tree equals the reviewed head. The native engine build succeeded. Retained actual early TRX results show Core 1,273, CLI 786, passive Host 5 and workspace 34 passing, with zero failures/skips. The hosted source-free package fixture reports 45/45 and identifies candidate FS.GG.Coord.Cli 0.114.5, SHA256 6adeaa460d1e026725eaba0f5d7b53a6cf6b5f10ae759e180ccf288d4ab5270b, bound to that actual synthetic source. Its receipts explicitly say public release/main installation are false. This package is qualification evidence, not a published release or installed board-reader selector. The original broader engine job remains in progress; its terminal result is required before integration. All ten native required checks have successful exact-head/App15368 joins; repaired edge, parse and semantic quality checks also passed.

The first source branch push selects no workflows. The opened PR selects 53 pull_request plus two pull_request_target workflows: one local reusable call, 78 leaf job definitions, no matrices, one known-false job and two runtime-output conditions (77 potential runner jobs before dependency outcomes). Inherited 2–40 minute timeouts remain. Five jobs may upload run artifacts; one mints/revokes a scoped read-only App token. No repository/project/package publisher is selected; tag-only legacy publishers and candidate/publisher dispatches remain unselected. The repair push and canonical exact-head/body update produced 62 original attempt-one runs: 55 synchronize-event entries plus seven edited-event entries. This final evidence-only body update selects another seven edited-event workflows/eight jobs, with the same source and no source push. Those metadata runs are counted separately; this is event-triggered workload, not manual reruns. Remaining runtime and cost observations follow the original native jobs.

This merge continues the Delivery. Required CI is green; broader original-engine terminal qualification and integration remain pending. Canonical publication, actual installed-caller qualification, supported successor enrollment and coordinated archive binding/commitment/reader/acceptance-receipt qualification remain open. No publication, installed selector, live constructor, enrollment or timer effect was performed by source preparation. Native-plan and membership gaps retain their owners.

architecture-map: unaffected