Record R14 public artifacts and staged installation scope

This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 19:04:52 +03:00
parent eed53dbc0b
commit 9c4d70b0e9
@@ -72,3 +72,24 @@ R14 is a public matched update: Node 0.8.11 and K1 0.1.11. It uses the existing
encrypted onboard credential. No Keychain export, new secret package, physical encrypted onboard credential. No Keychain export, new secret package, physical
CLI probe, Git push or Ops retry is part of this change. Production build, CLI probe, Git push or Ops retry is part of this change. Production build,
artifact identity and installation outcomes are recorded when completed. artifact identity and installation outcomes are recorded when completed.
## Built and staged R14
Source commit: `eed53dbc0b5a47061b51a46cd7905cc6137e0738`.
Both production/typecheck builds passed. Package inspection found 94 Node and
184 K1 members, no links or private application-key member, matching source
provenance, and `application_material_included=false` for K1.
- `mission-core-node_0.8.11_amd64.deb`: 109837510 bytes; SHA-256 `304adb734ada587256a444e54fef2ebf584738c72bd8f431cf63d82886d629bc`.
- `mission-core-xgrids-k1_0.1.11_amd64.deb`: 318114552 bytes; SHA-256 `f2d69dd6616167850e9a4d211fb7692127c1f65039d062ff24fd0614fde813cc`.
The unique R14 directory was staged on the authorized onboard computer. Both
remote checksums passed. Apt simulation selects exactly these two upgrades from
Node 0.8.10 and K1 0.1.10, with no additions/removals. The existing installer
safe-state guards remain in place.
Before installation, Fleet reported the board online and acquisitions idle.
Mission Core returned HTTP 200; the updated home page rendered in the in-app
browser. The single canonical process remains on 8000, with no listener on 8765.
The native “Mission Core · K1 R14” installation window is open for owner-entered
sudo. Installation exit status and clean-cache physical acceptance are pending.