update-doc

# Update Docs Synchronize documentation with repository evidence and avoid stale or speculative content. ## Quick Reference | If you need to… | Go to | |---|---| | Update README/docs after a code change (default workflow) | §Pre-Update Gates → §Output Mode Routing → §Standard Workflow | | Find what actually changed | §1) Scope Discovery | | Decide which command belongs in the doc | §4) Command Source Resolution | | Choose the right doc structure for project type | §Project-Type Guidance + Load `references/project-routing.md` | | Get the per-language evidence commands | Load `references/evidence-commands.md` | | Check docs-drift: find gaps between code and docs | §Quality Scorecard (12 Checks) + Load `references/update-doc.md` | | Add CI checks to catch docs drift automatically | Load `references/ci-drift.md` | | Understand what to mark vs. invent (`Not found in repo`) | §Hard Rules | ## Hard Rules - Use repository files as the only source of truth. - Mark missing information as `Not found in repo`. - Do not invent APIs, routes, env vars, ports, jobs, or dependencies. - Prefer minimal patches by default; preserve existing doc structure unless user requests restructure. - Use diff-scoped updates first; avoid unrelated bulk rewrites. - Keep output scannable: headings + concise bullets + short runnable command blocks. - Keep internal workflow markers out of user-facing docs by default. Verification labels, scorecards, and evidence tables belong in the assistant response unle...