docs(audit): align documentation with post-remediation backend reality

- Update data model enums to match backend models
- Update API reference auth requirements
- Add dispute module references and warning blocks
- Add 2026-05-24 audit remediation callout to Overview
- Generate task breakdowns and audit artifacts
- Add doc alignment report (.taskmaster/reports/)

Taskmaster/Tasks/task-4-9.md

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "4.9"
+status: "pending"
+priority: "medium"
+depends_on: ["8"]
+parent_id: "4"
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 4.9 - Create migration and operational runbooks
+
+- [ ] 4.9 - Create migration and operational runbooks #taskmaster #priority/medium #status/pending 🔼 🆔 tm-4-9 ⛔ tm-8
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 4.9 |
+| Status | pending |
+| Priority | medium |
+| Dependencies | 8 |
+| Parent | 4 - Define backend security and refactor strategy from latest audit |
+
+## Description
+
+Document rollout, rollback, and incident response for the selected backend/funds architecture.
+
+## Details
+
+Include SHKeeper legacy read path, provider feature flag, ledger backfill, validation report before enforcement, rollback criteria, webhook cutoff, manual reconciliation, failed webhook, duplicate/missing payment, stuck release, disputed release attempt, compromised admin, leaked API key, provider outage, chain/RPC outage, suspicious payment proof, and npm/package compromise.
+
+## Verification
+
+Runbooks identify owner, trigger, detection signal, immediate action, recovery action, and post-incident documentation for each scenario.