Record successful Node R17 installation on owner Ubuntu board

This commit is contained in:
DCCONSTRUCTIONS
2026-09-07 23:28:46 +03:00
parent 421a8c515a
commit d8afb61229
@@ -114,3 +114,26 @@ transfer until that confirmation is supplied.
Ops MISSIONCOR-76 baseline and state are preserved. Comment
`d16d36ed-f746-4fb9-8a63-f8d1a72f7e2d` records implementation, tests, candidate,
remaining UI/physical acceptance and transfer block; readback confirmed it.
## Installed after owner confirmation — 2026-09-07
The owner explicitly confirmed the Ubuntu destination and permitted transfer.
The previous automatic-review transfer block is resolved. The immutable package
and installer were copied; destination SHA-256 matched the values above.
The active graphical session opened the standard installer, which completed
with `install-result = 0`.
Post-install read-only acceptance:
- dpkg: Node 0.8.14, K1 0.1.13; both services active.
- Installed Node binary matches the built binary, SHA-256
`a7fca3ca950c983267f8547ea5ce1c50739d52753ca5546ef9b76bf049e058bc`.
- Installed provenance matches source a23c5b2 and DG b10fd5d.
- Home and isolated Rerun runtime return HTTP 200; unauthenticated presentation
API returns 401. Runtime response carries the scoped iframe/WASM CSP.
- No system tooling was installed for checks; Python's standard library was
used because curl is absent on this Ubuntu profile.
Detailed Home/settings interactions and local physical K1 acceptance remain
owner checks after reopening the desktop application. Successful installation
and service health do not replace those checks. No physical scanner command
was issued by the agent. The R16 laboratory evidence boundary remains unchanged.