From 111fe3dcfb32794979e95ecf4e10093425f1ede3 Mon Sep 17 00:00:00 2001 From: DCCONSTRUCTIONS Date: Mon, 7 Sep 2026 10:57:56 +0300 Subject: [PATCH] docs(k1): record Node 0.7.1 installation and acceptance boundaries --- ...k1-lab-acceptance-and-node-continuation.md | 48 +++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/docs/audits/2026-09-07-k1-lab-acceptance-and-node-continuation.md b/docs/audits/2026-09-07-k1-lab-acceptance-and-node-continuation.md index db3af32..794b64c 100644 --- a/docs/audits/2026-09-07-k1-lab-acceptance-and-node-continuation.md +++ b/docs/audits/2026-09-07-k1-lab-acceptance-and-node-continuation.md @@ -60,3 +60,51 @@ the board owns Bluetooth, network observation, K1 commands and raw data. Ops direct tools are absent in this session. This local report is prepared for the K1 and Node cards; no Ops publication is claimed. + +## Release addendum: installation confirmed + +The observations above describe the pre-build checkpoint. The final source +commit is `63ea2bed672cd17251fc484560a58d0de2e1075c`, published to `origin/main`; +the local and remote branches were verified equal with a clean working tree. +Core UI was built and published to canonical port 8000. The backend was +replaced only after idle/completed acquisition and control, no pending cleanup +and no running operation had been verified. The replacement reports +`operational=true`; no alternate Mission Core backend was introduced. + +Package `mission-core-node_0.7.1_amd64.deb` contains 429546210 bytes and has +SHA-256 `83ea1cdc9aea598e92fae519124279c9583be56b37cafca049e7029e22a92ee7`. +Its provenance binds the source checkpoint, including K1 frontend files. Package +metadata, maintainer scripts, required runtime files and the transferred hash +were verified before installation. The owner completed normal Ubuntu +administrator authentication on the previously trusted Mini. At +2026-09-07T07:51Z, `dpkg-query` confirms 0.7.1; both `mission-core-node` and +`mission-core-k1` are active with no automatic restarts. Bluetooth and +NetworkManager are active, and the Bluetooth adapter is powered on. The original +Node identity and Core binding remain intact; Core receives the available idle +Bridge runtime. RealSense remains registered and configured, but its hardware +is currently absent from the board's USB inventory. Live RealSense acceptance +after this update is not claimed. + +The installed worker starts without an application credential, as designed; +discovery is available while control authority remains to be prepared. Transfer +of the existing macOS Keychain application key to the Mini's encrypted systemd +credential store was rejected before execution by automatic approval review: +explicit consent for that credential and destination is required. The owner +has been asked for that consent. No key was read or transferred. The prepared +import uses protected SSH stdin and an in-memory pipe, normal Ubuntu sudo +authentication, the installed root-only import helper, and an idle worker +restart. It does not transfer a Wi-Fi password or put secrets in command-line +arguments, environment variables, source files or logs. + +Direct Ops tools subsequently became available. Their startup rules, project +context and current cards were read through the direct MCP. Five release and +acceptance blocks were appended to K1 card #3, preserving all 29 existing blocks +and its historical state. Node card #76 received progress comment +`604aa523-b1a0-4e61-8452-35d5a0fcbf1f`; its frozen 26-block architecture baseline +was not changed. The prior successful-after-cache-clear checker, Ubuntu live +acceptance, credential readiness and board recovery checkers remain open. + +Next acceptance is one explicit Bridge workflow through the installed Node and +Core interfaces, with cache cleared before every hardware test as requested by +the owner. Camera/LiDAR output, the isolated live profile and board-side outage +recovery are not yet proved by this installation check.