error-catalog-maintainerlisted

## What It Does Maintains per-module error catalogs so new or changed failure paths are documented with recovery guidance, ownership signals, and registry consistency. ## Use This When Use this when a change introduces new error codes, modifies user-facing messages, or changes the recovery path for existing failures. ## Inputs - Read the module `error-catalog.md` and any API error docs first. - Read the changed implementation and any available error-code extraction output. - Read `references/error-entry-fields.md` before editing catalog entries. ## Procedure 1. Run `scripts/find-error-catalogs.sh` to locate canonical per-module error catalogs. 2. Run `scripts/extract-error-codes.sh <changed-files...>` to surface candidate codes the diff introduces or renames. 3. For each new / changed code, write or update its entry using `assets/entry.template.md` (code, trigger, user message, operator meaning, recovery, retry safety, ownership). 4. Check global registry / module prefix collisions explicitly. 5. Format report per `assets/output.template.md` and validate with `scripts/lint-output.sh`. Vague user messages or unknown recovery → `## Catalog Gaps`, never a completed entry. ## Output Contract - Match `assets/output.template.md`: `## Updated Error Entries` and `## Catalog Gaps`. - Every updated entry must name the error code, catalog path, and changed trigger, message, recovery, or ownership field. - Output must pass `scripts/lint-output.sh` (exit 0). - Unknown recovery gu