4cf5c49274
- 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/)
1.1 KiB
1.1 KiB
taskmaster_id, status, priority, depends_on, parent_id, source, generated_at
| taskmaster_id | status | priority | depends_on | parent_id | source | generated_at | ||
|---|---|---|---|---|---|---|---|---|
| 5.6 | pending | high |
|
5 | taskmaster | 2026-05-24T07:15:25.199Z |
5.6 - Expose escrow, delivery, dispute, and release actions safely
- 5.6 - Expose escrow, delivery, dispute, and release actions safely #taskmaster #priority/high #status/pending ⏫ 🆔 tm-5-6 ⛔ tm-4 ⛔ tm-5
Metadata
| Field | Value |
|---|---|
| Taskmaster ID | 5.6 |
| Status | pending |
| Priority | high |
| Dependencies | 4, 5 |
| Parent | 5 - Deliver Telegram-native app, bot, and wallet experience |
Description
Make Telegram actions useful for real escrow work while preserving backend state authority.
Details
Telegram users can see current escrow state, next allowed actions, and blockers. Delivery confirmation, evidence upload, refund request, dispute open/respond, and release approval must route through backend precondition checks. High-risk actions require fresh confirmation and audit logging with Telegram context. Disputed or held funds cannot be released through Telegram shortcuts.
Verification
See Telegram-native PRD acceptance criteria.