hub v0.181.0 (not deployed): root files are 'behind' only when the files differ (R-1392, decision 304); Go 1.27.4 (R-1391)
gates / gates (push) Successful in 1m55s

This commit is contained in:
admin committed 2026-11-14 10:11:31 +01:00
1 parent 561a4d98e9
commit 83316fc986
15 files changed
+442 -11

No files matched your search

@@ -354,6 +354,15 @@ an installed box by reinstall or by hand.
operator (`runbooks/config-bundle.md`).
- **Visibility.** System page "Root files" column; alarm `os_config_bundle_behind` after 7 days
(`OS_ALARM_BUNDLE_BEHIND_AFTER`; decided by CC unattended — operator may reverse).
- **„Behind” is judged on the FILES, not on the bundle's label (hub v0.181.0, R-1392, `09` §3 decision 304).** The
bundle carries its `agent_version`, so its sha256 moves with every agent release — also when `configs/` did not
change and the release sends no bundle job (measured: 0.172.1 → 0.173.0, 32 files equal, two sha256s). When the box's
bundle sha256 differs from the vouched one, the hub fetches both bundles from the package registry, accepts each
only if its bytes hash to the sha256 already trusted (the vouched one; the one the box reports), and compares
everything but the label. Equal → not behind: no amber, no alarm, the „behind since” mark is cleared. Anything it
cannot read, verify or parse → the old verdict (behind). `hub/internal/bundlefiles`; pinned by `TestSame*`,
`TestBundleAlarm_R1392_*`, `TestBundleCell_R1392`. **Not covered:** a box whose bundle version was pruned from the
registry reads „behind” (true enough: it is older than the kept versions).
- **Measured live** (`audits/r840-config-bundle-2026-10-04/partB/`): both demo boxes had every file equal to the release
except `felhom-os-apply`; after the bootstrap the signed bundle wrote 0 of 22 (21 same, 1 setting kept), self-check
ok, capability probe 71/71. demo-hp: a wrong-sha job refused (nothing changed); a bundle with one deliberate change