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

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "5.7"
+status: "pending"
+priority: "high"
+depends_on: ["2", "3", "5"]
+parent_id: "5"
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 5.7 - Add admin and support surface for Telegram-originated cases
+
+- [ ] 5.7 - Add admin and support surface for Telegram-originated cases #taskmaster #priority/high #status/pending ⏫ 🆔 tm-5-7 ⛔ tm-2 ⛔ tm-3 ⛔ tm-5
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 5.7 |
+| Status | pending |
+| Priority | high |
+| Dependencies | 2, 3, 5 |
+| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
+
+## Description
+
+Give support/admin users visibility and controls for Telegram-originated users, payments, and bot events.
+
+## Details
+
+Admin UI/API should show Telegram linked identity, bot notification status, launch source, payment provider, and wallet/payment references. Support can resend links, revoke Telegram link, block bot access, and inspect Telegram-originated events. Admin overrides must use the same step-up or two-person policy as web flows when configured.
+
+## Verification
+
+See Telegram-native PRD acceptance criteria.