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

38
workplans/TAMQ-WP-0002-coordination-engine-adapter.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Coordination-engine adapter boundary"
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: "48da5fa7-b7bf-5d13-8edc-b90f266e241c"
---
@ -22,7 +22,7 @@ workflow/orchestration policy in coordination-engine.
```task
id: TAMQ-WP-0002-T01
status: todo
status: done
priority: high
state_hub_task_id: "a222dab7-edea-58c6-9dab-d684eb65c412"
```
@ -31,11 +31,17 @@ Define request, response, identity, delivery, acknowledgement, retry, and
failure semantics for a coordination-engine client. Resolve protocol-version
negotiation and document which system owns each state transition.
The implemented contract is `spec/coordination-engine-adapter-v0.1.md`. It
defines same-user socket authentication, major-version and capability
negotiation, exact endpoint resolution, message/correlation identity,
idempotency conflicts, bounded delivery states, ack timeouts, late
acknowledgement, recovery, and the TAMQ/coordination ownership boundary.
## Implement the coordination-engine client adapter
```task
id: TAMQ-WP-0002-T02
status: wait
status: done
priority: high
state_hub_task_id: "195db613-05a3-58d8-9e94-2db34920576f"
```
@ -43,11 +49,18 @@ state_hub_task_id: "195db613-05a3-58d8-9e94-2db34920576f"
Implement the adapter against the stable socket contract without importing
tmux/control-mode concerns into coordination-engine. This task waits for T01.
`tamq.client` provides a transport-only async client and
`CoordinationEngineAdapter`. It opens a fresh socket connection per operation,
resolves one live repository endpoint, maps the coordination lease ID to a
durable idempotency key, preserves trigger correlation metadata, and exposes
receipt, acknowledgement, and terminal retry operations. Protocol constants
are separate from the service and terminal implementation.
## Prove interoperability and recovery
```task
id: TAMQ-WP-0002-T03
status: wait
status: done
priority: high
state_hub_task_id: "23c7f6c7-be48-5b6c-b85c-ae05d82cc277"
```
@ -55,3 +68,18 @@ state_hub_task_id: "23c7f6c7-be48-5b6c-b85c-ae05d82cc277"
Add end-to-end coverage for delivery, acknowledgement, reconnect, replay,
deduplication, incompatible protocol versions, and endpoint disappearance.
Update both repositories' operator documentation with the verified workflow.
Unix-socket integration tests cover negotiation, identical-wake deduplication,
idempotency conflict, durable receipt recovery after service restart,
incompatible protocol, and disappeared endpoints. Reliability tests cover
delivery, explicit and late acknowledgement, same-ID ack-timeout redelivery,
lease expiry, exhaustion, and retry reset. JSONL replay now uses deterministic
idempotency while retaining normal gita validation. TAMQ documentation and the
coordination-engine worker-service specification link the verified contract.
## Residuals
This workplan does not implement coordination-engine's trigger observer,
coordination leases, actionability decisions, checkpoints, or State Hub
projection. Those remain owned by `COORDINATION-WP-0003` and consume this
adapter rather than expanding TAMQ's scope.