chore(docs): route domain test paths, anchor landed decisions, and expand AGENTS.md headroom

Merged
BI
1mo ago
+87-23

User description

Summary

  • Record the verified \prlanded\ review-ledger entry for PR #3544 (\def6fabcc8235e8592fea2613d07170e23dd9836).
  • Teach \classifyRepositoryPath\ in \scripts/maintain-docs-system.mjs\ to route new domain-specific \ ests/*\ files (\nswer-engine, \source-intake, \personal-practice, \clinical-content, \knowledge, \design-system, \pp-experience) to their owning system manifests instead of falling through to \delivery, with unit tests in \ ests/maintain-docs-system.test.ts.
  • Anchor 6 landed decision records under \docs/decisions/\ (\2026-10-15-coderabbit-stays-but-does-not-block-merges.md, \2026-10-15-no-default-ai-coding-tool.md, \2026-10-15-no-separate-github-account-for-ai-tools.md, \2026-10-15-remove-codspeed-check.md, \2026-10-15-specifiers-need-a-named-sign-off.md, \2026-10-16-keep-migration-history.md) to their live repository sources, reducing \unanchored\ decision notices from 10 to 4.
  • Tighten redundant wording in \AGENTS.md\ while preserving all test-guarded phrases, increasing startup instruction budget headroom to \1,807\ bytes (\22,193 / 24,000\ bytes).

Verification


  • px vitest run tests/maintain-docs-system.test.ts tests/organisation-decisions.test.ts tests/organisation-instruction-guards.test.ts tests/migration-history-guards.test.ts tests/challenger-m5-2-empirical-stress.test.ts\ (pass)

  • pm run docs:maintain\ &
    pm run docs:maintain:check\ (pass: 0 unplaced files across 10,356 tracked files, 5,936 doc links valid, 840 script refs valid, 139 decisions valid with 0 errors and 0 warnings)

Summary by cubic

Routes tests/* paths to their owning system manifests instead of falling through to delivery, with unit tests covering the new routing. Ambiguous work-* tests stay unplaced for explicit ownership rather than being auto-claimed by personal practice, while search- and document- prefixes are dropped so explicit manifest globs own those tests.

  • Anchors six landed decision records to live repo sources, cutting unanchored notices from 10 to 4 while retaining chat attribution for all six decisions.
  • Tightens redundant AGENTS.md wording and aligns Railway token guidance with .env.example: prefer the project-scoped RAILWAY_TOKEN for deploys, reserve RAILWAY_API_TOKEN for list/link.
  • Records the verified prlanded entry for PR #3544 and regenerates the branch-review index to 712 records after merging main.

Summary by CodeRabbit

  • Documentation

    • Clarified ownership requirements for Supabase settings, integrations, and credentials, and refined guidance for migration permissions and preview deployments.
    • Updated branch review records and decision references.

  • Chores

    • Improved repository documentation ownership mapping for test files and added coverage for those mappings.

CodeAnt-AI Description

Route domain tests to their owning documentation systems

What Changed

  • Domain-specific test files now go to their owning system manifests instead of defaulting to delivery.
  • Ambiguous work-* tests remain unassigned unless an exact ownership rule applies.
  • Updated Railway guidance clarifies which token to use for deploys and which to use for listing or linking projects; decision records now point to repository sources.

Impact

✅ Fewer domain tests assigned to delivery
✅ Ambiguous Work tests require explicit ownership
✅ Clearer Railway token choice for deploys

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.