HydraCache 0.72.0 — Management Center 2.0 and operational visibility

Status: shipped 2026-09-22 from exact qualified candidate 24927c28c279c6c34ad90111ee6470b4065e0815.

0.72 replaces the single-page observe-only console with a locally bundled TypeScript/component application and a versioned, read-only /management/v1 API. Operators now have routed dashboard, member and partition, HC/1-HC/2-RESP client, namespace/cache, health, persistence, operation, metrics and audit views. Cluster aggregation is authenticated and bounded. Every observation states whether it is live, modeled or unavailable; fresh or stale; complete or partial.

The browser remains read-only. This release does not add arbitrary proxying, browser-to-member fan-out, state-changing controls, unbounded history, sensitive identifiers, a new storage engine or a numerical performance claim. Optional Prometheus history uses only fixed reviewed queries. Missing or mixed-epoch evidence is shown as unknown/partial and cannot become a green health state.

Release evidence

The candidate was frozen before final qualification. Full exact-SHA campaign 35537203094 completed 50 jobs with zero failures, including the six-hour Management Candidate Soak and real v0.71.0 to 0.72 upgrade, leadership-change, restart and rollback proof. Separate ship campaign 35556487047 completed the 24-hour confirmation. Durations, one-request-per-second protocol load, 64-key HC/1 ring, TTL, hourly fault schedule and FD/RSS/latency ceilings were not weakened.

The campaign exposed a real unbounded owner before acceptance: ClusterAdmissionBridge retained every 50 ms admission decision. The candidate bounds detailed diagnostics to a 1,024-entry FIFO while preserving monotonic lifetime and eviction counters. Unit tests overflow that bound and verify newest-entry retention; Linux one- and three-daemon isolation profiles changed the idle behavior from linear growth to a stable RSS plateau; the complete six-hour and 24-hour contours then passed.

External baseline run 35723493297 measured clean pre-feature commit 8d205fa302d81a07c19147cb4431e16390d256c3, published v0.71.0 commit da8d6de409a657e0260e7fbfb4ab31d8d6ad5ca8, and the candidate independently. Both legacy baselines retained zero origin owners after quiescence, a 20,915-byte bundle and 93.1142% executed JavaScript byte-range coverage; the 0.71 baseline also passed all 12 legacy Playwright instances. These values establish provenance and regression boundaries, not a portable speed or memory claim.

After materializing the immutable artifacts, the unchanged candidate passed:

cargo xtask management-center-check --release 0.72 --require-evidence
cargo xtask release-evidence --release 0.72 --receipts-dir target/release-evidence/receipts --require-ship

The final aggregate contains 15 ship-ready work items, zero lower-stage items and no rejection reason. The accepted normalized evidence and byte-exact key Actions ZIPs are retained on branch evidence/0.72/management-center-ship at commit 351766af9241399306a385298f0cc252aca6036c; SHA256SUMS and the artifact manifest bind the archive to the source runs. Baseline capture tooling and its accepted decision remain on evidence/0.72-baseline-capture.

The Management Center guide describes the supported operator surface. The 0.72 verification page describes the test layers, fault schedule, evidence identity and release-admission rules.

The v0.72.0 tag points to the exact measured runtime candidate above. Later release-documentation and evidence-archive commits do not become a different runtime candidate.