📊 Refresh CIA data (0 CSVs + production stats)

[github-actions]

📊 Automated CIA data refresh

Pulled the latest service.data.impl/sample-data/ CSVs from
Hack23/cia@master
(resolved to commit 32242569115bdfee8d2afea74f27d9a312fb9e6b)
and re-ran the production-statistics pipeline against the same commit.

CSV refresh

Metric	Count
Total tracked CSVs	146
✅ Updated	0
🟰 Unchanged	140
❔ Missing upstream	0
⏭ Skipped (local-only)	6
❌ Failed downloads	0

Production statistics

• Total persons: 2500
• Total votes: 3793281
• Last extraction: 2026-06-30 14:35:30.655519

How resolution works

The workflow never introduces new files — it only refreshes CSVs
already tracked under data/cia/** and cia-data/**. Upstream paths
are resolved through a recursive basename → upstream-path index
built from the GitHub Tree API, so files living in
sub-folders (distinct_values/, framework-validation/,
risk-rule-tests/) are located correctly even though local paths
are organised differently. An <stem>_sample.csv alias is applied
for the handful of locally-renamed canonical files.

Review checklist

• CSV diffs look reasonable (no schema regressions)
• production-stats.json counts move monotonically or within reason
• Dashboards still render with the refreshed data
• No unexpected file additions or removals

Generated by .github/workflows/update-cia-csv-data.yml.

[github-actions]

🔍 Lighthouse Performance Audit

Category	Score	Status
Performance	85/100	🟡
Accessibility	95/100	🟢
Best Practices	90/100	🟢
SEO	95/100	🟢

📥 Download full Lighthouse report

Budget Compliance: Performance budgets enforced via budget.json