You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
error codes: migrate db.rs API-layer call sites to API-0xx, audit remaining sites to INT-0xx #362
Part of #277's rollout, step 6 — the last of the 5 category issues, deliberately last since it audits whatever call sites the other four didn't cover.
Work item
Two parts:
Migrate the remaining db.rs/API-layer bail!/anyhow! call sites (lock-poisoning, write-path invariants, prepare-only-queries checks, etc.) to their real API-0xx codes (9 documented in docs/ERROR_REFERENCE.md).
Audit every remaining uncoded bail!/anyhow! site crate-wide (after the PRS/STG/WAL/QRY/API issues land) and assign INT-0xx codes with new docs/ERROR_REFERENCE.md entries, so nothing permanently falls through to the generic INT-000 catch-all added in feat: structured error codes foundation (MinigrafError, ErrorCategory) — #277 (1/6) #357. Also upgrade the REGISTRY↔ERROR_REFERENCE.md sync test from subset-checking to full bidirectional equality (REGISTRY == doc), now that every call site is finally coded — see docs/superpowers/specs/2026-08-25-structured-error-codes-design.md's "Directionality note".
Sequencing
Depends on: #357 (merged), and in practice should land after the PRS/STG/WAL/QRY issues so its crate-wide audit isn't immediately stale.
Part of #277
Activity