Liveness outage tri-state (#650) + departed-owners fidelity batch #651
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-650"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #650, plus the five dogfood findings from the v0.6.244 review.
Backend:
liveness.OraclegainsProbe+Outage(ctx)on the NegTTL cache;spaces.Manager.Ping(admin-token round-trip; detection lags by at most the token TTL, documented) backs it in main.go./api/v1/admin/owners/departedresponse gains"outage".ownerTransferandownersRevokerefuse 503 during an outage — the server is the boundary; frozen-by-outage is not departed. Freeze semantics untouched.Frontend:
Also relaxes a stale exact-count pin in web/test/deptab.test.js (helper-usage counts in committed tests are lower bounds now).
Tests: internal/liveness/outage_test.go, internal/api/owners_outage_test.go, web/test/depoutage.test.js.