coulomb/tmux-amq
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: complete reliable coordination adapter
Some checks failed
tamq-ci / test (push) Failing after 5s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc
This commit is contained in:
tegwick 2026-08-26 08:11:09 +02:00
parent 25113f463e
commit 6d2ccc7760
30 changed files with 2553 additions and 144 deletions
Download patch file Download diff file Expand all files Collapse all files

35
workplans/TAMQ-WP-0003-delivery-reliability.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Delivery reliability and practical integration evidence"
domain: communication
repo: tmux-amq
status: active
status: finished
owner: codex
topic_slug: coulomb-social
created: "2026-08-24"
updated: "2026-08-24"
updated: "2026-08-26"
state_hub_workstream_id: "7961275b-8f1f-5827-b9fc-46b3ac35fb73"
---
@ -22,7 +22,7 @@ stable coordination-engine dependency.
```task
id: TAMQ-WP-0003-T01
status: todo
status: done
priority: high
state_hub_task_id: "52c43745-5c28-599e-b74c-0386d5b51e68"
```
@ -31,11 +31,18 @@ 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.
Completed with schema-v6 persistent attempt, deadline, and failure fields.
Lease acquisition consumes an attempt; write failure or lease expiry releases
ownership into configured bounded backoff. The selected endpoint policy caps
attempts from one to nine, exhaustion becomes `failed`, and `tamq retry` is the
explicit recovery action. Protocol events retain attempt, cap, reason, and
retry timing without raw terminal output.
## Enforce acknowledgement semantics
```task
id: TAMQ-WP-0003-T02
status: wait
status: done
priority: high
state_hub_task_id: "ff88d6c9-f4d7-52c7-9645-7c3a7a34ccb4"
```
@ -44,6 +51,13 @@ 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.
Completed for every automatic delivery mode. `injected` completes after a
successful terminal write. `acknowledged` enters `awaiting_ack`, schedules
same-message-ID redelivery after the configured deadline, records `ack_timeout`
on retries and exhaustion, and accepts a late acknowledgement even after
`failed`. The contract warns that redelivery can duplicate terminal
presentation and never represents task completion.
## Add real tmux and PTY lifecycle coverage
```task
@ -70,7 +84,7 @@ entirely as documented.
```task
id: TAMQ-WP-0003-T04
status: wait
status: done
priority: medium
state_hub_task_id: "44939829-a52e-582a-b06b-60337b36080e"
```
@ -78,3 +92,14 @@ state_hub_task_id: "44939829-a52e-582a-b06b-60337b36080e"
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.
Forgejo CI now runs `make check`, including generated-gita and isolated tmux
installation fixtures, compile/diff checks, and CLI/capture help smokes on
Python 3.11. README, SCOPE, configuration examples, and the agent introduction
describe the implemented state machine and terminal-comprehension boundary.
## Residuals
Long-duration and arbitrary-terminal soak coverage remains a maturity gate in
SCOPE rather than a missing part of this bounded reliability contract. The
coordination runtime above TAMQ remains owned by coordination-engine.