tmux-amq/workplans/TAMQ-WP-0003-delivery-reliability.md

68 lines
1.8 KiB
Markdown
Raw Normal View History

---
id: TAMQ-WP-0003
type: workplan
title: "Delivery reliability and practical integration evidence"
domain: communication
repo: tmux-amq
status: active
owner: codex
topic_slug: coulomb-social
created: "2026-08-24"
updated: "2026-08-24"
---
# Delivery reliability and practical integration evidence
Close the reliability gaps found during the 2026-08-24 intent and usability
assessment before treating tmux-amq as an unattended local transport or as a
stable coordination-engine dependency.
## Enforce bounded delivery attempts
```task
id: TAMQ-WP-0003-T01
status: todo
priority: high
```
Persist attempt counts and failure reasons, apply the selected policy profile's
retry cap, define lease-expiry behavior, and introduce an inspectable terminal
failure state. Prove restart-safe behavior and avoid tight retry loops.
## Enforce acknowledgement semantics
```task
id: TAMQ-WP-0003-T02
status: wait
priority: high
```
Make `delivery_ack_mode` control whether injection completes delivery or waits
for explicit recipient acknowledgement. Specify timeout, redelivery, duplicate,
and late-acknowledgement behavior. This task follows the state model from T01.
## Add real tmux and PTY lifecycle coverage
```task
id: TAMQ-WP-0003-T03
status: todo
priority: high
```
Exercise a real tmux server, managed windows, control-mode injection, `tamq tap`,
service shutdown, endpoint disappearance, and restart recovery without starting
an external coding agent. Keep fast unit tests while adding a bounded integration
suite.
## Align CI and operator documentation
```task
id: TAMQ-WP-0003-T04
status: wait
priority: medium
```
Run the integration suite in Forgejo CI with explicit tmux and gita setup. Update
README claims about retries, acknowledgement, prerequisites, and maturity from
verified behavior. This task follows T01-T03.