Patch release so the release tag points at a commit whose CI is actually green.
v0.7.1 was tagged at ec5ea9db, whose CI run was red -- ci (3) failed on a pre-existing /api/state bug that also failed on the previous main. That tag was left in place rather than moved, since retagging a pushed release rewrites published history and the same name would resolve to different code for anyone who already fetched it.
This tag was created only after main's own CI (CI, main-full, Pages) went green on this commit.
Fixed
/api/stateserved a collector's empty default instead of real data. The"data"CollectorSource seeds{}and is mtime-gated, so a quiet collector leaves that default cached. The endpoint only computed a section inline when the cached payload wasNone, and{}is notNone-- so the dashboard's first paint could show an empty data section (watchdog, monitor, repos, events, alerts and messages all missing). An empty section is now treated as not-yet-snapshotted and computed inline (#668).- Test isolation:
test_agent_detail_roundtripcalledconfig.reload()insetUpto pick up fixture paths but restored the environment intearDownwithout reloading, leaving the config module pointing at a temp directory it then deleted (#668).
Full 0.7.1 hardening notes (12 PRs) are in CHANGELOG.md.