diff --git a/docs/audits/2026-09-07-k1-between-scans-r16.md b/docs/audits/2026-09-07-k1-between-scans-r16.md index 0a3c275..8130205 100644 --- a/docs/audits/2026-09-07-k1-between-scans-r16.md +++ b/docs/audits/2026-09-07-k1-between-scans-r16.md @@ -110,13 +110,24 @@ Node 0.8.12 → 0.8.13 and K1 0.1.12 → 0.1.13, with zero additions/removals. The existing safe-state pre-install guards remain unchanged. Fleet was online with idle acquisition before staging; unrelated inventory entries were retained. -The native “Mission Core · K1 R16” installer is open for owner-entered sudo. -Installation and physical acceptance remain pending. Once installed, clear -Chrome cache and test through the normal UI: connect, named scan, STOP through -confirmed completion, navigate away and return, then start another named scan -without a separate recovery action. Also inspect autofill colors and the live -scene corners. No browser/GPU visual acceptance is claimed from build/tests. +The owner entered sudo in the native “Mission Core · K1 R16” installer. +Post-install read-only verification confirms both packages are `install ok +installed`: Node 0.8.13 and K1 0.1.13. The Node service entered active/running +at 21:22:04 MSK on 2026-09-07; K1 entered active/running at 21:22:13 MSK. +Both report NRestarts=0. The bounded warning-or-higher journal since 21:22:00 +contains no entries. This verifies installed state independently of an installer +exit code, which the owner has not reported. + +After installation, canonical Core health remains HTTP 200, ok=true; Fleet +reports ndc-rover-006 online. Its K1 inventory projection is currently +online=false, verified=false after the service restart. This is not physical +connection acceptance. Clear Chrome cache and test through the normal UI: +connect initially, named scan, STOP through confirmed completion, navigate away +and return, then start another named scan without a separate recovery action. +Also inspect autofill colors and the live scene corners. Physical and browser/GPU +visual acceptance remain pending; no such acceptance is claimed from build/tests. Final canonical Core health: HTTP 200, ok=true. Port 8000 remains on the original -PID 88424; no backend on 8765. No Docker service or temporary application server -was started. The waiting installer is the only new owner-facing process. +PID 88424 at the pre-install check; no backend on 8765. No Docker service or +temporary application server was started. The installer was the only new +owner-facing process.