Web Content Audit

Schema authority: cross-file consistency rules (3-place sync for materials, task ID stability, quiz renumber trap) are codified in _shared/domain-primitives.md §13. Audit scripts in this skill operationalise those rules.

Filename convention (English-first): audit reports land under data/audit-*.md; scripts under scripts/audit-*.mjs.

This skill produces audit scripts that read source files and deployed data, compare them, and emit a human-readable report. The goal is not to gatekeep deployment (that's verification's job) — it's to surface drift that humans should review.

When to Invoke

• Before a major content release (catch outline ↔ course-data ↔ visuals drift before students see it).
• After adding/removing units / materials / quiz items (re-check the three-place sync rule).
• Before handing off a corporate edition to a client (confirm the condensed COURSE matches its source).
• When the user senses "something's off" but can't see a runtime bug — audit is for the invisible drift.
• When planning the next iteration (e.g. "which sections need new illustrations?").

Do NOT invoke when the question is "does the page render correctly?" — that's web-visual-verification.

Audit vs Verify — Operating Mode Difference