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

Record staged K1 causal diagnostics release R8

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 14:16:18 +03:00
parent 4f715e41d2
commit 102e93796b
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/audits/2026-09-07-k1-causal-diagnostics-r8.md
+18
View File
@@ -42,3 +42,21 @@ monotonic collection timestamps and SHA-256 hashes under private/acceptance/
k1-node085-20260907-bluetooth-1355. Browser cache clearing for that attempt has
not been confirmed. No hardware commands were issued by the agent. The next
physical check remains through the owner UI after clearing browser cache.
## Prepared and staged release
Source 4f715e41d23a20c129111a4b550d1ccde2d311e4 produced Node 0.8.6
(109814516 bytes, SHA256
0d7e313dedefdb6609cfec5b6b7fa983d7886349255b19bb61e3f6a3201af916)
and private K1 0.1.5+private.1 (318107944 bytes, SHA256
9b271a418b7a64c336e70164d1592e41798afb29fc7de813abff026309772d53).
Node TypeScript/build, Go packaging and its UI boundary test passed. The
Design Guideline pin remains 5b882bc; existing application material is unchanged.
The private release is retained in
private/releases/mission-core-node-k1-20260907-r8, with previous releases kept.
Transfer checksums matched. APT simulation selected two upgrades and no
removals. Fleet reported an idle, disconnected K1 and the same terminal failed
attempt before the single Ubuntu GUI installer was opened. It awaits owner
sudo authentication. Installed versions, physical Bluetooth cause and
read-only control readiness remain pending, not accepted.