isolate M4.7 worker shadow runtime

docs/22_MILESTONE_4_OBJECT_CENTRIC_RECORDED_REALTIME_CV.md

@@ -1172,7 +1172,7 @@ terminal, report and manifest ledgers; acceptance requires exactly `4,489`
 delivered frames with zero failed, stale, superseded, rejected or unavailable
 terminal outcomes.
 
-The new Worker package uses transition `m47-canonical-graph-shadow-v1`. It is a
+The first Worker package used transition `m47-canonical-graph-shadow-v1`. It is a
 separate deterministic artifact and does not relabel the accepted historical
 `m4-detector-shadow-v1` wheel. Its PowerShell runner verifies release files,
 inputs, dependency trees, disk reserve, pinned Worker/Triton predecessor and
@@ -1182,6 +1182,17 @@ the run and re-verifies the predecessor. Provider readiness and graph readiness
 are emitted separately. The production builder refuses a dirty worktree so an
 artifact cannot claim a Git revision which does not contain its wheel.
 
+The live audit on 2026-08-23 found both pinned historical Mission Core
+containers present with their exact identities but stopped. M4.7 therefore
+uses the additive transition `m47-canonical-graph-isolated-shadow-v1`: it does
+not start, stop or replace either historical container. The runner creates a
+private, no-public-port Triton candidate from the same digest and a separate
+one-shot graph candidate, binds the accepted model/evidence read-only, and
+removes both candidates on every exit path. It records and re-verifies the
+identity and running state of the historical E15 worker and Triton before
+accepting the run. This makes Worker 006 usable without touching the stabilized
+K1/Zarya connection path.
+
 Local contract, graph, result-sealing, artifact and historical-rollback tests
 pass. This is implementation evidence only. It does not claim that Worker 006
 has the pinned local-surface input, that preflight has passed, that the 4,489