docs-trust-auditlisted

# docs-trust-audit Documentation about your own product goes stale when *you* change something, and you usually know when you did. Documentation about somebody else's product goes stale when *they* change something, and nobody tells you at all. That is the whole problem this skill exists for. Every claim your docs make about the outside world — "works with Postgres 12 and up", "Stripe's webhook signature header is `Stripe-Signature`", "unlike Competitor X, we do not cap projects", "see their authentication guide" — was true when it was written and decays without a single commit on your side. There is no failing test, no type error, and no incident. It just quietly becomes false, and a reader who follows it into a broken integration learns something about your docs that generalises to everything else in them. The cost is asymmetric. A wrong sentence about your own product reads as a bug; a wrong sentence about a partner's product reads as *you do not know what you are talking about*, and it undermines the pages next to it that are perfectly correct. **Mode: audit.** It verifies and reports. It rewrites nothing — a claim about someone else's product needs a human to decide what the replacement sentence should say. ## When to run - After a partner or dependency ships a breaking change, to find every page that described the old behaviour. - Before a launch or a campaign that will send scrutinising readers into the docs. - Quarterly, as a floor. External decay has no oth