Record installation of the onboard discovery fix
This commit is contained in:
@@ -75,3 +75,34 @@ previous R2 artifact bytes are retained. Exact source/release hashes and board
|
||||
installation results belong in the following acceptance addendum. Hardware UI
|
||||
discovery, provisioning, camera/LiDAR and recovery remain pending until a new
|
||||
owner run with cache cleared before the test.
|
||||
|
||||
## Installed release
|
||||
|
||||
The exact source commit is `77acb377e2a996f70eb6e24f38e9a924da8be023`.
|
||||
The private directory `private/releases/mission-core-node-k1-20260907-r3`
|
||||
contains both packages, `install` and `SHA256SUMS`.
|
||||
|
||||
| Package | Bytes | SHA-256 |
|
||||
| --- | ---: | --- |
|
||||
| `mission-core-node_0.8.1_amd64.deb` | 109813420 | `13c96905d32fb665c5fee4b76d1704a24507c5c62afc68186561bae83cd678f2` |
|
||||
| `mission-core-xgrids-k1_0.1.1+private.1_amd64.deb` | 318106574 | `03b34b11f0608608dad2b366f86903afef39b5c85d042b3ec37f819ab322a95a` |
|
||||
|
||||
Both archive provenances, the packaged runtime-fence fix and private member
|
||||
permissions were checked. Transferred hashes matched; APT simulation selected
|
||||
two upgrades and zero removals. The owner completed Ubuntu authentication and
|
||||
the installer exited successfully. At 09:17 UTC on 07.09.2026, the Mini started
|
||||
Node 0.8.1 and K1 0.1.1+private.1. Both services are active/running with
|
||||
NRestarts=0. Installed provenance and the runtime-fence source match this
|
||||
commit. Reinstall preparation accepted the existing application profile.
|
||||
Fleet receives the new runtime through the preserved original binding.
|
||||
|
||||
The owner was instructed to clear Chrome cache again for the next UI test.
|
||||
Read-only observations with UTC/monotonic timestamps are kept under
|
||||
`private/acceptance/k1-node081-20260907-core-ui`. Successful hardware discovery,
|
||||
Bridge and live output are not inferred from service readiness.
|
||||
|
||||
Git publication of the preceding installation report `2fdf1d3` was rejected
|
||||
before execution by automatic approval review, citing internal deployment
|
||||
metadata and requiring explicit authorization for that payload/destination.
|
||||
The owner has been asked; no alternative push was used to bypass the decision.
|
||||
The R3 source and report are currently committed locally on top of that report.
|
||||
|
||||
Reference in New Issue
Block a user