compound-refresh

Audit the knowledge stores against the current codebase and prune what no longer earns its place. Two stores: `docs/solutions/` and the project's `AGENTS.md`. Every change is user-gated. ## Scope An argument narrows the sweep to matching `docs/solutions/` docs — try it as a filename, then a frontmatter `area`/`tags` value, then a content keyword. No argument → every doc plus `AGENTS.md`. If nothing matches, say so in one line and stop. ## Audit docs/solutions/ The format contract is [`../compound/solutions-format.md`](../compound/solutions-format.md). For each doc in scope, cross-check its claims against the current code — cited paths and names still exist, the fix still matches how the code works today, snippets reflect the current implementation — and against its sibling docs for overlap and contradiction. Verdict per file: - **Keep** — still accurate and useful. No edit: reported as reviewed, zero churn. - **Update** — the problem is still real but the doc drifted, from moved paths and renamed names up to a fix the current code now contradicts. On approval: evidence-backed in-place edits; on a contradicted fix, rewrite the doc to the current truth and present it as the rewrite it is. - **Consolidate** — two docs overlap so heavily a maintainer must read both to get the truth. On approval: merge unique content into the canonical (broadest, most current) doc, delete the other. - **Delete** — both the implementation _and_ the problem domain are gone, or the doc is ...