Record verified R13 installation on onboard computer
This commit is contained in:
@@ -107,6 +107,22 @@ records `application_material_included=false`.
|
||||
|
||||
The unique R13 directory is staged on the previously authorized onboard computer.
|
||||
Remote SHA-256 checks passed. Apt simulation selects exactly the two upgrades
|
||||
above, with zero additions/removals. The native “Mission Core · K1 R13” installer
|
||||
is open for owner-entered sudo. Installation exit status and clean-cache physical
|
||||
UI acceptance remain pending; neither is inferred from build or unit results.
|
||||
above, with zero additions/removals. The owner entered sudo in the native
|
||||
“Mission Core · K1 R13” installer and reported exit status 0.
|
||||
|
||||
## Installed verification
|
||||
|
||||
Read-only verification on 2026-09-07 confirms installed Node 0.8.10 and K1 0.1.10.
|
||||
Both installed provenance files identify source commit
|
||||
`9bba44f7c4b79d4ba3ec95680610081cc4db9c96`; K1 still records
|
||||
`application_material_included=false`.
|
||||
|
||||
Both services are active/running with `NRestarts=0`. Node entered active state
|
||||
at 17:53:51 MSK and K1 at 17:53:59 MSK. A bounded warning/error journal check
|
||||
for both services since 17:53:59 returned no entries. Canonical Mission Core
|
||||
on port 8000 returns HTTP 200; Fleet reports `ndc-rover-006` online and the
|
||||
device acquisition idle.
|
||||
|
||||
Installation verification is complete. Clean-cache physical UI acceptance
|
||||
remains pending: the installed state and automated regressions do not establish
|
||||
continuous live preview or route preservation while moving this scanner.
|
||||
|
||||
Reference in New Issue
Block a user