Refresh PR399 before merging after CMMMech exceeds the freshness limit #402

PR #399's original snapshot pins CMMMech at 76cd81d310a6ccb4cf7bdebcc61be050d0863222 with ten material records. Before publication, check_cards.py reported 27 live records and exited nonzero: growth exceeded its 50% freshness limit. The draft PR disclosed this failure, so its passing unit-test workflow alone does not establish merge readiness.

Run a complete fourteen-Mech refresh from one new set of immutable revisions. Regenerate the census, overlaps, heatmap record lists, statistics and site audit; recheck hand-curated claims and propagate changed figures to related pages. Keep website deployment audits independent from census pins. Do not weaken the freshness gate or re-pin only CMMMech.

Require the full test suite, assembly and manifest checks, independent review, browser previews and a successful live check_cards.py run immediately before merge.

Priority: P2. Resolution belongs in PR #399.