docs-fact-registrylisted

# Docs Fact Registry ## What this is, and when to invoke it Docs drift silently, and ad-hoc drift checking produces the two classic failures: facts "verified" against the very doc under check, and judgment calls silently overwritten by an auto-fixer. This skill makes drift-checking declarative — a registry of claims, each with a source of truth and a policy — and keeps the policy attached to the finding all the way to the fix decision. Invoke when checking or reporting docs↔code drift (the documentation-auditor preloads this skill), or when authoring anything that auto-updates documentation. ## The registry (MUST) Drift is checked against a registry: *claim in docs → source of truth in code → policy*. The checking agent instantiates the table **in-context per run** from the docs under review — no checked-in registry file is required (a project MAY check one in; use it if present). | Claim (in docs) | Source of truth (in code) | Policy | |---|---|---| | version string in a plugin table row | manifest `version` field | mechanical | | "N plugins" count / badge | manifest entry count | mechanical | | script path cited in a guide | file exists at that path | dead reference | | "coverage ≥ 80%" aspiration | CI config threshold | decision | ## Three-way classification (MUST — not binary) - **mechanical** — uniquely derivable fact (version string, script name, file count) → auto-fixable. - **decision** — judgment call (aspirational threshold, descriptive prose, "is docs or co