Wave 4 Pass 4.A residual-risk register accepted: 3 risks identified po…

Decision

Wave 4 Pass 4.A residual-risk register accepted: 3 risks identified post-hardening — H1 Safari iOS IDB 7-day eviction (mitigated by PWA-install flow; document in pilot runbook), H2 Server Action ID rotation across deploys (already deploy-safe — IDB stores payload only, drain re-imports action fresh), H3 no inline-edit on conflict entries (Pass 4.B FAB covers this). NONE block Pass 4.B/4.C; H1 surfaces in pilot runbook; H2 is non-issue by construction; H3 is in-scope for Pass 4.B. Pass 4.A architecture closed.

Rationale

Reasoning chain: ST session dfdee8e0 (premortem → 2 hardening fixes shipped commit 3f6dd0d) followed by generate_hypotheses (5 templates) + 3 add_evidence calls (d6767afe + 26380975 + a7ad8e0f) anchoring residual risks against actual code. H1 (Safari quota) is reliability 0.85 — known WebKit storage cap; mitigated when user installs PWA per manifest. H2 (action rotation) is reliability 0.95 — verified SyncRunner uses module-level import, not closure capture; queue stores payload not action ref. H3 (no edit) is reliability 0.9 — already in Pass 4.B scope per PILOT-READINESS. Together: Pass 4.A architecture is stable foundation for 4.B/4.C; no rework risk identified; pilot-readiness checklist gets H1 line item. architecture,real-estate,reversible,st-derived

Alternatives Rejected

Outcome

Pending