/wiki-lint — wiki maintenance pass

The wiki is the codebase; this is its test suite. WIKI = the global knowledge base path defined in your global CLAUDE.md. It is a git repo — every lint run ends with a commit, so damage is always recoverable.

Checks (run all, cheap subagents for the reading)

Delegate bulk reading to a cheap subagent that returns findings as a packet; verify load-bearing claims yourself before editing (leads, not facts).

1. Index freshness — does every status line in index.md match the current reality in its project page AND the actual repo state (git log dates, status files)? The index is the highest-traffic file; it rots first.
2. Stale claims — frontmatter updated: older than 30 days on an ACTIVE project's page = suspect. Cross-check the 2-3 most load-bearing claims per stale page against reality (repo, status files). Fix or mark.
3. Contradictions — same fact stated differently in two places (index vs page, page vs me/, wiki vs project CLAUDE.md). One fact, one place: fix the copies to reference the canonical location.
4. Orphans — pages nothing links to (grep for [[name]] and ](path references). Either link them from the right index/_index page or propose deletion.
5. Broken links — [[wikilinks]] and relative markdown links pointing at files that don't exist. Fix or remove.
6. Delete-when-wrong sweep — anything proven false (old model names, dead tools, superseded decisions): DELETE the claim, don't annotate around it. Update an existing page rather than creating a duplicate; delete notes that turn out to be wrong.
7. Log hygiene — daily logs are append-only (never rewrite), but check the last week's rich summaries exist; a run of marker-only days means the session-end summaries aren't being written — flag it.
8. Size guard — index.md should stay under ~60 lines of content; me/ files under ~30. If growing, tighten: statuses move to pages, index keeps one line each.

Output

1. Apply all safe fixes directly (index refresh, link repair, deletions of proven-wrong claims, updated: bumps).
2. git -C <WIKI> add -A && git commit with message lint: <date> — <n> fixes, <n> flags.
3. Report to the user: fixes applied, contradictions that needed judgment, anything flagged for them (risks noted in pages, decisions only they can make).
4. Append a one-line entry to today's log: ## [YYYY-MM-DD] lint | wiki | <n> fixes.

Scale guard

When the wiki passes ~100 pages or grep starts missing things phrased differently, install qmd (the search tool Karpathy names) as an MCP server. Not before — at current scale the index IS the search engine.