docs-structurelisted

# Docs Structure Check the shape of a repository's documentation, build the docs it is missing, and fill them from the repository's own evidence. Three jobs, two modes. **plan** is the default and read-only: run the checker, report. **apply** writes Markdown into the working tree only when the user asks, and stops; the user owns branches, commits and PRs. Nothing here judges whether a sentence a human wrote is true: that is `docs-sync-audit`. ## Core Rules - Stay read-only until the user says "apply". The plan report is the contract: apply never does what the report did not list. - Which docs a repo needs comes from its evidence inventory (`scripts/docs_evidence.py`): a table of concerns, each one earned by something the repo contains or held by every repo. Where each doc lives is fixed by the shape in `references/shape.md`: six buckets by reader intent (getting-started, guides, reference, explanation, plans, history), every doc always in its bucket folder. Fourteen are unconditional - the README, the agent file, setup, onboarding, the daily loop, testing, deployment, operations, contributing, what it is, the architecture, the configuration, the integrations, security - and every other concern has to be earned; an `unknown` ecosystem means fill writes only open questions; every default is overridable in the manifest. There is no compatibility mode: a doc that covers a concern at another path is a move (R15), and apply does the move. - Never delete or reword prose a human w