docs(spec): sync SPEC.md to actual architecture (ADR-014)

[Seungpyo1007]

Summary

SPEC.md's §4/§16/§17 still described the original 2026-05 plan (FastAPI on Railway/Fly.io, Supabase Postgres, Sentry/Better Stack/UptimeRobot) — none of which was ever actually deployed. Adds ADR-014 documenting the real architecture that's been in production for months (static JSON dump + GitHub Pages, no live server), marks ADR-002/ADR-010 as superseded rather than deleting them, and rewrites §16.1 (CI/CD workflow tables) and §17 (ops/observability) to match the real workflows and TechMachine-based monitoring. Also refreshes §3.1's dataset scope numbers from the original ~500-phone target to the actual current counts (93,396 smartphones etc.).

Details

• ADR-014: static-dump-only architecture, supersedes ADR-002/ADR-010 without deleting their rationale (kept for the Phase 4+ re-trigger condition).
• §16.1: replaced fictional workflow table with the real TechAPI/TechEngine/TechMachine workflow lists.
• §16.2-16.4: replaced Railway/Fly.io/Sentry deploy+rollback steps with the actual GitHub Pages flow.
• §17: replaced Sentry/Better Stack/UptimeRobot/Supabase monitoring with TechMachine's actual daily health-check + issue-comment model.
• §3.1: real per-category record counts as of 2026-09-24, noting the game-catalog split and the software/websites identity-based retention decision.

Test plan

• Markdown structure spot-checked (no broken headers/tables)
• Doc-only change, no code/data affected