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

Record installed wireless steps and diagnostic release R6

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 13:35:25 +03:00
parent d7986cb62f
commit 06d216ac4a
1 changed files with 28 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/audits/2026-09-07-k1-wireless-steps-r6.md
+28
View File
@@ -64,3 +64,31 @@ installation and owner UI acceptance must be recorded separately. Private
screenshots, observations, UTC/monotonic manifest and hashes are retained under
private/acceptance/k1-node084-20260907-core-ui. Cache clearance is not yet
explicitly confirmed for the preceding owner observation.
## Delivered and installed
Source `d7986cb62f2fad01f4a37faab10d971eaf29f266` produced Node 0.8.4
(109814576 bytes, SHA256
`85b2ff1b101d02c55ac99a80aac706c317054884665decd38c6ff4f6d911c628`)
and private K1 0.1.3+private.1 (318107598 bytes, SHA256
`3893d8c28e4af8cf751861d7a307ee1e6a744f174083fe3ffffb777c33bc0c46`).
The private release is retained as mission-core-node-k1-20260907-r6. Transfer
hashes matched and APT simulation selected two upgrades without removals.
The owner entered sudo in the Ubuntu GUI; the installer exited with code 0.
Installed versions and both provenance base commits match this source. Node
and K1 are active/running with zero restarts, started at 13:31:04 and 13:31:12
MSK respectively. The old application credential and Fleet binding are retained.
Core on 8000 remains operational and serves the exact new index, SHA256
`f8e1241271f46192ec89385ee32e16d9b322b5445bc04e97eb70e186571abd46`;
there is no Mission Core listener on 8765. Node UI boundary test also passed.
The Ubuntu window is a separate ephemeral WebKit view; closing and reopening it
loads the new frontend without restarting the background services. An already
open window does not prevent updated service code from running.
The owner has been asked for a fresh-cache Chrome discovery/selection/connection
check so the new trace can establish the Bluetooth failure origin. That UI test,
successful Bridge, live camera/LiDAR and recovery are still pending. No agent
CLI BLE/MQTT experiment or in-app browser cache workaround was used. Both
implementation and this report are local commits; the earlier automatic review
block on Git publication of installation reports remains unresolved.