diff --git a/docs/roadmaps/2026-10-07-unified-development-roadmap-v3.md b/docs/roadmaps/2026-10-07-unified-development-roadmap-v3.md
index 0b7936513..4662dc9b1 100644
--- a/docs/roadmaps/2026-10-07-unified-development-roadmap-v3.md
+++ b/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. 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-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 |
 | **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 |