Resolve reliability and adoption audit backlog

[Codewriter90x]

Summary

• align licensing, release notes, roadmap and issue forms with the clean-room v2 provenance
• harden future releases with main-ancestry validation and draft-upload-publish ordering
• add scheduled upstream freshness checks, a deterministic reconciliation backlog and a source-backed correction example
• expand Ruff, mypy and whole-script coverage; split Pages data modelling from rendering
• improve Pages with lazy data loading, accessible filter-link copying, checksum downloads, historical-code labelling and automated link/accessibility/performance budgets
• add an opt-in typed JSON/SQLite schema 4 preview without altering published v2 assets

Why

The audit found materially stale licensing language, a false immutability claim, release-ordering risk, narrow quality gates, heavy eager Pages loading and no reproducible source-freshness workflow. The published v2 assets remain unchanged.

Validation

• ruff check scripts tests
• mypy on all maintained Python scripts
• 48 Python unit/integration tests
• 8 Node tests
• whole-script branch coverage: 81%
• deterministic two-build comparison
• dataset validation and cross-format equivalence
• Pages build plus accessibility, local-link and performance-budget validation
• release build, checksums and SQL import validation
• live upstream checksum comparison: ISTAT and GeoNames both current on 2026-07-30

Repository settings applied

• immutable releases enabled for future releases
• Python 3.11, 3.12 and 3.13 added to required status checks
• empty Wiki disabled
• source-update label created

Existing v2.0.0 assets cannot become immutable retroactively; documentation now states that boundary explicitly.