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

Record R10 release hashes and remaining acceptance gates

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 15:32:56 +03:00
parent 92b60de945
commit 7ce09eabcd
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-node-preview-r10.md
+28
View File
@@ -88,3 +88,31 @@ All 801 frontend tests, Core TypeScript and production build pass. Release
hashes, installation readback and owner fresh-cache UI acceptance are recorded
below when observed. Local synthetic
checks do not establish camera decoding or live stream recovery on the BK.
## Release prepared
Source: 92b60de945e000c20b370c07802c5eedc12d310a. The Design Guideline pin is
unchanged at 5b882bc3d9b13a86e6c26111ef5ded687ea3a2fc. Node UI/Go/Debian build
and the additional Node UI boundary test pass.
| Artifact | Bytes | SHA-256 |
| --- | ---: | --- |
| mission-core-node_0.8.8_amd64.deb | 109816486 | 1df3ff4216d7311cb4967609d3ed829729fa7e01b713cdfb706aef5df99daae1 |
| mission-core-xgrids-k1_0.1.7+private.1_amd64.deb | 318109018 | 48af45db2fa1d2f40285d7d25a563f22189cb9dd0f92627c5a94a6ec70631002 |
The immutable private R10 release was copied to the same authorized BK.
All remote SHA256SUMS match. Apt simulation selects exactly two upgrades,
zero new packages and zero removals. The bounded GUI installer is open on
Ubuntu; owner sudo authentication and installed R10 readback are pending.
The Core frontend on port 8000 already serves the rebuilt UI. The browser
tool exposes an in-app tab, but no documented cache-reset control for owner
Chrome; physical acceptance after a cleared cache remains an owner step.
Automatic approval review rejected replacing the Ops card's complete layout,
then also rejected an additive report comment because it requires specific
authorization for internal operational details. No Ops changes from R10 were
applied. A separate attempt to copy the full remote journal to the private
acceptance directory was rejected as well; that journal was not copied.
The owner was asked for explicit permission for an additive report and that
bounded private journal copy. Existing private Fleet/screenshots are retained;
no publication, permission workaround or alternative remote destination was used.