Knowledge Lint

Run the semantic lint pass on a cogni-knowledge base — surface stale pages, stale drafts, claim drift, missing reverse links, entries-count drift, and formatting findings, and optionally repair the mechanical classes with --fix. This is the standalone analog of cogni-wiki:wiki-lint, computed natively on the vendored lint_wiki.py engine (resolved vendored-first via resolve_wiki_scripts()), so a Karpathy base is lintable with no cogni-wiki plugin installed.

Lint is read-only by default (a pure audit). It writes to the wiki only when the user passes --fix — and even then only the mechanical, deterministic repair classes the engine owns. This is the tokenful semantic counterpart to knowledge-health's cheap structural gate: run health first, reach for lint when you want to inspect or repair drift.

Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once at the start of a session so you remember the wiki-engine boundary — cogni-knowledge runs the lint pass on the vendored wiki-lint engine, it does not dispatch cogni-wiki:wiki-lint.

When to run

• User asks to lint, audit hygiene, or find/fix stale content in a knowledge base
• After noticing entries-count or claim drift in knowledge-health and wanting to reconcile it
• Periodically as a maintenance pass on a compounding base
• Before a knowledge-finalize run, to clean reverse links and drift the synthesis would otherwise inherit

Never run when

• The target directory has no .cogni-knowledge/binding.json — offer knowledge-setup instead.