check:catalog + check:terms CI gates

Why these gates exist

RFD-AGT-002 D-2 forbids shipping a surface with neither a Page Card nor an explicit unsupported declaration — silence makes the model guess what a page can do. D-3 locks the backend permission namespace to three write strings plus their reads; a card claiming a fiction like firm:manage must be rejected. D-6 locks the agent's name layers and bans zombie aliases (assistant · bot · Orient · Atlas Presence Bar · app CCB) in code, not just docs. These gates make all three checkable in CI.

What changed

• src/lib/surface-registry/page-card/permissions.ts — the canonical backend permission set (the interim authority mirror of the RFD D-3 namespace, until gen:permissions lands).
• src/lib/surface-registry/page-card/catalog.ts — the Tier-1 catalog index mapping every L1 (agent: "atlas") surface to a Page Card or an unsupported reason, plus the pure findCatalogViolations() validator.
• src/lib/surface-registry/page-card/banned-terms.ts — the banned-alias list + the pure scanForBannedAliases() matcher (whole-word for word aliases, literal for phrases) with a documented check:terms-ok line-level escape hatch.
• scripts/page-card/check-catalog.ts and scripts/page-card/check-terms.ts — the CLI gates, wired as pnpm check:catalog / pnpm check:terms and added to .github/workflows/ci.yml right after check:routes.
• Vitest mirrors (catalog.test.ts, banned-terms.test.ts) so pnpm test enforces the same invariants locally.
• Annotated three pre-existing legitimate non-agent uses of "bot" (a lucide robot glyph for an automated audit actor; a CAPTCHA error message) with justified check:terms-ok markers.

The three acceptance criteria, proven

Verification

Both gates pass on the current tree, and the full pipeline is green:

$ pnpm check:catalog
check:catalog OK — 22 L1 surfaces, all carded or explicitly unsupported.

$ pnpm check:terms
check:terms OK — no banned agent aliases in code.

$ pnpm lint        # 0 errors (1 pre-existing unrelated img warning)
$ pnpm typecheck   # clean
$ pnpm test        # 121 files, 782 tests passed
$ pnpm build       # success

• Gates are scripts (tsx + Node fs), so they run on the CI runner without ripgrep.
• Negative paths are unit-tested: each AC has a failing-case test that proves the gate actually rejects.
• No user-facing strings added (model-facing config, same i18n-exempt class as the surrounding surface descriptions); no color literals.

Scope notes

• The permission set is hand-declared on purpose: the drift-proof gen:permissions generator (the D-2 build) is a separate Story this gate depends on. When it lands, the generated export replaces permissions.ts and the gate keeps its shape.
• The shipped glossary.md (docs lane) is a sibling Story, not this one — this ticket is only the two app-side CI gates.

Files changed

11 file(s), +614 / -1 lines