doc-synclisted

# Doc Sync ## Purpose Check whether current documentation still matches the current codebase and confirmed decisions. Use this skill to identify real documentation drift and propose the smallest precise edits needed to restore alignment. This skill is for maintenance and synchronization, not broad rewriting. ## Use when - code behavior changed - interfaces changed - identifiers changed - boundaries changed - assumptions or contracts changed - the human asks whether docs need to be updated - you suspect code and docs no longer match - a public route was added, removed, renamed, or changed indexability: the sitemap's hand-maintained `STATIC_PUBLIC_PATHS` in `src/services/siteMetaService.ts` does not auto-discover routes, so a new public hub or editorial page must be added there. Entity-detail pages (events, clubs, net teams, tricks, rules, IFPA docs) are DB-derived and update automatically; the static list is the part that drifts. Do not use this skill for: - formatting-only changes - wording preferences that do not change meaning - speculative architecture work - broad documentation improvement passes unrelated to actual drift ## Source-of-truth order Use the authority order and read order in root `CLAUDE.md`; do not restate them here. For membership, tiers, Active-Player status, voting eligibility, or published-rules content, consult the IFPA governing documents at the rank that order gives them; a genuine governance change is routed to IFPA, not edited in. When code,