Feature #209: self-heal (health, empty guide, degraded visibility) #216
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!216
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/issue-209"
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?
Implements issue #209 waves 1-3 per the plan with R1 + review normative (give-up CUT).
Backend (internal/api): summary health empty|healthy|degraded (empty from in-hand manifest+refs, +0 trips; degraded via one conditional fsck.pb probe on non-empty summaries; ETag covers health with ~degraded suffix); empty repository: 404-marker prefix at all 9 bind_wal sites (exact HeadSeq==0 + no-refs predicate, fail-closed); overview fsck projection (+1 conditional GET, stated) with read-side repair_stalled + effective upstream. No new endpoints, no bucket families, no protobuf changes.
Web: EmptyRepoGuide on Code tab, known-empty fetch suppression, degraded amber banner + inline notices + WAL object-health section with re-audit trigger. SDK typedefs updated.
Docs: 07_api, 10_maintenance, 12_web_ui + Decisions appends; EVIDENCE E13 no-change entry.
Tests: go test -race + cover 95.3% on internal/api; node --test 410/410; real-Chromium 29/29 (empty guide zero toasts, degraded banner, WAL card, both themes, console clean). No new Go modules, no new npm deps.