Risk Register
Owner: Tompi. Review weekly. L = Likelihood, I = Impact (H/M/L).
| # | Risk | L | I | Mitigation | Owner |
|---|---|---|---|---|---|
| R1 | Test infra deprioritized → whole plan slips (it’s the critical path) | H | H | Treat Phase 0 as a hard blocker; Gate 0 before any cutover work; protect dev time | Saiqul |
| R2 | “Tests exist” assumption (stale docs) leads someone to skip Phase 0 | M | H | Correct CLAUDE.md + project note (task 0.6); this tracker is source of truth | Saiqul |
| R3 | Parity never declared “done” — moving target as legacy keeps shipping | H | H | Feature freeze on legacy from W4 (task 2.1); enforce strictly | Tompi |
| R4 | Payment/booking regression reaches real users | M | H | Test-mode API only; payment a top-rank E2E; rollback trigger on payment failure spike | Detta |
| R5 | Performance regression vs legacy hurts conversion | M | H | Lighthouse CI budgets ≥ legacy parity (Gate 3); RUM Core Web Vitals during canary | Saiqul |
| R6 | Cloudflare weighted-routing mechanism not ready by W8 | M | H | Spike + confirm mechanism with hh-cloudflare early (by W6); rehearse rollback in staging | Irfan |
| R7 | Device-specific breakage (iOS Safari / Capacitor web) found late | M | M | Cross-device matrix in Phase 2; Playwright mobile viewports; dogfood on real devices | Detta |
| R8 | Canary metrics ambiguous → can’t tell if rollout is safe | M | H | Define pass/fail margins per metric before W8; baseline legacy first | Saiqul + Tompi |
| R9 | Analytics/funnel events differ → conversion looks worse than reality | M | M | Event parity check (task 3.5) before canary | Tompi |
| R10 | Flaky E2E erode trust in the gate | M | M | Quarantine flaky specs, never auto-retry into green; track flake rate | Afif |
| R11 | Rollback untested → fails when actually needed | L | H | Mandatory rollback rehearsal in staging (task 3.4) before any real traffic | Irfan |
| R12 | Bus factor — Afif is sole assignee on nearly all ClickUp port subtasks (verified 2026-06-15) | H | H | Spread ports across Growth devs; pair on critical flows; docs in this tracker reduce single-person context | Tompi |
| R13 | Large unmigrated surface (Guest QR Pay-Now ~14, booking-confirmation 9, View Menu 11, apps/web SSR 9 issues) underestimated | M | M | Track via 08-issue-index.md; re-baseline timeline as clusters close | Tompi |
Escalation
Any risk that turns 🔴 (materialized) → Tompi calls it; if it threatens a gate, the gate stays ⬜/🔴 and dependent work pauses. Cutover (Phase 4) never proceeds with an open H/H risk.