feat(k1): wire dormant control lease

docs/01_IMPLEMENTATION_PLAN.md

@@ -21,7 +21,7 @@ Each gate produces evidence and an explicit GO, PAUSE or BLOCKED result.
 | Stage 7 observation archive | GO (point/pose/telemetry contract) — durable catalog, recovery, capture-clock-bounded RRD preparation, archived metric time series, saved-session timeline and atomic playback are implemented |
 | Stage 7 recorded cameras | GO (contract), acceptance pending — acquisition-owned fMP4 archive and player are implemented/tested; one real archived K1 camera plus point-cloud session has not passed playback yet |
 | Plugin isolation | GO (laboratory control plane) — vendor backend/frontend and optional scene controls are plugin-owned; manifest/runtime descriptor parity, versioned handshake, lifecycle health and transport correlation fail closed while execution remains in-process |
-| K1 application control | PAUSE (offline execution gate complete) — exact five-batch response-barrier orchestrator passes the retained 10-request dialogue; the 36-byte application authority loads only from macOS Keychain; current publisher boundary is structurally write-disabled and never touches its sink; runtime wiring, physical START/STOP and durable save remain closed gates |
+| K1 application control | PAUSE (dormant runtime gate complete) — plugin v0.4.0 exposes operator-confirmed shadow arm/disarm/state; authority is held in a 15–300 s non-exportable lease and revoked on expiry, reprovision, acquisition preparation or shutdown; orchestrator is facade-owned, but no emission method/live sink exists and vendor writes remain false |
 | Stage 8 product storage | PAUSE — retention, replication, encryption, capacity monitoring and long-run browser/WASM stress remain deployment gates |
 
 USB project copying remains optional ground truth rather than a blocker for the
@@ -41,9 +41,14 @@ is separately attested through live DeviceStatus. A fixed macOS Keychain loader
 now reads the exact 36-byte authority without environment/file/browser fallback.
 The response orchestrator correlates required headers/results and rejects
 identity/profile drift. The installed publish boundary is a separate
-write-disabled type that cannot call its injected sink. Runtime wiring, a
-reviewed write-capable type and durable post-stop save remain unproven. The
-physical button remains the known-safe fallback.
+write-disabled type that cannot call its injected sink. A dormant coordinator
+is now wired into the XGRIDS facade and plugin manifest. Explicit operator arm
+loads the Keychain value into a bounded 15–300 second process-memory lease;
+expiry, disarm, reprovision, acquisition preparation and shutdown drop both the
+lease and orchestrator. Public state contains only lease timing/booleans. There
+is deliberately no batch-emission method, live MQTT sink or UI button. Keychain
+item provisioning, a separately reviewed write-capable type and durable
+post-stop save remain unproven. The physical button is the known-safe fallback.
 
 The Stage 6 live path uses a bounded raw-first bridge: loss in the visualization
 queue cannot discard MQTT evidence. The queue holds four preview messages;
@@ -262,7 +267,7 @@ useful stream is decoded or structurally identified.
 - firmware or internal-Linux analysis;
 - physical end-to-end shared-timeline playback for a newly archived session
   containing point cloud plus one selected K1 camera;
-- operator-owned Keychain provisioning/execution lease, authorized command transport
+- operator-owned Keychain item provisioning, separately reviewed emission transport
   and stable-artifact proof after the observed stop lifecycle;
 - long-running large-session WebViewer/WASM memory telemetry;
 - production retention, replication, encryption and cross-platform packaging.