SILVER/NODEDC_MISSION_CORE
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Record inspected R16 artifacts and pending onboard acceptance

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 21:22:41 +03:00
parent c6693d6f44
commit 0e9faa6824
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/audits/2026-09-07-k1-between-scans-r16.md
+29
View File
@@ -91,3 +91,32 @@ focused tests above). Installer/package lifecycle: 14 passed. Core TypeScript
and production build passed (8.29 s). Ruff and whitespace checks passed.
Design Guideline pin: `26a1bf72a2a32b002e51f910e8faa300333bb6c3`.
R16 package versions: Node 0.8.13 and K1 0.1.13.
### Built and staged packages
Source commit: `c6693d6f442e0d2bb4ea3c5710db7af44d41b667`. Node production
build/typecheck passed. Both Debian archives were streamed and inspected:
regular files/directories only, no unsafe paths or private application key,
matching source provenance. All K1 per-file hashes matched its provenance;
`application_material_included=false`. Node provenance matches the pinned DG.
- `mission-core-node_0.8.13_amd64.deb`: 109838014 bytes; SHA-256 `d5571c956f305ee658a9119d7afeecfb47c99a2aa9dffad37ad2ba9b5e25e592`; 71 regular payload files.
- `mission-core-xgrids-k1_0.1.13_amd64.deb`: 318115794 bytes; SHA-256 `0cb5826f6c452189c19d69291552492da56bb88b08715fddff8c31eb587a7429`; 150 regular payload files.
The immutable R16 directory is staged at
`/home/dcsudo/Загрузки/NDC/mission-core-node-k1-20260907-r16/` on the authorized
Ubuntu board. Both remote checksums passed. Apt simulation upgrades exactly
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.
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.