feat: add hash routing for pushy agents

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

workplans/TAMQ-WP-0011-hash-routing-for-pushy-agents.md

@@ -4,13 +4,13 @@ type: workplan
 title: "Hash-prefixed routing for pushy agent sessions"
 domain: communication
 repo: tmux-amq
-status: active
+status: finished
 owner: codex
 topic_slug: coulomb-social
 planning_priority: P0
 planning_order: 16
 created: "2026-08-24"
-updated: "2026-08-24"
+updated: "2026-08-25"
 state_hub_workstream_id: "9a38f0c3-bd98-51ae-a6ad-502bef94a38f"
 ---
 
@@ -35,7 +35,7 @@ comment and a clear coding-agent prompt.
 
 ```task
 id: TAMQ-WP-0011-T01
-status: progress
+status: done
 priority: high
 state_hub_task_id: "d50b09b2-e4ad-5eb4-b833-2d9a62b5ff1f"
 ```
@@ -48,7 +48,7 @@ validation, sender identity, and ordinary-input pass-through.
 
 ```task
 id: TAMQ-WP-0011-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "1170ae19-a2ce-5f50-8a43-41b9625621e7"
 ```
@@ -61,7 +61,7 @@ command is supplied and keep legacy `--tap` behavior distinct.
 
 ```task
 id: TAMQ-WP-0011-T03
-status: todo
+status: done
 priority: high
 state_hub_task_id: "2a355d88-5272-58c2-a4f8-82df6cac7c3e"
 ```
@@ -71,3 +71,20 @@ CLI, PTY, and real two-window tmux coverage proving one `#repo:` source line
 creates one durable message, one target submission, and no bounced message.
 Document the interaction, run full checks, install, and exercise a controlled
 live commanded pushy session if it can be isolated from user input.
+
+## Completion evidence
+
+- `make check`: 120 tests passed, including a real isolated two-window tmux
+  test proving one `#activity-core:` source line creates one durable message,
+  one submitted target prompt, an `injected` transition, and no feedback or
+  duplicate delivery on a second service pass.
+- Coverage: 77% overall; routing is 100%, tmux management is 82%, terminal
+  framing is 85%, and the service is 77%.
+- `make install`: installed `tmux-amq==0.1.0` with hash routing and automatic
+  PTY observation for newly created commanded pushy windows.
+- The inbound `# from sender:` envelope is deliberately outside the outbound
+  route grammar, preventing tapped targets from bouncing injected messages.
+- The operator's existing session was not recreated or modified. Existing
+  windows must be recreated to gain PTY observation; this preserves live input.
+- Bounded retry and acknowledgement-policy residuals remain owned by
+  `TAMQ-WP-0003`; this workplan creates no additional residual record.