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

@@ -0,0 +1,35 @@
+---
+taskmaster_id: "5.3"
+status: "pending"
+priority: "high"
+depends_on: ["1", "2"]
+parent_id: "5"
+source: "taskmaster"
+generated_at: "2026-05-24T07:15:25.199Z"
+---
+
+# 5.3 - Implement bot command and notification foundation
+
+- [ ] 5.3 - Implement bot command and notification foundation #taskmaster #priority/high #status/pending ⏫ 🆔 tm-5-3 ⛔ tm-1 ⛔ tm-2
+
+## Metadata
+
+| Field | Value |
+| --- | --- |
+| Taskmaster ID | 5.3 |
+| Status | pending |
+| Priority | high |
+| Dependencies | 1, 2 |
+| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
+
+## Description
+
+Create the Telegram bot backend for commands, inline keyboards, callback queries, deep links, and outbound notifications.
+
+## Details
+
+Support start/help/link/status/request/offer/payment/dispute/settings basics. Use short opaque IDs or signed tokens for callback payloads. Process incoming updates idempotently with rate limits. Respect notification preferences, quiet/error states, failed delivery, blocked bot, and retry observability.
+
+## Verification
+
+See Telegram-native PRD acceptance criteria.