Documentation maintenance

How contributor and usage docs stay current. See the setup index for the other setup pages.

• Read project-intent.md before making product-level changes or writing docs that describe the project's goals.
• Follow Documentation principles for usage docs, MCP instruction text, and contributing guides (lightweight pages, current behavior, post-tool detail in responses).
• Update docs/use/ when end-user MCP behavior or guidance changes; update docs/contributing when contributor workflows, architecture notes, or verification guidance change.
• Treat docs updates as part of done work.
• Keep AGENTS.md concise and index-like; put details in focused docs.
• When failures repeat, promote lessons from docs into tests, lint rules, or scripts.