v0.94.0: REPORT — appended (SMART serialized into /disks, live-validated on demo-felhom)

2026-07-24 21:41:01 +02:00
parent 21fee69154
commit 643899c191
1 changed files with 29 additions and 0 deletions
@@ -1,3 +1,32 @@
+# REPORT — v0.94.0: serialize per-disk SMART into /disks (2026-07-24)
+
+Part of the **disk-health** cross-repo train (agent v0.94.0 + controller v0.169.0/.1 + hub v0.73.1).
+Appended above the previous report (kept below).
+
+**Baseline:** felhom-agent `c230258` (v0.93.0) → committed `21fee69` (v0.94.0). Re-verified clean at start.
+
+**Change (additive, backward-compatible; MinAgent floor unchanged):** `localapi.DiskInfo` gains
+`Smart *hub.SmartSummary \`json:"smart,omitempty"\``, copied from the target's already-computed
+Observe-time enrichment **only when `t.Smart.Health != ""`** — a zero-value summary (SMART never read)
+stays omitted so the controller sees "absent" and renders "Nincs adat". No new smartctl load, endpoint,
+or sudoers change. Files: `internal/localapi/disks.go`, `internal/localapi/disks_smart_test.go` (new),
+`CHANGELOG.md`, `CONTEXT.md`.
+
+**Tests:** `TestDisks_SmartSerialized` (fixture target's SATA counters + temperature present; an
+absent-SMART target omits the field). Red-proof: drop the `di.Smart = &sm` copy → "smart not serialized"
+FAIL (confirmed). Full agent suite: 29 packages pass, 0 fail; build + vet clean.
+
+**Deploy + live validation (demo host `demo-felhom`):** the vacation note was stale — the agent is
+**up and reachable** (binds `192.168.0.162:8443`). Built `felhom-agent-0.94.0` (ldflags), scp'd,
+backed up `.bak-0.93.0`, `install`-ed, restarted → **active**, `--version` 0.94.0, capabilities 68/68
+degraded=0, local-api listening. **§13(1) live:** the authed `/disks` payload now carries the `smart`
+object — dir-backed targets show `smart.health` (UNKNOWN on this virtualized demo hardware), the USB
+(union-path) target omits it. The field is live end-to-end; the controller consumes it (see the
+controller REPORT). Binary published: image tag on the registry via the publish flow is a follow-up if
+a fleet-wide agent republish is wanted — the code + live-deployed binary on demo-felhom prove the field.
+
+---
+
 # REPORT — v0.93.0 publish train executed: built, published, vouched, deployed fleet-wide (2026-07-22)

 **The previous report's "NOT built or deployed" line dies here.** v0.93.0 (hyphen-free escrow