Continuity runbook: Gap analysis ops

Task

A second maintainer can diagnose incomplete/503 map analysis on production and fix it by local backfill plus optional approved cache sync — never by computing gap analysis on Heroku.

Success criteria

• HTTP diagnose: make monitor-ga-health-prod / make verify-ga-complete-prod
• Can start local backfill: make backfill-gap-analysis or make backfill-gap-analysis-sync after local-stack
• States clearly: prod is cache-only; miss → 404; no --ga_backfill_* against prod URLs
• Runbook docs/continuity/runbooks/gap-analysis-ops.md (skill continuity-gap-analysis-ops)

Context

• scripts/backfill_gap_analysis.sh, scripts/sync_gap_analysis_table.py
• Worker dyno + Redis/Neo4j matter for 503s; restart may be the first prod action, still no GA compute on prod

Constraints

• existing maintainers only
• Do not sync GA tables to prod in the first drill unless asked
• No authenticated chatbot prompts as a “test”

Agent prompt

See Agent prompt in docs/continuity/runbooks/gap-analysis-ops.md.

Start with docs/continuity/runbooks/gap-analysis-ops.md and its Agent prompt, then review scripts/backfill_gap_analysis.sh and scripts/sync_gap_analysis_table.py. Run the documented production health checks and local-stack backfill commands; done means the runbook covers diagnosis, local backfill, optional approved cache sync, cache-only production behavior, and the stated constraints.