wiki-lintlisted

# Wiki Lint Run the wiki linter and act on its findings. Mandatory gate before `drafting-manuscript` and `finishing-a-research-project`; useful after bulk ingest or whenever the wiki has grown. **Announce at start:** "Using wiki-lint to validate the knowledge tree." <SOFT-GATE> Before transitioning to `drafting-manuscript` or `finishing-a-research-project`: (1) `scripts/lint-wiki.py` exits 0 If not met: tell the user which classes of issues remain (errors / warnings / orphans), ask for a short reason to proceed anyway (e.g. "orphan is intentional — it's the index page"), and write the reason into `knowledge/_meta/gate-overrides.log`. Errors should as a rule be fixed rather than overridden — the override is an audit trail, not a substitute. </SOFT-GATE> ## When to use - Before `drafting-manuscript` (soft gate) - Before `finishing-a-research-project` (soft gate) - After `ingest-source` batch runs (≥ 3 new sources) - When user says "clean up the wiki", "lint", "check the wiki" - Periodically when the project is long-running ## Checklist 1. **Locate the lint script** — `scripts/lint-wiki.py` in the project root (from template) 2. **Run it** — `python scripts/lint-wiki.py`. **If Python or PyYAML or the script itself is missing, take the Python-free fallback path below.** 3. **Parse output** into categories: errors, warnings, orphans 4. **Fix errors inline** (missing frontmatter fields, broken wikilinks, invalid `type` values) 5. **Assess warnings** — stale pages, status in