fix(worker): deploy persistent runtime companions

docs/01_IMPLEMENTATION_PLAN.md

@@ -11,7 +11,7 @@ Each gate produces evidence and an explicit GO, PAUSE or BLOCKED result.
 | Prediction/evaluation boundary | GO — truth-free E41 predictor package/result are physically separate from E37 and reproduce E40 predictions exactly; the visible evaluator runs only after inference. |
 | Source-scoped quality | PAUSE — E40 visible engineering evaluation is 84.2466% presence, 84.2466% geometry association and 94.5205% freshness, with 11 high-severity failures, complete accounting and zero false-free claims. This is not a blind accuracy gate. |
 | Structural regressions | GO (bounded) — E42 passes predictor identity/order/chunk invariance and PointSlab order/SE(3) checks. Raw-producer and cross-route invariance remain unproved. |
-| Native pipeline telemetry | GO for producer/normalizer contract — lifecycle events and JSONL/MQTT sink boundaries exist and an E41 smoke run records real stage accounting. Durable Worker 006 MQTT wiring/deployment remains pending. |
+| Native pipeline telemetry | GO (durable Worker 006) — lifecycle events and JSONL/MQTT sink boundaries exist; the persistent worker writes to its existing D:-backed publish mount, host Telegraf tails with saved offset and publishes through the existing authenticated QoS 1 path. Real request `durable-native-acceptance-20260729-115418` produced native run `started → failed` after reaching the unavailable live-source boundary, and both documents were observed through broker → normalizer → Timescale query API with the same run/request identity. No broker credential or additional container entered the inference runtime. |
 | Evidence storage | MEASURED — E44 finds 525,471,092 logical bytes, 312,753,179 unique-content bytes and 1.680146× amplification across 14 E30–E40 roots. Exact-content references/deduplication precede any format migration. |
 | Future transfer | PREREGISTERED — E43 freezes same-K1/mount/calibration/firmware, required streams, connected-component split and independent label reveal. Capture and labels do not yet exist. |
 | E31 binding sensitivity | MEASURED — E45 closes accounting for 87/87 accepted correspondences and finds no material monotonic residual association with represented image radius, rig speed or pose age. It does not supply calibration-target truth or outer-fisheye coverage. |

docs/adr/0031-local-compute-contour-telemetry-plane.md

@@ -29,13 +29,26 @@ The existing Worker 006 containers were renamed in place to
 container identities were preserved, so this namespace migration did not restart the
 inference or perception runtimes.
 
-The compute-side native pipeline contract is now implemented. It emits
-`missioncore.agent-pipeline-telemetry/v1` lifecycle documents through an injected
-transport, and the telemetry normalizer preserves source, method, stage and stage-state
-identities in the normalized series key. The E41 runner has exercised the JSONL
-evidence sink against the immutable predictor package. This proves producer and
-normalizer compatibility; it does not claim that the durable Worker 006 process has
-been wired to the MQTT sink or deployed with this code.
+The compute-side native pipeline contract is implemented and deployed on Worker 006.
+It emits `missioncore.agent-pipeline-telemetry/v1` lifecycle documents through an
+injected transport, and the telemetry normalizer preserves source, method, stage and
+stage-state identities in the normalized series key. The E41 runner first exercised
+the JSONL evidence sink against the immutable predictor package.
+
+The durable path was then accepted on 2026-07-29 with real persistent-worker request
+`durable-native-acceptance-20260729-115418`. The request reached the actual live-source
+boundary and terminated because no K1 shadow source was open. Its native run
+`started` and `failed` documents were appended by the worker, tailed by host Telegraf,
+published on the contour pipeline topic and returned by the normalized Timescale query
+API with the same run/request identity. This is transport and lifecycle acceptance,
+not a successful perception-result or stage-performance claim.
+
+The acceptance also closed two deployment-unit defects found by the real request:
+the token-stdin launcher now installs its required `MissionCoreDockerNames.ps1`
+companion, and the perception runner updater atomically digest-gates
+`run_e15_shadow_inference.py`, `e15_shadow_runtime.py` and
+`pipeline_telemetry.py`. The existing perception container is still the only
+inference worker; broker credentials remain on the host Telegraf service.
 
 ## Decision