docs(node): record R5 package and pending Ubuntu authentication

This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 13:08:01 +03:00
parent 5c4546a2a6
commit a0732386f1
@@ -63,3 +63,25 @@ build passed. Ruff, shell syntax and diff checks passed.
Node 0.8.3 is the replacement UI/host package. Installed optional K1
0.1.2+private.1 is retained. Exact artifact and installation acceptance follows;
a new fresh-cache UI connection, live streams and recovery remain pending.
## Prepared release
Source `5c4546a2a68052a7f871ecf6111728e0560d74e4` was built into
`mission-core-node_0.8.3_amd64.deb`: 109814334 bytes, SHA256
`fa8ce997aad75be29d03b1db78e1e4efe068cef6eed546f46fca9f6f027cc142`.
Its package provenance matches that source. Node TypeScript/production/Go build
and UI boundary validation passed. Transferred package and installer checksums
match; APT simulation selected one Node upgrade and zero removals.
The canonical Core serves the exact new frontend index, SHA256
`02cb6f8c3ffee93dd97130c551b2fbfb3dab144cec6e44efb29e8a9ef4ceb6b9`.
The release is retained in `private/releases/mission-core-node-20260907-r5`.
Owner screenshots, redacted UTC/monotonic manifest and validation logs are
hashed under `private/acceptance/k1-node083-20260907-core-ui`.
One Ubuntu GUI installer is open and awaiting owner sudo authentication.
The latest observed installed versions are still Node 0.8.2 and K1
0.1.2+private.1, both active. Installation and new UI hardware acceptance must
not be inferred from the package build. Git publication remains pending the
explicit owner reply to the prior automatic approval rejection of deployment
reports; no push workaround was used.