Recover bounded CI continuation through authenticated durable publication

[EHotwagner]

Exact-head CI collection can exhaust its request budget or restart while receiver publication is pending. Retain the validated continuation and exact pending bytes, finish authenticated receiver publication before acquiring more provider data, and publish partial fence, suite graph and final seal in order. Repository/profile discovery shares the original aggregate budget; current store, producer, stream, config and fact identities remain required throughout recovery.

Add paired read-only graph and authenticated receiver accessors, strict bounded continuation/publication codecs, safe private-file custody, and deterministic crash/restart, refusal and budget controls. The owning plan records source preparation separately from publication, installed adoption and external provider acceptance.

Validation: combined Core 36, GitHub 90 and CLI 158 cases passed; configured end-to-end controls include metered 41-suite acquisition and an actual disposable authenticated receiver. The CLI execution passed all 158 cases but its outer reporting step failed on period-containing test names; the retained original execution was reconciled using exact full identities, refusal controls and separately timed unchanged build-output verification. Root semantic review accepted that component without repeating unchanged product tests. The 534 qualification inputs matched the current-main source integration; later product-file changes convert 24 discarded XML comment markers to ordinary comments and repair the custody test fixture parent selection. Public signatures and production executable code are unchanged. The original full coherent run passed 1,209 Core tests and 714 of 720 CLI tests; all six CLI failures came from custody fixtures beneath shared /tmp, correctly refused by the production guard. Fixtures now select safe nonwritable ancestry and refuse unsafe alternatives; nine focused custody/configured/receiver recovery controls pass with complete source/runtime postchecks. The candidate is rebased onto current main with the merged dashboard source preserved. The full documentation-siting fixture passes 90 cases and the mutation protocol passes eight controls. The hosted release-notes fixture also exposed a pre-existing captured-manifest scan error. Its exact historical 0.102.0 exemption now matches the existing 0.91.4 evidence exemption; executable and adjacent-JSON duplicate controls remain strict. Captured manifests and runtime policy are unchanged. Routine eligibility and operation-boundary fixtures pass; required hosted/coherent checks remain required.