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

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "4.8"
+status: "pending"
+priority: "medium"
+depends_on: ["2", "3", "4", "5", "6", "7"]
+parent_id: "4"
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 4.8 - Make backend-core stack decision
+
+- [ ] 4.8 - Make backend-core stack decision #taskmaster #priority/medium #status/pending 🔼 🆔 tm-4-8 ⛔ tm-2 ⛔ tm-3 ⛔ tm-4 ⛔ tm-5 ⛔ tm-6 ⛔ tm-7
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 4.8 |
+| Status | pending |
+| Priority | medium |
+| Dependencies | 2, 3, 4, 5, 6, 7 |
+| Parent | 4 - Define backend security and refactor strategy from latest audit |
+
+## Description
+
+Choose whether the security-critical backend core remains TypeScript or moves to Go/Kotlin/Rust/Python.
+
+## Details
+
+Evaluate team capability, two-year maintainability, operational footprint, rewrite cost, dual-stack complexity, auditability, supply-chain exposure, and which modules belong in a payment/auth/escrow core versus the existing marketplace/chat API.
+
+## Verification
+
+Architecture decision record states chosen stack, scope of extraction, non-goals, migration phases, rollback criteria, and owners.