Statements: installable PWA + nftables volume populator + app roadmap

[a777ance]

What this does

Adds the backend pieces that support the statement mockups, and makes the gallery
installable on phone and laptop.

① Installable PWA (the phone + laptop demo, no app store)

• manifest.webmanifest, sw.js (offline precache of the gallery + statements), and
  branded A7 icons in icons/ (generated by tools/make_icons.py).
• Wired into index.html only — individual statement files stay self-contained
  (no external assets / no JS), which is deliberate.
• Verified locally: manifest is valid JSON, sw.js passes node --check, and every
  asset serves 200 over HTTP.
• Works on both: laptop browsers + Chrome/Edge "Install"; phones via "Add to Home
  Screen." Opens full-screen, works offline.
• Publishing: merging to main triggers the existing pages.yml. (Feature branches
  can't deploy — the github-pages environment is locked to the default branch, which
  is exactly why this needs to land on main.)

② Real volume data — the one measured-data gap

• tools/collect/populate_sets.py resolves categories.json → public CDN IPs and feeds
  the nftables accounting sets (the previously-missing half of the volume layer; the
  counters were empty without it). Filters to globally-routable IPs; default dry-run,
  --apply on the box. Tested: 256 IPs across 8 categories.
• tools/collect/README.md — deploy + cron runbook (also fixes the dangling
  collect/README.md references in nftables-accounting.nft).
• README data-sourcing table: volume-by-category moves from buildable → built, run it
  on the box.

③ Roadmap

• APP-ROADMAP.md — the honest path from mockup to a real app (PWA → real data → service
  backend → native + store), with the data-honesty gate.

Still sample, on purpose

The 20-home operator portfolio and the peer benchmarks remain sample data
(random.seed(77)), per the repo's own rule against printing invented averages. This PR
does not fabricate client data — it makes one home's numbers real.

Minor note

pages.yml gains this branch in its trigger list (consistent with the existing
claude/meta-audit-… entry). Harmless on main; happy to prune the trigger list if you'd
prefer it clean.

https://claude.ai/code/session_01BmHwvmJ25nDxDGX5hhjFkM

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	cloudflarelocaldns	6d3fc88	Jun 03 2026, 07:05 PM