Project UTEL native-case and Rendering caller delivery

docs/roadmaps/2026-10-07-unified-development-roadmap-v3.md

@@ -49,7 +49,7 @@ Conditional work in section 6 is not automatically scheduled.
 
 | Feature and accountable owner | Remaining outcome | Entry or blocking join | Owning plan | Done |
 |---|---|---|---|---|
-| **UTEL operational collection — `.github` telemetry/Coordination** | Reconcile the observed existing 0.100.0 installation/selector under original effect identities, then qualify the current-only dispatch contract and fresh CI/delivery collection. Recover retained pending publications through their supported original-identity route. | 0.100.0 is published; HOST-01 install-only source is delivered. Immutable CI profile classification and strict native PR/head/base/repository association are delivered in [#4344](https://github.com/FS-GG/.github/pull/4344); genuine target-case qualification and installed collection remain open. A verified published-DLL version-only call passed, but installer/shim provenance, original installed effects and receiver recovery remain unresolved. Preserve historical records, unknown operations and incomplete dispatch/usage coverage. | [Operational completeness](utel-operational-completeness.md), [local store](utel-local-telemetry-store.md), [correctness](utel-01-telemetry-correctness.md) | No |
+| **UTEL operational collection — `.github` telemetry/Coordination** | Reconcile the observed existing 0.100.0 installation/selector under original effect identities, then qualify the current-only dispatch contract and fresh CI/delivery collection. Recover retained pending publications through their supported original-identity route. | 0.100.0 is published; HOST-01 install-only source is delivered. Immutable CI profile classification and strict native PR/head/base/repository association are delivered in [#4344](https://github.com/FS-GG/.github/pull/4344); genuine target-event association, immutable profile and disposable replay controls are delivered in [#4349](https://github.com/FS-GG/.github/pull/4349). A coherent collector successor and installed collection remain open. A verified published-DLL version-only call passed, but installer/shim provenance, original installed effects and receiver recovery remain unresolved. Preserve historical records, unknown operations and incomplete dispatch/usage coverage. | [Operational completeness](utel-operational-completeness.md), [local store](utel-local-telemetry-store.md), [correctness](utel-01-telemetry-correctness.md) | No |
 | **Routine activity, review and usage coverage — programme/telemetry owners** | Collect planning, implementation, review, validation, delivery, operations and repair spans; submit reviews for settled attempt populations; reconcile native usage with explicit unknowns; continue CI/delivery reconciliation. Every efficiency view exposes coverage, freshness, unresolved observations and its denominator. | Reliable collection and actual settled populations. Overlapping queue intervals cannot prove human idle time or critical-path delay. Delivery counts cannot prove completed features or adoption. | [Observation guidance](../../.agents/skills/work-programme/references/observation.md), [efficiency measurement](process-efficiency-telemetry.md) | No |
 | **V2-EFF-01.2–.6 — telemetry, dashboard and receiver owners** | Qualify remaining canonical measurement/correction and completion-assessment behavior; install the coherent schema-14/Host-5 route, migrate the store, enroll supported providers, deploy matching dashboard/feed and run calibration plus a bounded live pilot. | Reuse delivered schema-14 and Responses source and published coherent 0.100/Host 0.5. Actual installation, migration, provider execution and end-to-end collection remain separate. | [Efficiency delivery plan](process-efficiency-telemetry.md), [dashboard](utel-telemetry-dashboard.md) | No |
 | **V2-PROC-01.1–.8 — Coordination; SDD/FsQuint consumers** | Finish library evaluation including error-path exit/cleanup; qualify shared I/O/deadline contracts, routine adapter and Linux containment, then publish, adopt selected consumers and consolidate proven replacements with a benefit review. | Resume retained evaluator/source work. Contract selection precedes routine/Linux implementation; native containment needs its own custody and resource profile. | [Shared process supervision](2026-10-05-shared-process-supervision.md) | No |
@@ -58,7 +58,7 @@ Conditional work in section 6 is not automatically scheduled.
 | **SVG-RELEASE-D — producer and workspace owners** | Close remaining public Wizard/full installed workspace and selected activation outcomes; qualify any later single-lifecycle default separately. | Reuse public Rendering 0.32.1 and Templates 0.18.1 and the Templates-only receiver. A Templates-only pass does not close full Wizard/Release-D adoption. | [Release D](svg-release-d.md), [coherent receiver dependency window](svg-coherence-and-instancing-01.md#svg-coherence-018--wizard-coherent-099-dependency-window) | No |
 | **SVG-COHERENCE-01.3–.8 — Rendering/Templates; product consumers** | Complete realistic repeated-glyph software research, affected shared reconciliation/performance changes, integrated reference, consumer candidates, one consolidated host-GPU batch, then remaining publication/adoption/removal. | Instance command-stream fixtures and controls are delivered in [Rendering#1402](https://github.com/FS-GG/FS.GG.Rendering/pull/1402), with native packed-browser checks passing. Public screening counters and raw-sample instrumentation are delivered in [Rendering#1403](https://github.com/FS-GG/FS.GG.Rendering/pull/1403), with native packed-browser checks passing; measured realistic software/performance evidence still precedes the late host batch; wider perf/GPU conclusions and publication/adoption remain open. Product-specific acceptance is in the games roadmap. | [Coherence and instancing](svg-coherence-and-instancing-01.md) | No |
 | **GAME-BOX2D-01 adoption / GAME-PORTAL-01 P3 — Game/Rendering/Templates** | Qualify remaining presentation/interpolation performance-release evidence, fresh generated-product opt-in consumption and preserving retained adoption; integrate applicable examples in the Game template. | Public Game 0.17.0 and P1/P2 are inputs. [P3 source and eight tests landed](https://github.com/FS-GG/FS.GG.Game/pull/707). [Game#708](https://github.com/FS-GG/FS.GG.Game/pull/708) qualifies the actual package-only presentation/CLI against seven public packages, with unchanged locked restore and passing entrypoint checks. [Game#709](https://github.com/FS-GG/FS.GG.Game/pull/709) delivers the stock-counter smoke mode and twenty raw samples over 24,000 views; historical comparison and a performance-release verdict remain open, alongside generated-product and retained adoption. Browser/Fable physics and rollback limits require explicit qualification; do not imply cross-area contact solving. | [Box2D](game-box2d-physics.md), [portals](game-area-portals.md) | No |
-| **FABLE-ADOPT-01 shared reference / GAME-TEMPLATE-01 — Rendering/Game/Templates** | Consolidate reusable completed games work into producer APIs and the installed `fable-game` reference; qualify remaining WASM/example composition, publication and clean/retained creation. Section 3 specifies coverage. | Reuse the accepted inventory/disposition and delivered local/external reference slices, including [Templates#682](https://github.com/FS-GG/FS.GG.Templates/pull/682) command-outcome recovery controls. [Templates#683](https://github.com/FS-GG/FS.GG.Templates/pull/683) aligns the hosted receipt with eight cases per browser and runs static controls before costly qualification. Source/native checks pass; the caller pin and actual example/WASM/browser composition, publication and fresh/retained adoption still require acceptance. Producer changes require reproducers; product authority stays local. Product pilots/removal belong to the games roadmap. | [Staged adoption](2026-10-01-staged-fable-game-adoption.md), [disposition](evidence/fable-adopt-01.1-inventory-disposition-20261001.md) | No |
+| **FABLE-ADOPT-01 shared reference / GAME-TEMPLATE-01 — Rendering/Game/Templates** | Consolidate reusable completed games work into producer APIs and the installed `fable-game` reference; qualify remaining WASM/example composition, publication and clean/retained creation. Section 3 specifies coverage. | Reuse the accepted inventory/disposition and delivered local/external reference slices, including [Templates#682](https://github.com/FS-GG/FS.GG.Templates/pull/682) command-outcome recovery controls. [Templates#683](https://github.com/FS-GG/FS.GG.Templates/pull/683) aligns the hosted receipt with eight cases per browser and runs static controls before costly qualification. [Rendering#1404](https://github.com/FS-GG/FS.GG.Rendering/pull/1404) pins the caller and consumer to that protected Templates source; native checks pass. Actual 24-case hosted qualification and remaining example/WASM composition, publication and fresh/retained adoption still require acceptance. Producer changes require reproducers; product authority stays local. Product pilots/removal belong to the games roadmap. | [Staged adoption](2026-10-01-staged-fable-game-adoption.md), [disposition](evidence/fable-adopt-01.1-inventory-disposition-20261001.md) | No |
 | **WASM-SHARED-01 remaining producer compatibility / .7 — Game** | Qualify the additive SC2 compatibility successor and genuine installed guest SDK/profile acceptance where still missing; support remaining consumer joins and retire only proven superseded duplication. | Reuse the connected published 0.2.0 boundary and later native publisher evidence in the owner plan. Browser deadlines do not prove deterministic instruction fuel; each adapter retains its wire/ABI and native authority. Product adoption is in the games roadmap. | [Shared WASM](2026-10-02-shared-wasm-foundation.md) | No |
 | **LEARN-01.2/.4–.5 / Akka orchestration — Coordination/telemetry/receiver owners** | Complete causal-declaration receiver and producer projection, then qualify publication and receiver-first adoption. Verify served Manager/runtime closure, inactive persistent-v3 images and genuine receiver grant/turn/capture/restart/cleanup; establish census/shared costs and enrollment, then a locked dataset or truthful stopped-window comparison. | Actor-owned durable causal admission, bounded committed-intent census and native identity joins are delivered in [Coordination#962](https://github.com/FS-GG/FS.GG.Coordination/pull/962), with local PostgreSQL composition and native checks passing. Exact retained-byte receiver projection and installed acceptance remain open. Reuse accepted O0–O3/Akka core; installed runtime, custody, cgroup/UID and two cold-image qualification precede activation. Source delivery supplies no live census, cost or critical-path claim. | [LEARN](2026-09-12-095059-stable-policy-orchestration-and-statistical-learning.md), [actor observation](https://github.com/FS-GG/FS.GG.Coordination/blob/main/docs/roadmaps/learn-01-actor-observation.md), [persistent-v3 receiver](learn-c2-persistent-receiver-v3.md) | No |
 | **COORD-BOARD-V2-01 remaining .4–.6 — `.github`/SDD/Templates** | Reconcile current open population and delivered-history disposition; finish carryover/consumer adoption and published fresh/retained workspace qualification. | Refresh actual issue/project facts. Historical four-target bindings cannot establish currentness after a target closes. Reuse existing bounded refresh and installed `check-board` qualification. | [V2 board design](../coordination/2026-09-29-coordination-v2-board-design.md) | No |