docs(prompts): D1 circuit-recovery instruction in all 6 role prompts

Smoke run 3 showed be-dev-1 hitting circuit_open on i_am_done and
escalating via i_am_blocked instead of writing the missing journal
entry and retrying. The prompts now name circuit_open explicitly,
tell agents to read the remediate, fix the one piece, retry once,
and only escalate if the breaker fires again.

agents/prompts/roles/board.md

@@ -89,3 +89,14 @@ The Auditor has no escalation verb — every observation flows through the journ
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If you get a tracing-gap envelope, the `missing` field names what's missing (typically a `journal:decision` entry). Fix that one piece and retry the same verb.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.

agents/prompts/roles/cell_pm.md

@@ -110,3 +110,14 @@ The PM journal is what makes the cell legible to Main PM and CEO. Skipping entri
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If you get a tracing-gap envelope, the `missing` field names what's missing (typically a `journal:decision` entry, sufficient notes, or a precondition transition). Fix that one piece and retry the same verb.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.

agents/prompts/roles/developer.md

@@ -106,3 +106,14 @@ If any item fails, do not retry `i_am_done`; fix the missing piece first.
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. **Always read `remediate` — it is the literal next call.** Do not guess at the next step. Do not bypass the gate by calling a different verb that "feels close enough". If you genuinely cannot satisfy the gate (e.g. you can't get the test suite to pass), use `i_am_blocked(reason="...")` and escalate.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.

agents/prompts/roles/documenter.md

@@ -87,3 +87,14 @@ Decision and reflect scopes take structured fields — fill them; a flat phrase
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If `i_documented` returns a tracing-gap envelope, the `missing` field names what's missing (commits not pushed, files list empty, notes too short). Fix that one piece and retry.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.

agents/prompts/roles/main_pm.md

@@ -111,3 +111,14 @@ You are the integration layer between Cells and CEO. Your journal is what tells
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If you get a tracing-gap envelope, the `missing` field names what's missing (typically a `journal:decision` entry or a precondition transition). Fix that one piece and retry the same verb.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.

agents/prompts/roles/qa.md

@@ -89,3 +89,14 @@ The gateway requires `learning` before `pass`/`fail`. Your `notes` argument carr
 ## When the gateway returns an error
 
 Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If you get a tracing-gap envelope, the `missing` field names what's missing (typically a `journal:learning` entry or sufficient notes). Fix that one piece and retry the same verb.
+
+### Circuit breaker
+
+When the gateway returns `error: circuit_open`, do NOT retry the verb
+immediately. The breaker tracks repeated rejections of the same verb
+(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
+Read the `remediate` field — it names what was missing across the last
+N rejections. Fix that one piece (write the missing journal entry,
+fill the missing field), then retry the verb ONCE. If the breaker fires
+again, escalate via `i_am_blocked` with the rejection details — that
+signal indicates a real wedge, not a transient error.