From 7822772905bb28ba0c99d0512ec3a755e5c4b114 Mon Sep 17 00:00:00 2001 From: Dai Ha Date: Sun, 16 Aug 2026 19:05:06 +0200 Subject: [PATCH] =?UTF-8?q?CB-582:=20bridge=5Fstatus=20now=20reports=20an?= =?UTF-8?q?=20open=20question=20=E2=80=94=20say=20so,=20and=20keep=20the?= =?UTF-8?q?=20warning?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The prompt is part of the product: CB-582 changed what bridge_status returns, so the primary's step 5 was no longer the whole truth. The second half matters more than the first. A nudge makes a lead more likely to notice an ask; it does not widen the ~55s window, which is bounded by the WORKER's own MCP client timeout, not by anything the daemon chooses. Without that sentence a lead reads 'the ask now nudges me' as 'asking works now' and briefs a worker to ask — which is the failure CB-582 was filed about. --- CLAUDE.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 6ea95c0..899dacb 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -80,7 +80,9 @@ below are the procedure — run them in order, every task, not only the big ones of your context, your plan, or your screen. 5. **Collect** — `bridge_poll{ticket}` → `bridge_ack{ticket, 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. + `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 + brief a worker to "ask me". Decide before you delegate, or give it an explicit default. 6. **Verify yourself.** Re-run the build and the checks. A worker cannot run your IDE tooling, any forge tools it appears to have hold a blocked credential and fail, and a piped command (`… | tail`) hides failures behind a zero exit — never promote a worker's "clean" to a fact.