docs: assess scope and practical usability

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc

workplans/ADHOC-2026-08-24.md

@@ -0,0 +1,28 @@
+---
+id: TAMQ-WP-ADHOC-2026-08-24
+type: workplan
+title: "Refresh scope and assess practical usability"
+domain: communication
+repo: tmux-amq
+status: finished
+owner: codex
+topic_slug: coulomb-social
+created: "2026-08-24"
+updated: "2026-08-24"
+---
+
+# Refresh scope and assess practical usability
+
+## Assess implementation against intent and update scope
+
+```task
+id: TAMQ-WP-ADHOC-2026-08-24-T01
+status: done
+priority: medium
+```
+
+Reviewed the implementation and tests against `INTENT.md`, ran the 50-test
+suite with coverage, exercised the isolated socket/queue/history/export/shutdown
+workflow, and updated `SCOPE.md` with an evidence-based maturity assessment.
+Reliability residuals were handed to `TAMQ-WP-0003`; coordination-engine
+interoperability remains owned by `TAMQ-WP-0002`.

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

@@ -0,0 +1,67 @@
+---
+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.