write-frontend-documentation

Research a frontend codebase end-to-end, propose an approval-gated documentation plan, then generate developer- and LLM-agent-oriented documentation in a consistent house style. Auto-detects framework, routing, state, styling, API, build/deploy, and tests with path:line evidence. Adapts the structure to the techniques actually found. A single README lives in the frontend root; generated docs use UPPERCASE filenames under documentation/. Existing docs are archived under documentation/archive, never blindly overwritten. Nothing is written before the user approves the plan.