Record R12 update artifacts and pending clean-cache acceptance

2026-09-07 16:53:32 +03:00
parent 9e03404f23
commit 9b6534287a
1 changed files with 23 additions and 0 deletions
@@ -94,3 +94,26 @@ cache reset. Do not describe that as a completed clean-cache hardware test.
 No Ops publication or Git push is attempted here: prior specific automatic
 approval rejections remain unresolved. Private raw artifacts remain outside Git.
 ## Staged R12 update
 Final package source: `9e03404f23b9d6ee9d147f87886e29c25781d778`
 (on top of shared UI/source commit `fa8ac76`).
 - `mission-core-node_0.8.9_amd64.deb`: 109835024 bytes, SHA-256 `d7a8a74edc7645f416d667048f96688d1aa24c91c1cb51296c3ccfbc3412959f`.
 - `mission-core-xgrids-k1_0.1.9_amd64.deb`: 318111122 bytes, SHA-256 `4e1296ea423f95273188759ffa3db234bb5987fdcb1537aeab28165b3f7dcd23`.
 Both artifacts were staged on the same previously authorized onboard computer.
 Remote SHA-256 checks passed. Apt simulation: exactly two upgrades, zero removals
 and zero new packages. The native Ubuntu installer “Mission Core · K1 R12” is
 open; owner sudo/installation outcome and clean-cache Chrome acceptance are
 pending. The canonical operator service remains on port 8000 (no 8765 listener).
 This update contains **no application key**. Automatic approval review rejected
 a new Keychain-to-installer copy as lacking sufficiently explicit authorization
 for that copy/destination. No retry or indirect copy was attempted. Inspection
 of the existing installer proved the safer path: the R11 encrypted board profile
 is preserved by package removal/upgrade; public R12 preparation leaves it in
 place and the service consumes the same systemd credential. Thus this artifact
 is an update for the existing R11 board, not a self-contained credential-bearing
 installer for a new board. The older private release is not altered.