From 4e71c5ca5c3583ce4f52e43b7bf19692bf48eed4 Mon Sep 17 00:00:00 2001 From: Dai Ha Date: Mon, 17 Aug 2026 14:26:14 +0200 Subject: [PATCH] CB-609: bridge_ack takes target, not ticket (template must match CLAUDE.md) --- 7-Use-Cases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/7-Use-Cases.md b/7-Use-Cases.md index a4ec80c..69e1745 100644 --- a/7-Use-Cases.md +++ b/7-Use-Cases.md @@ -366,7 +366,7 @@ below are the procedure — run them in order, every task, not only the big ones what makes them reliable. Where the project ships no such skill, spell the procedure out in the brief instead. The brief is self-contained — the worker sees your message and the repo, nothing of your context, your plan, or your screen. -5. **Collect** — `bridge_poll{ticket}` → `bridge_ack{ticket, msgId}`. Answer a worker's `bridge_ask` +5. **Collect** — `bridge_poll{ticket}` → `bridge_ack{target, msgId}`. Answer a worker's `bridge_ask` with `bridge_send{turnId, content}` — **not** `sessionId`. A worker gone quiet is diagnosed with `bridge_status`, never by reading its terminal; it also reports an open question and the `turnId` that answers it. **A worker's ask waits ~55 seconds, and no nudge makes that longer** — so never