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

docs(k1): record R4 onboard installation and pending hardware acceptance

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 12:44:22 +03:00
parent d2dbfc9c85
commit 2f80507bc0
1 changed files with 34 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/audits/2026-09-07-k1-node-operation-identity-r4.md
+34 -1
View File
@@ -54,7 +54,7 @@ and confirmed empty scans and retain network/bootstrap/recovery regressions.
Focused Python bridge, installer, Fleet enrollment, BLE scanner and operation
journal suite: 73 passed. Core frontend suite: 789 passed, no failures or skips.
Build and installation acceptance is recorded below when completed.
Build and installation acceptance is recorded below.
Release versions are Node 0.8.2 and optional K1 0.1.2+private.1. Existing private
release bytes and application material are retained. This is a Node adapter
@@ -62,3 +62,36 @@ correction; no Rerun profile, protocol frame, MQTT recovery state machine or
shared lifecycle validator was modified. Physical Bluetooth discovery, Bridge,
live camera/LiDAR and interruption recovery still require fresh-cache UI
acceptance. No agent CLI hardware command is part of this test.
## Release preparation
Both packages use source `d2dbfc9c85a8375205626914232d7355ce24f30b`.
Core and Node TypeScript/production builds passed; Node UI boundary test passed;
Go package tests passed (cached). The canonical Core on 8000 is operational and
serves the exact new index, SHA256
`77e0ab03a271e3213d4aa12d3d7b91f75ad8d2d6b5dc8294263a47e91ab7cfc1`.
| Package | Bytes | SHA-256 |
| --- | ---: | --- |
| `mission-core-node_0.8.2_amd64.deb` | 109813510 | `1318a2ff45171d20b3aad677d7fec0e3866b5367672b0a254800e50aad468a19` |
| `mission-core-xgrids-k1_0.1.2+private.1_amd64.deb` | 318107248 | `3a883b1398718ea04b9d81e9632eaa64f37459dca19d262e4a362f29383c80d5` |
Provenance, the packaged adapter source and root:0600 private profile member
were verified. Transferred hashes match. APT simulation selected two upgrades
and zero removals. The private release is in
`private/releases/mission-core-node-k1-20260907-r4`; the redacted UTC/monotonic
acceptance manifest and hashed validation logs are in
`private/acceptance/k1-node082-20260907-core-ui`.
The owner entered sudo authentication in the one launched GUI installer. It
exited with code zero. Installed Node 0.8.2 and K1 0.1.2+private.1 both report
source d2dbfc9; the installed adapter contains the operation-ID conversion.
Node and K1 became active/running at 12:41:26 and 12:41:34 MSK respectively,
both with NRestarts=0. Core Fleet receives the new runtime through the retained
binding; it reports fresh/available/idle and permits scan-ble. No hardware
discovery is inferred from these readiness facts. The owner was asked to clear
Chrome cache again and repeat Find K1 through the Core Fleet modal.
Git publication remains pending explicit owner authorization after automatic
approval review rejected the preceding installation report `2fdf1d3` due to
internal deployment metadata and its destination. No push workaround was used.