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-2.md

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "2"
+status: "done"
+priority: "high"
+depends_on: []
+parent_id: ""
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 2 - Implement platform audit remediation plan
+
+- [x] 2 - Implement platform audit remediation plan #taskmaster #priority/high #status/done ⏫ 🆔 tm-2
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 2 |
+| Status | done |
+| Priority | high |
+| Dependencies | None |
+| Parent | None |
+
+## Description
+
+Address the code-backed security and consistency issues identified in the 2026-05-24 platform audit remediation PRD.
+
+## Details
+
+Source PRD: .taskmaster/docs/prd-platform-audit-remediation-plan-2026-05-24.md. Target backend hardening first, then documentation/runtime alignment. Delivery order suggested by PRD: security/auth, rate limiting, passkeys, Web3 verification, socket hardening, dispute hold controls, docs/API alignment.
+
+## Verification
+
+Add focused regression tests for route auth/ownership, passkey challenge/verification, Web3 verification semantics, socket authorization, rate limiting tiers, and payout/release dispute holds. Update API docs after behavior is implemented.