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

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "5"
+status: "in-progress"
+priority: "high"
+depends_on: []
+parent_id: ""
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 5 - Deliver Telegram-native app, bot, and wallet experience
+
+- [ ] 5 - Deliver Telegram-native app, bot, and wallet experience #taskmaster #priority/high #status/in-progress ⏫ 🆔 tm-5
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 5 |
+| Status | in-progress |
+| Priority | high |
+| Dependencies | None |
+| Parent | None |
+
+## Description
+
+Create a Telegram bot plus Mini App surface so users can complete Amanat buyer, seller, escrow, chat, dispute, payment, release/refund, and support workflows from inside Telegram.
+
+## Details
+
+Source PRD: .taskmaster/docs/prd-telegram-native-app-bot-wallet.md. Keep this as a separate delivery track from security remediation and Request Network migration. Identity, bot navigation, Mini App shell, and notifications can start behind flags; wallet/payment crediting and release/refund actions must use canonical backend authorization, provider adapter, funds ledger, escrow state machine, idempotency, and dispute holds.
+
+## Verification
+
+Use Telegram sandbox and production bot separation, Mini App client matrix testing, provider/wallet payment fixtures, backend authorization and ledger invariant tests, webhook/callback replay tests, and staged rollout analytics before launch.