Qualify the first installed facts-and-coverage provider-to-browser journey #4707

Owner: Programme /root is accountable for intake and owner recovery; implementation ownership, existing branches and original attempts are preserved; this intake does not dispatch work. Programme /root accountable; existing dashboard/telemetry application owner owns projection/browser assertions; Home installation owner supplies its distinct receiver operation. Preserve each current owner.

Done when: One genuine provider item traverses the exact compatible installed receiver/store, sanitized projection and actual browser view with facts and coverage matching canonical records and privacy/public allowlists. Missing usage/provisional status remains truthful. Reuse the UTEL durable receipt supplier result without claiming its guarantees again; record exact installed artifact/configuration and browser evidence.

Current deliverable: Accepted Host successor source [PR #4782](https://github.com/FS-GG/.github/pull/4782), exact source `74cbd6f0b1b598d48556eb854c4ba6a3c3abda54`, original candidate39574162631/a1/artifact12334065598 and preflight39578047585/a1 retain their scopes. Original [publication39580298871/a1](https://github.com/FS-GG/.github/actions/runs/39580298871) has now completed successfully. Independent readback verifies its native run/job, tag/source, promoted [Host0.8.0 release](https://github.com/FS-GG/.github/releases/tag/telemetry-host/v0.8.0) and exact assets, public NuGet normalized payload, Authority protection and journal14 generation17 with all eight protected states marked verified. The maintained independent effect reader nevertheless remains partial: five effects verify, while GitHub org-package GET403 leaves `github`, `publication-journal-asset` and `promote` independently Unknown through their org-byte dependency. Full independent publication acceptance is not claimed. Programme/root separately retired the operation-specific source hold; this releases no inherited Unknown. The existing #4707 owner /root/sc2_prerequisite retains implementation/publication reconciliation. Host0.7/journal13 and held0.6/journal12 originals remain preserved; Home installation,4705 genuine receipt and complete provider-to-browser acceptance remain open. Programme/root has now selected the same owner’s concrete four-path hosted read-only source continuation: extend the existing feed-readiness workflow with a closed Host0.8 org-artifact observation using its existing repository token and read permissions. Source preparation is selected and awaiting guarded Ready/dispatch; no new hosted observation has run.

Next action: After Programme/root independently reads back guarded Ready and dispatches the existing owner /root/sc2_prerequisite, implement the selected source continuation in one ordinary follow-up PR to closed PR #4782. The four paths are `.github/workflows/release-successor-feed-readiness.yml`, `scripts/telemetry-host-published-org-read.py`, `tests/telemetry-host-published-org-read/run.py` and `tests/release-successor-candidate/run.py`. Preserve the default coherent-set absence branch; add only the closed Host0.8 read branch, fixed published source/tag/manifest/journal bindings, one bounded org-package GET, unchanged verifier and one bounded genuine evidence artifact. Keep existing contents:read/packages:read; no new workflow, credential grant, token export or publication route. Apply focused static workflow mutation and fake transport/verifier controls, independent exact-source review and normal required CI before protected merge. Programme/root separately admits one first-attempt hosted read after accepted source delivery. Reuse original publication39580298871/a1; no candidate/publisher rerun, journal reset or automatic feed-read retry follows. Home4516 still owns the distinct authenticated receiver/cutover, exact installed artifact/configuration/store provenance, current-data fence, backup and recovery. After independent publication and installed receiver acceptance, reuse4705’s genuine canonical receipt for the complete sanitized provider-to-browser facts, coverage and privacy journey.

Blocked on: The executable hosted source route is now selected; lack of a Home-side package-read operator does not block that source preparation. Live independent org-package byte acceptance remains incomplete after the retained403 and cannot be inferred from source tests, workflow permission declarations, native promotion or journal states. Full Delivery acceptance still requires the genuinely published compatible Host tuple, exact installed receiver/configuration/store custody,4705 genuine canonical receipt, actual sanitized projection/browser facts and truthful coverage/privacy, plus Home-owned cutover/backup/recovery. Published Host0.7/journal13, original Host0.6/journal12 Unknown and inherited439/46 holds remain unchanged. Guarded Ready/dispatch, source qualification, the eventual hosted read and whole Delivery acceptance are distinct.

Acceptance evidence: [Protected merge 74cbd6f0](https://github.com/FS-GG/.github/commit/74cbd6f0b1b598d48556eb854c4ba6a3c3abda54) was independently read back with tree `b477c03e72523d95732a867194c6ade0c579d9c3`, identical to reviewed PR head `e123bf83a518226b1ac25f896fbe50c222e2987d`. Final native checks:82 passed,4 skipped. [Host qualification](https://github.com/FS-GG/.github/actions/runs/39567814143) passed, including all27 installed-package fixture tests and actual browser/isolated-restore checks; [coordination qualification](https://github.com/FS-GG/.github/actions/runs/39567813969) passed without retry. Independent source and Atlas closure reviews passed; the protected candidate/publisher/read-gate bytes and all10 prepared controller helpers match their reviewed source identities. The prior failed attempts remain preserved at their original scope. Atlas record `platform/independent-host-embedded-consumer-release-boundary` captures the source/runtime boundary. Full #4707 acceptance and parent [#4640](https://github.com/FS-GG/.github/issues/4640) remain open; no parent completion or publication/Home acceptance is inferred.

Accepted candidate and preflight milestone: original [candidate39574162631/a1](https://github.com/FS-GG/.github/actions/runs/39574162631) succeeded against exact source `74cbd6f0b1b598d48556eb854c4ba6a3c3abda54`. The mandatory read-first gate passed before candidate work; its original authenticated feed/source observations have only that operation's scope and do not erase the older local org-feed403 Unknown or establish fresh publication occupancy. Root independently authenticated artifact12334065598/archive SHA256 `56dda6d46dc0b9114cf0ca2266042f36f57fd78ca8845a636b786637ebba27bd` and the unchanged verifier's three-file result: package `FS.GG.Telemetry.Host.0.8.0.nupkg` SHA256 `44273495ed12083b0c9762818ca0ef5688418e6fbc46bde9f2565b400c5aba89`,27 PASS/0 FAIL, journal schema14, exact producer payload `sha256:f036808546d75e62e9fdf5fc8de518a0e4de055efa3ef6e742db8dd1ee1802ee`, and preserved manifest/package evidence. Original local HTTP415 retrieval and archive-layout failures remain failed local custody observations; separately bounded read/verification corrected custody without retrying the hosted candidate. Original [preflight39578047585/a1](https://github.com/FS-GG/.github/actions/runs/39578047585), job119148403657, bound that same run/artifact/archive with `continue_failed_original=false` and `publish=false`; the actual publisher step succeeded at09:37:20Z, NuGet login was skipped, prepared archive/package and producer payload equality passed, and no journal/tag/feed/release changed. The original local unique-result log-parser refusal remains retained; the bounded evidence review resolved parsing of this original run without workflow retry. Root accepted the preflight at09:41:05Z. Publication, installed Home adoption, full #4707/#4640 acceptance and inherited439/46 holds remain unchanged.

Original publication and partial independent readback milestone: [publication39580298871/a1](https://github.com/FS-GG/.github/actions/runs/39580298871), job119155967025, completed successfully against source74cbd6f0b1b598d48556eb854c4ba6a3c3abda54; no rerun or redispatch occurred. Read-only independent inspection verifies tag/source and promoted release419394647 at `telemetry-host/v0.8.0`, exact release package/manifest/journal asset bytes and their original correspondence, normalized public NuGet producer payload `sha256:f036808546d75e62e9fdf5fc8de518a0e4de055efa3ef6e742db8dd1ee1802ee`, and protected journal14 generation17 (all eight states verified). Candidate/archive/package/payload identities and all earlier local failures remain unchanged. Independent GitHub org-package bytes returned HTTP403; actual maintained effect results are five verified (`tag`, `draft`, `nuget`, `package-asset`, `manifest-asset`) and three Unknown (`github`, `publication-journal-asset`, `promote`) because they depend on that unavailable org observation. Native promoted-release/journal evidence does not override those independent byte checks. Scoped local collection/outer retirement completed; full publication and installed Home/provider/browser acceptance remain unaccepted, and no historical0.6/journal12 or439/46 hold is released. Root owns parent4640 reconciliation separately.

Historical current fields before accepted PR #4782 source milestone (preserved):

> Current deliverable: Completed #4679/PR4685 remains accepted at its source scope. Programme/root has now admitted the existing scoped Delivery's independent Host successor source preparation to /root/sc2_prerequisite. The owner acknowledged an original1800-second source-only profile at2026-10-21T06:44:54Z, CPU4/memory2GiB, based on protectedf8b2088e. Published Host0.7 predates the accepted unassigned-usage browser feature; no new package or installed adoption is yet claimed.
> 
> Next action: The admitted same source owner prepares a fresh independent Host successor coordinate after actual absence checks, its candidate/publisher/journal bindings, closed qualification and actual-package passive-display assertions. Preserve accepted4679/PR4685 and existing dashboard/Home owners. Root separately admits hosted qualification, publication and exact installed adoption after review; complete the genuine provider-to-browser acceptance only with the retained UTEL receipt supplier and actual receiver/browser evidence.
> 
> Blocked on: No Home access prerequisite blocks this admitted source preparation. Whole Delivery acceptance still requires the compatible genuine published Host tuple, exact installed adoption and authenticated Home-owned receiver/store/cutover plus4705 genuine receipt and actual projection/browser evidence. Historical Host0.6/journal12 uncertainty and Host0.7/journal13 publication remain immutable; no runtime, publication, host operation or historical retry follows from this source admission.
> 
> Acceptance evidence: Root source admission2026-10-21: existing4707 owner /root/sc2_prerequisite acknowledged original1800 seconds, CPU4/memory2GiB and isolated source-only scope on protectedf8b2088efcf03f96252dcdd92f8bda7b84983f24; successor proposal SHA2560349cb24549de092147d949ddd7688fb4bb19e0131addc3c01d354f107fa23af. No coordinate, package, host adoption or complete runtime acceptance is inferred. process-efficiency-telemetry.md: V2-EFF-01.2–.6 and facts-first dependency order; utel-telemetry-dashboard.md: facts-first and privacy; completed #4679/PR4685. Preserve accepted parent source/publication evidence at its original scope. Record actual PR/head, selected artifact/profile/operation, independent scoped result and native acceptance here after they exist; this draft supplies none. Full original parent promise and history remain authoritative at https://github.com/FS-GG/.github/issues/4640; broader programme outcome: https://github.com/FS-GG/.github/issues/4640. This bounded source/receiver result does not close either broader promise. Accepted decomposition design: https://github.com/FS-GG/.github/issues/4701 and `docs/coordination/2026-10-19-board-clearing-lifecycle-design.md` (owning source plan; publication remains separate).


Historical current-field boundary before PROC/LEARN/UTEL priority reconciliation (preserved verbatim):

> Current deliverable: Existing installed telemetry/projection/dashboard/feed receiver and browser journey; source #4679/PR4685 remains completed and is not reimplemented. <!-- fsgg:board-lifecycle-delivery/v1 key=facts-provider-browser parent=FS-GG/.github#4640 -->
> 
> Next action: Join the selected compatible coherent/Host publication and installed provenance to UTEL receipt delivery, then qualify the actual projection/browser path. Fresh-read the existing Home source/delivery disposition before repeating any access blocker.
> 
> Blocked on: Real authenticated receiver ingestion and compatible current package/cutover joins are still required. Native host authority is Home-owned; the browser owner cannot infer it from source tests. Publication and installed adoption remain separately admitted.



Root source decision2026-10-21: prospective Host0.8.0 and journal14 may be bound in reversible SOURCE preparation while org-feed occupancy remains explicitly Unknown after existing-token REST/v3 reads returned403. This does not assert coordinate availability. Default-disabled publisher/effect gates remain; no candidate or publication is admitted until authoritative fresh coordinate/journal/source checks succeed. A conflict requires a reviewed prospective source-coordinate change before any candidate. Original Host0.7/journal13 publication and Host0.6/journal12 Unknown remain unchanged. Existing source owner and original1800-second source window remain; no clock reset or new runtime authority follows.


<!-- root-selected-candidate-readfirst-20261021 -->
### Programme/root source decision: existing candidate read-first gate — 2026-10-21

Authority and provenance: Programme/root selects this bounded source repair under the user's instruction to prioritize PROC, LEARN and UTEL, finish current safe operations and pursue their nearest concrete unblockers in parallel. This follows review of the existing candidate ordering and its repository-token capabilities; it does not rely on a proposal's assertion of approval. The accountable source owner remains the existing #4707 owner and PR #4782.

Selected source scope: place a mandatory closed, bounded, read-only feed gate immediately after exact checkout in the existing release-telemetry-host-successor-candidate.yml, before SDK setup, tests, restore/browser work, build, pack and candidate archive creation. Reuse maintained NuGet version semantics and authenticated index policy; verify both indexes with known 0.7 predecessor readability, normalized absence of prospective 0.8, exact package absence, actor/attempt/ref/source bindings and unchanged protected main. Refuse unreadable, redirected, oversized, malformed, occupied, contradictory or stale observations before candidate work. Retain later CLR version checks, existing qualification/archive contract and all required CI. No new observer workflow, dispatch input, optional mode, credentials or publication route is selected.

The four source paths are .github/workflows/release-telemetry-host-successor-candidate.yml, scripts/telemetry-host-candidate-read-gate.py, tests/telemetry-host-successor/run.py and docs/coordination/telemetry-host-release.md. Pipeline preflight uses static ordering/mutation checks and fake transport controls proving good input reaches the existing path and every refusal prevents dependent work. One independent exact-candidate source review and final required CI remain necessary. Previously accepted Host package/browser/restore checks retain their exact original scope and head.

Narrow supersession of the earlier coordinate ruling: authenticated feed absence may be established by this mandatory first gate of a separately admitted, first-attempt existing candidate invocation. Candidate qualification, packing and archive creation remain prohibited until that gate actually passes. This changes only the timing of feed observation; it does not assert absence now or admit a workflow invocation. Before any later invocation, Programme/root must separately verify accepted exact source, actual tag/release occupancy, current Authority journal14 destination/protection and the operation's complete resource/custody prerequisites. The repository token's cross-repository Authority and private draft-release visibility are not assumed. A source literal for journal14 is not native absence evidence.

No candidate, publisher preflight, publish, Home cutover, credential change or native runtime is admitted by this source decision. Local org-feed HTTP403 remains Unknown. A failed future gate retains its original invocation and does not grant rerun or automatic coordinate changes; a package access failure yields the concrete existing Manage Actions access operator question. Published 0.7/journal13, original 0.6/journal12 Unknown, all inherited439/46 holds and the full #4707/#4640 acceptance remain unchanged. Source merge, publication, installed receiver/store custody, #4705 receipt and real private dashboard recovery are separate assertions.


Natural source-knowledge closure for the selected read-first repair: Programme/root permits the same #4707 owner/PR to capture one concise superseding version of platform/independent-host-embedded-consumer-release-boundary, preserving the original immutable 3dfcea4e record. The generated owner record and identical two seed copies, the existing docs/atlas/catalog.json and .agents/.claude Atlas seed catalogs, and registry/driver-skill-manifest.json are the only additional closure paths. Use the maintained capture/staging route, cite the actual source commit, and run the cheap assembled closure checks. Record the selected source contract and remaining runtime gates; do not claim publication, deployment or successful candidate operation. This natural capture stays within the original source operation and changes no runtime/effect authority.


Historical current fields before selected hosted org-read source continuation (preserved verbatim):

> Current deliverable: Accepted Host successor source [PR #4782](https://github.com/FS-GG/.github/pull/4782), exact source `74cbd6f0b1b598d48556eb854c4ba6a3c3abda54`, original candidate39574162631/a1/artifact12334065598 and preflight39578047585/a1 retain their scopes. Original [publication39580298871/a1](https://github.com/FS-GG/.github/actions/runs/39580298871) has now completed successfully. Independent readback verifies its native run/job, tag/source, promoted [Host0.8.0 release](https://github.com/FS-GG/.github/releases/tag/telemetry-host/v0.8.0) and exact assets, public NuGet normalized payload, Authority protection and journal14 generation17 with all eight protected states marked verified. The maintained independent effect reader nevertheless remains partial: five effects verify, while GitHub org-package GET403 leaves `github`, `publication-journal-asset` and `promote` independently Unknown through their org-byte dependency. Full independent publication acceptance is not claimed. Programme/root separately retired the operation-specific source hold; this releases no inherited Unknown. The existing #4707 owner /root/sc2_prerequisite retains implementation/publication reconciliation. Host0.7/journal13 and held0.6/journal12 originals remain preserved; Home installation,4705 genuine receipt and complete provider-to-browser acceptance remain open.
> 
> Next action: The concrete operator read-package proposal for the already-published Host0.8 tuple is now prepared by the existing #4707 owner /root/sc2_prerequisite and reviewed by Programme/root. Its next step awaits the existing authorized environment/operator response, requested by Programme/root, to address the exact GitHub org-download403 before any separately admitted read-only reconciliation. Reuse original publication39580298871/a1 and its retained artifact/effect identities; no rebuild, publisher redispatch, workflow retry, journal reset or automatic feed-read retry follows. Programme/root reviews that proposal and the actual operator capability before further action. In parallel, retain the existing Home4516 operator/custodian request for a legitimate authenticated bounded service/application route and exact installed receiver/configuration/store provenance, current-data fence, backup/recovery and compatible cutover facts. Home's LEARN fixture admin profile is not UTEL installation authority. After independent publication and installed receiver acceptance,4705 still supplies the genuine durable canonical receipt;4707 must reuse that receipt for actual sanitized provider projection/browser facts and truthful coverage/privacy. No additional product source defect was identified as a prerequisite for this selected journey.
> 
> Blocked on: Source preparation is accepted; Home access did not block that source slice. Complete Delivery acceptance still requires a genuinely published compatible Host tuple, exact installed artifact/configuration and receiver/store custody, the #4705 genuine canonical receipt, and actual sanitized projection/browser facts and coverage with truthful missing/provisional usage and privacy allowlists. Home owns its distinct authenticated receiver/cutover, backup and recovery operation. Local org-feed403 remains Unknown until the separately admitted gate establishes its own facts. Published Host0.7/journal13, original Host0.6/journal12 Unknown and inherited439/46 holds remain unchanged; source CI does not satisfy publication, remote adoption or recovery.