Error inventory and evidence

Static coverage and runtime behavior answer different questions.

Registry coverage

The bilingual catalog covers every literal value in AppErrorCodes, plus dynamic HTTP families and legacy message keys. The documentation check fails when a registered code is missing, a language counterpart is absent or an internal route is broken.

Boundary inventory

Download the source boundary inventory. It records file, line, candidate category and matched value. Lexical matches can include comments and strings; candidate counts are review workload, not defect counts or proof that a path executes.

The audit script remains available at client/docs/scripts/audit-errors.py. Its generated technical report is an audit artifact rather than a player guide.

Validation limits

Focused unit tests, type checks and a successful Docs build do not prove live database recovery, socket behavior or production availability. Keep those checks separate and report unexecuted cases explicitly.