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

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "5.5"
+status: "pending"
+priority: "high"
+depends_on: ["2", "4"]
+parent_id: "5"
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 5.5 - Add Telegram payment and wallet strategy
+
+- [ ] 5.5 - Add Telegram payment and wallet strategy #taskmaster #priority/high #status/pending ⏫ 🆔 tm-5-5 ⛔ tm-2 ⛔ tm-4
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 5.5 |
+| Status | pending |
+| Priority | high |
+| Dependencies | 2, 4 |
+| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
+
+## Description
+
+Evaluate and implement safe payment entry points for Telegram-native users without weakening escrow accounting.
+
+## Details
+
+Compare Bot API payments/Stars, Wallet Pay, TON Pay, TON Connect, Request Network links, and existing crypto checkout. Select a first payment path and document rejected options. Store provider, Telegram user ID, deep-link source, payment reference, invoice/order/request ID, currency, amount, expiration, and idempotency key. Wallet/TON flows must validate recipient, asset, amount, memo/reference, confirmation status, and reconciliation evidence before crediting escrow. Refund/release behavior must remain compatible with canonical ledger and dispute holds.
+
+## Verification
+
+See Telegram-native PRD acceptance criteria.