fix(worker): deploy persistent runtime companions

This commit is contained in:
DCCONSTRUCTIONS
2026-07-29 14:57:34 +03:00
parent 9db39347bd
commit 611853d3af
6 changed files with 193 additions and 24 deletions
@@ -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