flow-workflows 0.71.0 → 0.73.0

package/adapters/codex/CORE.md

@@ -17,7 +17,7 @@ Every `$flow-*` command assumes these rules. They are stated once, here, so a co
 carries what is specific to its phase. Read this once per session; a command that says "load
 `flow-core`" means this file.
 
-**This file belongs to flow `0.71.0`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.73.0`.** Compare it once, at the start of the session, against
 `version` in `~/.claude/flow/.claude-plugin/plugin.json`. The two differing means the session
 is running a **mixture** — the commands from one copy of the plugin, these shared rules from another
 — which is exactly what happens when a branch or a release candidate is loaded over an installed
@@ -237,7 +237,9 @@ terminal by construction, the turn is over before you notice.
   (`guided`/`auto` chaining, §2), the turn opens with the call that starts it, not with prose about
   the one that ended. **A report is never the last thing in a turn you meant to continue.**
 - **Progress belongs to the panel, not to a turn.** Someone watching reads the live panel (§4):
-  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both.
+  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both. **An answered
+  question is progress too**: the `Decision` line and the panel's claim on the user go the moment
+  the answer arrives, before the work resumes (§4.4e).
 - **Stopping? Then say so.** `I need:` names the decision or the action you are waiting on. It
   never announces that you are continuing — if you were, you would not be writing this header.
 
@@ -269,8 +271,17 @@ right now. **Any progress line you were about to type into the chat is a panel u
 **Two transports, one document.** When the tools `panel_set` / `panel_patch` / `panel_get` are
 available, this console is a pane of agent-terminal: publish the panel through them (§4.2) and
 **stop writing `.claude/work/<work>/panel.json`** — while a pane is claimed, its file is not read at
-all. When the tools are not there, write the file exactly as before (§4.3). No work folder
-(lightweight `respond`/`green`) → nothing to publish, either way.
+all. When they are not there, write the file exactly as before (§4.3). No work folder (lightweight
+`respond`/`green`) → nothing to publish, either way.
+
+**Look for them before you conclude they are missing**, once per session, in pre-flight. A harness
+namespaces an MCP server's tools, so what you are looking for is a tool whose name *ends* in
+`panel_set` — `mcp__panel__panel_set` on Claude Code, another prefix elsewhere — and the name is
+whatever it is called there, not `panel_set`. It may also be **deferred**: listed by name with no
+schema, uncallable until you load it, and indistinguishable from absent unless you read that list.
+A deferred tool is a tool that is there; load the three schemas and publish. The file is the answer
+only after that search comes back empty — and this is the one paragraph that decides it, because
+prose describing a file is otherwise obeyed to the letter.
 
 ### 4.1 The document — the same whichever transport carries it
 
@@ -297,7 +308,7 @@ all. When the tools are not there, write the file exactly as before (§4.3). No
 
 - **`mark` says what a line is**; the reader draws it. `done` · `current` (at most one) · `pending` · `wait` (waiting on someone else: an open MR/PR, a user decision) · `block` · `info`. Marked lines form an aligned column: symbol, `ref`, text, link pinned right. Do not set `style` on a marked line — except `mark: "info"` + `style: ok|warn|error` when the colour *is* the information (a monitoring verdict).
 - **`ref` need not be a number**: `#1`, `#3–#6`, `Now`, `Next`, `Decision`. Column width is per block; blocks are separated by blank lines — use them so the MR/PR train and the labels below do not drag each other wide.
-- **`link` is a field, never a URL inside `text`.**
+- **`link` is a field, never a URL inside `text`** — and **every line that names an MR/PR carries it**: the train entries, a blocker about somebody else's MR/PR, a `Now` or `Next` about the open one. The URL is in `meta.json.mrs[].url` or in whatever recorded that blocker; a bare `!10327` typed into `text` is a number the reader cannot make clickable, which is the whole point of the field. No URL recorded anywhere → the number in `text` and nothing else, and go and record it.
 - **Order:** (1) work title (`style: title`, no mark); (2) the MR/PR train, one entry per `meta.json.mrs[]` with `ref` `#n`, short title, real-state `mark`, `link` when there is a URL — not-started entries collapse into one `#a–#z` `pending` line; omit the block without `mrs`; (3) `Now` — what is running, the one fact `meta.json` cannot hold; (4) `Next`; (5) `Decision`, `mark: wait`, **only** when parked on the user — over the tools it travels with `attention: "wait"` (§4.2), and both are cleared together; (6) blockers, `mark: block` (a sibling repo with `contract_handoff: pending`, a red pipeline, an unmerged dependency).
 - **Rules:** `phase` is the phase you are **running now** (not `meta.json.phase`, which advances only at Close). `header: true` means ticket, type, phase and age are drawn by the reader — do not repeat them in `lines`. Keep it under ~14 lines. Every fact from `meta.json` and the artifacts — an invented MR/PR state is worse than a blank panel. Write in the language of the work's artifacts.
 
@@ -366,6 +377,13 @@ halfway is not shown as finished. When the stretch will outlast the ~30 min stal
 `stale_after_minutes` to what it will really take; (d) wherever `## Close` updates `meta.json`. A
 held panel still goes stale: the app stamps each delivery's arrival.
 
+**(e) The moment a question is answered or a gate is cleared** — before you resume the work, not at
+the next stop. Drop the `Decision` line, clear `attention`, and move `Now` on: one patch, the first
+thing you do with the answer. A panel still asking what the user already answered is worse than one
+that never asked, because they answered it and the screen says it did not land; and an `attention`
+nobody clears keeps that tab claiming them for ever. The same applies to a blocker that lifted and
+to a `wait` line whose MR/PR merged.
+
 ### 4.5 `meta.json.cost[]` — what a phase measured, when it could
 
 A phase that can measure what it spent appends one entry: `{ "phase": "review", "at": "<ISO>",

package/adapters/codex/skills/flow-doctor/SKILL.md

@@ -199,7 +199,7 @@ refuse) · **degraded** (it runs, quietly worse than the config promises), plus
   `.agents/agents`, or a plugin. Report each missing name and that it falls back to `general-purpose`
   (a skill: skipped) — a panel missing agents reviews less and still reports a clean pass.
 - Harness cannot set a model per subagent → note that every `models.*` value degrades to inheritance.
-- **Where the live panel will go this session** (flow-core §4): `panel_set` / `panel_patch` exposed → the terminal draws the panel and no `panel.json` is written; absent → the panel is that file, as before. Neither is a fault — one line saying which one this session gets.
+- **Where the live panel will go this session** (flow-core §4): a tool whose name ends in `panel_set` / `panel_patch` — namespaced by the harness (`mcp__panel__panel_set` on Claude Code) and possibly **deferred**, which reads as absent until the list of deferred tools is checked → the terminal draws the panel and no `panel.json` is written; genuinely absent → the panel is that file, as before. Neither is a fault — one line naming the tools as they are actually called here, or saying the file is the transport.
 
 ### 2.3 Knowledge sources
 

package/adapters/codex/skills/flow-work-README/SKILL.md

@@ -159,7 +159,7 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 
 ## The panel document
 
-`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools, or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
+`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools (namespaced by the harness, and possibly deferred: flow-core §4 says how to find them), or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
 
 ```json
 {
@@ -185,13 +185,13 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 - **`lines`** — one entry per line. Bare string = plain line; object takes `text`, `ref`, `mark`, `link`, `style`, `indent`. Empty string = blank line **and alignment block separator** (`ref` widths per block).
 - **`mark`** — `done` · `current` · `pending` · `wait` (waiting on someone else) · `block` · `info`; the reader draws it. `style` on a marked line overrides its colour — right only when the colour *is* the information.
 - **`ref`** — the column label: `#1`, `#3–#6`, `Now`, `Next`, `Decision`.
-- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable.
+- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable. Every line naming an MR/PR carries one — train entry, blocker about another MR/PR, `Now`/`Next` about the open one (flow-core §4.1).
 - **`stale_after_minutes`** — raises the 30-minute staleness threshold for a stretch known to run long.
 - **`style`** — `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`; semantic names, the reader owns the palette.
 - **`header`** — `true` (default): the reader draws ticket, type, phase and age, which never belong in `lines`. `false` hands every line to the writer.
 - **`phase`** — the phase running **right now** (`meta.json.phase` advances only at close); the reader prefers it.
 - **`updated_at`** — local ISO-8601 with offset from the real clock, never carried over; lets the reader flag a stale snapshot. Over the tools the app stamps each delivery itself.
-- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever.
+- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever — it goes, with the `Decision` line, the moment the question is answered (flow-core §4.4e).
 - **`key`** *(tools only)* — a unique, never-painted name on any line a later `panel_patch` may replace or delete (`title`, `mr-1`, `now`, `next`, `decision`, `block-1`).
 
 **No headings over the train.** A shipped MR/PR is *open, waiting to merge*; `mark` says it per entry — `wait` shipped, `current` being worked, `done` only merged.

package/adapters/codex/skills/flow-work-resume/SKILL.md

@@ -117,7 +117,7 @@ After a break the panel is most likely stale, and a resumed session is exactly w
 
 - `phase` = the phase you are resuming into (`meta.json.phase` does not yet say it).
 - `Now` in prose; `Next` names the command §4 suggested.
-- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's.
+- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's. It goes the moment they make it (flow-core §4.4e), not at the next stop.
 - `block` lines for the blockers §4 surfaced (`contract_handoff` `pending` in a sibling repo, a red pipeline, an unmerged dependency).
 - Train: one entry per `meta.json.mrs[]`, not-started collapsed into one `#a–#z` line; omit without `mrs`.
 - `updated_at` from `date -Iseconds` when the panel goes to the file; every fact from `meta.json` and the artifacts; language of the work's artifacts.

package/adapters/gemini/CORE.md

@@ -16,7 +16,7 @@ Every `/flow:*` command assumes these rules. They are stated once, here, so a co
 carries what is specific to its phase. Read this once per session; a command that says "load
 `flow-core`" means this file.
 
-**This file belongs to flow `0.71.0`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.73.0`.** Compare it once, at the start of the session, against
 `version` in `~/.claude/flow/.claude-plugin/plugin.json`. The two differing means the session
 is running a **mixture** — the commands from one copy of the plugin, these shared rules from another
 — which is exactly what happens when a branch or a release candidate is loaded over an installed
@@ -236,7 +236,9 @@ terminal by construction, the turn is over before you notice.
   (`guided`/`auto` chaining, §2), the turn opens with the call that starts it, not with prose about
   the one that ended. **A report is never the last thing in a turn you meant to continue.**
 - **Progress belongs to the panel, not to a turn.** Someone watching reads the live panel (§4):
-  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both.
+  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both. **An answered
+  question is progress too**: the `Decision` line and the panel's claim on the user go the moment
+  the answer arrives, before the work resumes (§4.4e).
 - **Stopping? Then say so.** `I need:` names the decision or the action you are waiting on. It
   never announces that you are continuing — if you were, you would not be writing this header.
 
@@ -268,8 +270,17 @@ right now. **Any progress line you were about to type into the chat is a panel u
 **Two transports, one document.** When the tools `panel_set` / `panel_patch` / `panel_get` are
 available, this console is a pane of agent-terminal: publish the panel through them (§4.2) and
 **stop writing `.claude/work/<work>/panel.json`** — while a pane is claimed, its file is not read at
-all. When the tools are not there, write the file exactly as before (§4.3). No work folder
-(lightweight `respond`/`green`) → nothing to publish, either way.
+all. When they are not there, write the file exactly as before (§4.3). No work folder (lightweight
+`respond`/`green`) → nothing to publish, either way.
+
+**Look for them before you conclude they are missing**, once per session, in pre-flight. A harness
+namespaces an MCP server's tools, so what you are looking for is a tool whose name *ends* in
+`panel_set` — `mcp__panel__panel_set` on Claude Code, another prefix elsewhere — and the name is
+whatever it is called there, not `panel_set`. It may also be **deferred**: listed by name with no
+schema, uncallable until you load it, and indistinguishable from absent unless you read that list.
+A deferred tool is a tool that is there; load the three schemas and publish. The file is the answer
+only after that search comes back empty — and this is the one paragraph that decides it, because
+prose describing a file is otherwise obeyed to the letter.
 
 ### 4.1 The document — the same whichever transport carries it
 
@@ -296,7 +307,7 @@ all. When the tools are not there, write the file exactly as before (§4.3). No
 
 - **`mark` says what a line is**; the reader draws it. `done` · `current` (at most one) · `pending` · `wait` (waiting on someone else: an open MR/PR, a user decision) · `block` · `info`. Marked lines form an aligned column: symbol, `ref`, text, link pinned right. Do not set `style` on a marked line — except `mark: "info"` + `style: ok|warn|error` when the colour *is* the information (a monitoring verdict).
 - **`ref` need not be a number**: `#1`, `#3–#6`, `Now`, `Next`, `Decision`. Column width is per block; blocks are separated by blank lines — use them so the MR/PR train and the labels below do not drag each other wide.
-- **`link` is a field, never a URL inside `text`.**
+- **`link` is a field, never a URL inside `text`** — and **every line that names an MR/PR carries it**: the train entries, a blocker about somebody else's MR/PR, a `Now` or `Next` about the open one. The URL is in `meta.json.mrs[].url` or in whatever recorded that blocker; a bare `!10327` typed into `text` is a number the reader cannot make clickable, which is the whole point of the field. No URL recorded anywhere → the number in `text` and nothing else, and go and record it.
 - **Order:** (1) work title (`style: title`, no mark); (2) the MR/PR train, one entry per `meta.json.mrs[]` with `ref` `#n`, short title, real-state `mark`, `link` when there is a URL — not-started entries collapse into one `#a–#z` `pending` line; omit the block without `mrs`; (3) `Now` — what is running, the one fact `meta.json` cannot hold; (4) `Next`; (5) `Decision`, `mark: wait`, **only** when parked on the user — over the tools it travels with `attention: "wait"` (§4.2), and both are cleared together; (6) blockers, `mark: block` (a sibling repo with `contract_handoff: pending`, a red pipeline, an unmerged dependency).
 - **Rules:** `phase` is the phase you are **running now** (not `meta.json.phase`, which advances only at Close). `header: true` means ticket, type, phase and age are drawn by the reader — do not repeat them in `lines`. Keep it under ~14 lines. Every fact from `meta.json` and the artifacts — an invented MR/PR state is worse than a blank panel. Write in the language of the work's artifacts.
 
@@ -365,6 +376,13 @@ halfway is not shown as finished. When the stretch will outlast the ~30 min stal
 `stale_after_minutes` to what it will really take; (d) wherever `## Close` updates `meta.json`. A
 held panel still goes stale: the app stamps each delivery's arrival.
 
+**(e) The moment a question is answered or a gate is cleared** — before you resume the work, not at
+the next stop. Drop the `Decision` line, clear `attention`, and move `Now` on: one patch, the first
+thing you do with the answer. A panel still asking what the user already answered is worse than one
+that never asked, because they answered it and the screen says it did not land; and an `attention`
+nobody clears keeps that tab claiming them for ever. The same applies to a blocker that lifted and
+to a `wait` line whose MR/PR merged.
+
 ### 4.5 `meta.json.cost[]` — what a phase measured, when it could
 
 A phase that can measure what it spent appends one entry: `{ "phase": "review", "at": "<ISO>",

package/adapters/gemini/commands/flow/doctor.toml

@@ -195,7 +195,7 @@ refuse) · **degraded** (it runs, quietly worse than the config promises), plus
   `.agents/agents`, or a plugin. Report each missing name and that it falls back to `general-purpose`
   (a skill: skipped) — a panel missing agents reviews less and still reports a clean pass.
 - Harness cannot set a model per subagent → note that every `models.*` value degrades to inheritance.
-- **Where the live panel will go this session** (flow-core §4): `panel_set` / `panel_patch` exposed → the terminal draws the panel and no `panel.json` is written; absent → the panel is that file, as before. Neither is a fault — one line saying which one this session gets.
+- **Where the live panel will go this session** (flow-core §4): a tool whose name ends in `panel_set` / `panel_patch` — namespaced by the harness (`mcp__panel__panel_set` on Claude Code) and possibly **deferred**, which reads as absent until the list of deferred tools is checked → the terminal draws the panel and no `panel.json` is written; genuinely absent → the panel is that file, as before. Neither is a fault — one line naming the tools as they are actually called here, or saying the file is the transport.
 
 ### 2.3 Knowledge sources
 

package/adapters/gemini/commands/flow/work/README.toml

@@ -155,7 +155,7 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 
 ## The panel document
 
-`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools, or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
+`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools (namespaced by the harness, and possibly deferred: flow-core §4 says how to find them), or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
 
 ```json
 {
@@ -181,13 +181,13 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 - **`lines`** — one entry per line. Bare string = plain line; object takes `text`, `ref`, `mark`, `link`, `style`, `indent`. Empty string = blank line **and alignment block separator** (`ref` widths per block).
 - **`mark`** — `done` · `current` · `pending` · `wait` (waiting on someone else) · `block` · `info`; the reader draws it. `style` on a marked line overrides its colour — right only when the colour *is* the information.
 - **`ref`** — the column label: `#1`, `#3–#6`, `Now`, `Next`, `Decision`.
-- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable.
+- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable. Every line naming an MR/PR carries one — train entry, blocker about another MR/PR, `Now`/`Next` about the open one (flow-core §4.1).
 - **`stale_after_minutes`** — raises the 30-minute staleness threshold for a stretch known to run long.
 - **`style`** — `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`; semantic names, the reader owns the palette.
 - **`header`** — `true` (default): the reader draws ticket, type, phase and age, which never belong in `lines`. `false` hands every line to the writer.
 - **`phase`** — the phase running **right now** (`meta.json.phase` advances only at close); the reader prefers it.
 - **`updated_at`** — local ISO-8601 with offset from the real clock, never carried over; lets the reader flag a stale snapshot. Over the tools the app stamps each delivery itself.
-- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever.
+- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever — it goes, with the `Decision` line, the moment the question is answered (flow-core §4.4e).
 - **`key`** *(tools only)* — a unique, never-painted name on any line a later `panel_patch` may replace or delete (`title`, `mr-1`, `now`, `next`, `decision`, `block-1`).
 
 **No headings over the train.** A shipped MR/PR is *open, waiting to merge*; `mark` says it per entry — `wait` shipped, `current` being worked, `done` only merged.

package/adapters/gemini/commands/flow/work/resume.toml

@@ -113,7 +113,7 @@ After a break the panel is most likely stale, and a resumed session is exactly w
 
 - `phase` = the phase you are resuming into (`meta.json.phase` does not yet say it).
 - `Now` in prose; `Next` names the command §4 suggested.
-- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's.
+- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's. It goes the moment they make it (flow-core §4.4e), not at the next stop.
 - `block` lines for the blockers §4 surfaced (`contract_handoff` `pending` in a sibling repo, a red pipeline, an unmerged dependency).
 - Train: one entry per `meta.json.mrs[]`, not-started collapsed into one `#a–#z` line; omit without `mrs`.
 - `updated_at` from `date -Iseconds` when the panel goes to the file; every fact from `meta.json` and the artifacts; language of the work's artifacts.

package/adapters/hermes/CORE.md

@@ -17,7 +17,7 @@ Every `/flow-*` command assumes these rules. They are stated once, here, so a co
 carries what is specific to its phase. Read this once per session; a command that says "load
 `flow-core`" means this file.
 
-**This file belongs to flow `0.71.0`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.73.0`.** Compare it once, at the start of the session, against
 `version` in `~/.claude/flow/.claude-plugin/plugin.json`. The two differing means the session
 is running a **mixture** — the commands from one copy of the plugin, these shared rules from another
 — which is exactly what happens when a branch or a release candidate is loaded over an installed
@@ -237,7 +237,9 @@ terminal by construction, the turn is over before you notice.
   (`guided`/`auto` chaining, §2), the turn opens with the call that starts it, not with prose about
   the one that ended. **A report is never the last thing in a turn you meant to continue.**
 - **Progress belongs to the panel, not to a turn.** Someone watching reads the live panel (§4):
-  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both.
+  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both. **An answered
+  question is progress too**: the `Decision` line and the panel's claim on the user go the moment
+  the answer arrives, before the work resumes (§4.4e).
 - **Stopping? Then say so.** `I need:` names the decision or the action you are waiting on. It
   never announces that you are continuing — if you were, you would not be writing this header.
 
@@ -269,8 +271,17 @@ right now. **Any progress line you were about to type into the chat is a panel u
 **Two transports, one document.** When the tools `panel_set` / `panel_patch` / `panel_get` are
 available, this console is a pane of agent-terminal: publish the panel through them (§4.2) and
 **stop writing `.claude/work/<work>/panel.json`** — while a pane is claimed, its file is not read at
-all. When the tools are not there, write the file exactly as before (§4.3). No work folder
-(lightweight `respond`/`green`) → nothing to publish, either way.
+all. When they are not there, write the file exactly as before (§4.3). No work folder (lightweight
+`respond`/`green`) → nothing to publish, either way.
+
+**Look for them before you conclude they are missing**, once per session, in pre-flight. A harness
+namespaces an MCP server's tools, so what you are looking for is a tool whose name *ends* in
+`panel_set` — `mcp__panel__panel_set` on Claude Code, another prefix elsewhere — and the name is
+whatever it is called there, not `panel_set`. It may also be **deferred**: listed by name with no
+schema, uncallable until you load it, and indistinguishable from absent unless you read that list.
+A deferred tool is a tool that is there; load the three schemas and publish. The file is the answer
+only after that search comes back empty — and this is the one paragraph that decides it, because
+prose describing a file is otherwise obeyed to the letter.
 
 ### 4.1 The document — the same whichever transport carries it
 
@@ -297,7 +308,7 @@ all. When the tools are not there, write the file exactly as before (§4.3). No
 
 - **`mark` says what a line is**; the reader draws it. `done` · `current` (at most one) · `pending` · `wait` (waiting on someone else: an open MR/PR, a user decision) · `block` · `info`. Marked lines form an aligned column: symbol, `ref`, text, link pinned right. Do not set `style` on a marked line — except `mark: "info"` + `style: ok|warn|error` when the colour *is* the information (a monitoring verdict).
 - **`ref` need not be a number**: `#1`, `#3–#6`, `Now`, `Next`, `Decision`. Column width is per block; blocks are separated by blank lines — use them so the MR/PR train and the labels below do not drag each other wide.
-- **`link` is a field, never a URL inside `text`.**
+- **`link` is a field, never a URL inside `text`** — and **every line that names an MR/PR carries it**: the train entries, a blocker about somebody else's MR/PR, a `Now` or `Next` about the open one. The URL is in `meta.json.mrs[].url` or in whatever recorded that blocker; a bare `!10327` typed into `text` is a number the reader cannot make clickable, which is the whole point of the field. No URL recorded anywhere → the number in `text` and nothing else, and go and record it.
 - **Order:** (1) work title (`style: title`, no mark); (2) the MR/PR train, one entry per `meta.json.mrs[]` with `ref` `#n`, short title, real-state `mark`, `link` when there is a URL — not-started entries collapse into one `#a–#z` `pending` line; omit the block without `mrs`; (3) `Now` — what is running, the one fact `meta.json` cannot hold; (4) `Next`; (5) `Decision`, `mark: wait`, **only** when parked on the user — over the tools it travels with `attention: "wait"` (§4.2), and both are cleared together; (6) blockers, `mark: block` (a sibling repo with `contract_handoff: pending`, a red pipeline, an unmerged dependency).
 - **Rules:** `phase` is the phase you are **running now** (not `meta.json.phase`, which advances only at Close). `header: true` means ticket, type, phase and age are drawn by the reader — do not repeat them in `lines`. Keep it under ~14 lines. Every fact from `meta.json` and the artifacts — an invented MR/PR state is worse than a blank panel. Write in the language of the work's artifacts.
 
@@ -366,6 +377,13 @@ halfway is not shown as finished. When the stretch will outlast the ~30 min stal
 `stale_after_minutes` to what it will really take; (d) wherever `## Close` updates `meta.json`. A
 held panel still goes stale: the app stamps each delivery's arrival.
 
+**(e) The moment a question is answered or a gate is cleared** — before you resume the work, not at
+the next stop. Drop the `Decision` line, clear `attention`, and move `Now` on: one patch, the first
+thing you do with the answer. A panel still asking what the user already answered is worse than one
+that never asked, because they answered it and the screen says it did not land; and an `attention`
+nobody clears keeps that tab claiming them for ever. The same applies to a blocker that lifted and
+to a `wait` line whose MR/PR merged.
+
 ### 4.5 `meta.json.cost[]` — what a phase measured, when it could
 
 A phase that can measure what it spent appends one entry: `{ "phase": "review", "at": "<ISO>",

package/adapters/hermes/skills/flow-doctor/SKILL.md

@@ -199,7 +199,7 @@ refuse) · **degraded** (it runs, quietly worse than the config promises), plus
   `.agents/agents`, or a plugin. Report each missing name and that it falls back to `general-purpose`
   (a skill: skipped) — a panel missing agents reviews less and still reports a clean pass.
 - Harness cannot set a model per subagent → note that every `models.*` value degrades to inheritance.
-- **Where the live panel will go this session** (flow-core §4): `panel_set` / `panel_patch` exposed → the terminal draws the panel and no `panel.json` is written; absent → the panel is that file, as before. Neither is a fault — one line saying which one this session gets.
+- **Where the live panel will go this session** (flow-core §4): a tool whose name ends in `panel_set` / `panel_patch` — namespaced by the harness (`mcp__panel__panel_set` on Claude Code) and possibly **deferred**, which reads as absent until the list of deferred tools is checked → the terminal draws the panel and no `panel.json` is written; genuinely absent → the panel is that file, as before. Neither is a fault — one line naming the tools as they are actually called here, or saying the file is the transport.
 
 ### 2.3 Knowledge sources
 

package/adapters/hermes/skills/flow-work-README/SKILL.md

@@ -159,7 +159,7 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 
 ## The panel document
 
-`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools, or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
+`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools (namespaced by the harness, and possibly deferred: flow-core §4 says how to find them), or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
 
 ```json
 {
@@ -185,13 +185,13 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 - **`lines`** — one entry per line. Bare string = plain line; object takes `text`, `ref`, `mark`, `link`, `style`, `indent`. Empty string = blank line **and alignment block separator** (`ref` widths per block).
 - **`mark`** — `done` · `current` · `pending` · `wait` (waiting on someone else) · `block` · `info`; the reader draws it. `style` on a marked line overrides its colour — right only when the colour *is* the information.
 - **`ref`** — the column label: `#1`, `#3–#6`, `Now`, `Next`, `Decision`.
-- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable.
+- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable. Every line naming an MR/PR carries one — train entry, blocker about another MR/PR, `Now`/`Next` about the open one (flow-core §4.1).
 - **`stale_after_minutes`** — raises the 30-minute staleness threshold for a stretch known to run long.
 - **`style`** — `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`; semantic names, the reader owns the palette.
 - **`header`** — `true` (default): the reader draws ticket, type, phase and age, which never belong in `lines`. `false` hands every line to the writer.
 - **`phase`** — the phase running **right now** (`meta.json.phase` advances only at close); the reader prefers it.
 - **`updated_at`** — local ISO-8601 with offset from the real clock, never carried over; lets the reader flag a stale snapshot. Over the tools the app stamps each delivery itself.
-- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever.
+- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever — it goes, with the `Decision` line, the moment the question is answered (flow-core §4.4e).
 - **`key`** *(tools only)* — a unique, never-painted name on any line a later `panel_patch` may replace or delete (`title`, `mr-1`, `now`, `next`, `decision`, `block-1`).
 
 **No headings over the train.** A shipped MR/PR is *open, waiting to merge*; `mark` says it per entry — `wait` shipped, `current` being worked, `done` only merged.

package/adapters/hermes/skills/flow-work-resume/SKILL.md

@@ -117,7 +117,7 @@ After a break the panel is most likely stale, and a resumed session is exactly w
 
 - `phase` = the phase you are resuming into (`meta.json.phase` does not yet say it).
 - `Now` in prose; `Next` names the command §4 suggested.
-- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's.
+- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's. It goes the moment they make it (flow-core §4.4e), not at the next stop.
 - `block` lines for the blockers §4 surfaced (`contract_handoff` `pending` in a sibling repo, a red pipeline, an unmerged dependency).
 - Train: one entry per `meta.json.mrs[]`, not-started collapsed into one `#a–#z` line; omit without `mrs`.
 - `updated_at` from `date -Iseconds` when the panel goes to the file; every fact from `meta.json` and the artifacts; language of the work's artifacts.

package/adapters/opencode/CORE.md

@@ -16,7 +16,7 @@ Every `/flow-*` command assumes these rules. They are stated once, here, so a co
 carries what is specific to its phase. Read this once per session; a command that says "load
 `flow-core`" means this file.
 
-**This file belongs to flow `0.71.0`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.73.0`.** Compare it once, at the start of the session, against
 `version` in `~/.claude/flow/.claude-plugin/plugin.json`. The two differing means the session
 is running a **mixture** — the commands from one copy of the plugin, these shared rules from another
 — which is exactly what happens when a branch or a release candidate is loaded over an installed
@@ -236,7 +236,9 @@ terminal by construction, the turn is over before you notice.
   (`guided`/`auto` chaining, §2), the turn opens with the call that starts it, not with prose about
   the one that ended. **A report is never the last thing in a turn you meant to continue.**
 - **Progress belongs to the panel, not to a turn.** Someone watching reads the live panel (§4):
-  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both.
+  `Now`, `Next`. Writing it costs no turn and no stop; saying it in chat costs both. **An answered
+  question is progress too**: the `Decision` line and the panel's claim on the user go the moment
+  the answer arrives, before the work resumes (§4.4e).
 - **Stopping? Then say so.** `I need:` names the decision or the action you are waiting on. It
   never announces that you are continuing — if you were, you would not be writing this header.
 
@@ -268,8 +270,17 @@ right now. **Any progress line you were about to type into the chat is a panel u
 **Two transports, one document.** When the tools `panel_set` / `panel_patch` / `panel_get` are
 available, this console is a pane of agent-terminal: publish the panel through them (§4.2) and
 **stop writing `.claude/work/<work>/panel.json`** — while a pane is claimed, its file is not read at
-all. When the tools are not there, write the file exactly as before (§4.3). No work folder
-(lightweight `respond`/`green`) → nothing to publish, either way.
+all. When they are not there, write the file exactly as before (§4.3). No work folder (lightweight
+`respond`/`green`) → nothing to publish, either way.
+
+**Look for them before you conclude they are missing**, once per session, in pre-flight. A harness
+namespaces an MCP server's tools, so what you are looking for is a tool whose name *ends* in
+`panel_set` — `mcp__panel__panel_set` on Claude Code, another prefix elsewhere — and the name is
+whatever it is called there, not `panel_set`. It may also be **deferred**: listed by name with no
+schema, uncallable until you load it, and indistinguishable from absent unless you read that list.
+A deferred tool is a tool that is there; load the three schemas and publish. The file is the answer
+only after that search comes back empty — and this is the one paragraph that decides it, because
+prose describing a file is otherwise obeyed to the letter.
 
 ### 4.1 The document — the same whichever transport carries it
 
@@ -296,7 +307,7 @@ all. When the tools are not there, write the file exactly as before (§4.3). No
 
 - **`mark` says what a line is**; the reader draws it. `done` · `current` (at most one) · `pending` · `wait` (waiting on someone else: an open MR/PR, a user decision) · `block` · `info`. Marked lines form an aligned column: symbol, `ref`, text, link pinned right. Do not set `style` on a marked line — except `mark: "info"` + `style: ok|warn|error` when the colour *is* the information (a monitoring verdict).
 - **`ref` need not be a number**: `#1`, `#3–#6`, `Now`, `Next`, `Decision`. Column width is per block; blocks are separated by blank lines — use them so the MR/PR train and the labels below do not drag each other wide.
-- **`link` is a field, never a URL inside `text`.**
+- **`link` is a field, never a URL inside `text`** — and **every line that names an MR/PR carries it**: the train entries, a blocker about somebody else's MR/PR, a `Now` or `Next` about the open one. The URL is in `meta.json.mrs[].url` or in whatever recorded that blocker; a bare `!10327` typed into `text` is a number the reader cannot make clickable, which is the whole point of the field. No URL recorded anywhere → the number in `text` and nothing else, and go and record it.
 - **Order:** (1) work title (`style: title`, no mark); (2) the MR/PR train, one entry per `meta.json.mrs[]` with `ref` `#n`, short title, real-state `mark`, `link` when there is a URL — not-started entries collapse into one `#a–#z` `pending` line; omit the block without `mrs`; (3) `Now` — what is running, the one fact `meta.json` cannot hold; (4) `Next`; (5) `Decision`, `mark: wait`, **only** when parked on the user — over the tools it travels with `attention: "wait"` (§4.2), and both are cleared together; (6) blockers, `mark: block` (a sibling repo with `contract_handoff: pending`, a red pipeline, an unmerged dependency).
 - **Rules:** `phase` is the phase you are **running now** (not `meta.json.phase`, which advances only at Close). `header: true` means ticket, type, phase and age are drawn by the reader — do not repeat them in `lines`. Keep it under ~14 lines. Every fact from `meta.json` and the artifacts — an invented MR/PR state is worse than a blank panel. Write in the language of the work's artifacts.
 
@@ -365,6 +376,13 @@ halfway is not shown as finished. When the stretch will outlast the ~30 min stal
 `stale_after_minutes` to what it will really take; (d) wherever `## Close` updates `meta.json`. A
 held panel still goes stale: the app stamps each delivery's arrival.
 
+**(e) The moment a question is answered or a gate is cleared** — before you resume the work, not at
+the next stop. Drop the `Decision` line, clear `attention`, and move `Now` on: one patch, the first
+thing you do with the answer. A panel still asking what the user already answered is worse than one
+that never asked, because they answered it and the screen says it did not land; and an `attention`
+nobody clears keeps that tab claiming them for ever. The same applies to a blocker that lifted and
+to a `wait` line whose MR/PR merged.
+
 ### 4.5 `meta.json.cost[]` — what a phase measured, when it could
 
 A phase that can measure what it spent appends one entry: `{ "phase": "review", "at": "<ISO>",

package/adapters/opencode/commands/flow-doctor.md

@@ -197,7 +197,7 @@ refuse) · **degraded** (it runs, quietly worse than the config promises), plus
   `.agents/agents`, or a plugin. Report each missing name and that it falls back to `general-purpose`
   (a skill: skipped) — a panel missing agents reviews less and still reports a clean pass.
 - Harness cannot set a model per subagent → note that every `models.*` value degrades to inheritance.
-- **Where the live panel will go this session** (flow-core §4): `panel_set` / `panel_patch` exposed → the terminal draws the panel and no `panel.json` is written; absent → the panel is that file, as before. Neither is a fault — one line saying which one this session gets.
+- **Where the live panel will go this session** (flow-core §4): a tool whose name ends in `panel_set` / `panel_patch` — namespaced by the harness (`mcp__panel__panel_set` on Claude Code) and possibly **deferred**, which reads as absent until the list of deferred tools is checked → the terminal draws the panel and no `panel.json` is written; genuinely absent → the panel is that file, as before. Neither is a fault — one line naming the tools as they are actually called here, or saying the file is the transport.
 
 ### 2.3 Knowledge sources
 

package/adapters/opencode/commands/flow-work-README.md

@@ -157,7 +157,7 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 
 ## The panel document
 
-`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools, or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
+`meta.json` is the *state machine*; the panel is the *view* a reader outside the chat watches. Optional: a work that never publishes it still resolves from `meta.json` alone. Writer rules (order, when, ceiling) and the two transports — the terminal's `panel_set` / `panel_patch` / `panel_get` tools (namespaced by the harness, and possibly deferred: flow-core §4 says how to find them), or `.claude/work/<work>/panel.json` — are flow-core §4. The document below is the same either way.
 
 ```json
 {
@@ -183,13 +183,13 @@ This system **orchestrates** the project's existing sub-agents and skills (it do
 - **`lines`** — one entry per line. Bare string = plain line; object takes `text`, `ref`, `mark`, `link`, `style`, `indent`. Empty string = blank line **and alignment block separator** (`ref` widths per block).
 - **`mark`** — `done` · `current` · `pending` · `wait` (waiting on someone else) · `block` · `info`; the reader draws it. `style` on a marked line overrides its colour — right only when the colour *is* the information.
 - **`ref`** — the column label: `#1`, `#3–#6`, `Now`, `Next`, `Decision`.
-- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable.
+- **`link`** — URL as a **field, never pasted into `text`**; the reader shortens it to the MR/PR number and makes it clickable. Every line naming an MR/PR carries one — train entry, blocker about another MR/PR, `Now`/`Next` about the open one (flow-core §4.1).
 - **`stale_after_minutes`** — raises the 30-minute staleness threshold for a stretch known to run long.
 - **`style`** — `normal` · `dim` · `title` · `accent` · `ok` · `warn` · `error`; semantic names, the reader owns the palette.
 - **`header`** — `true` (default): the reader draws ticket, type, phase and age, which never belong in `lines`. `false` hands every line to the writer.
 - **`phase`** — the phase running **right now** (`meta.json.phase` advances only at close); the reader prefers it.
 - **`updated_at`** — local ISO-8601 with offset from the real clock, never carried over; lets the reader flag a stale snapshot. Over the tools the app stamps each delivery itself.
-- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever.
+- **`attention`** *(tools only)* — `wait` · `block` · `done`, beside `phase`, absent while simply working: the pane's claim on the user's attention, which the app never deduces from a line's `mark`. A tab's card shows the strongest claim among its panes, so an uncleared `wait` flags that tab for ever — it goes, with the `Decision` line, the moment the question is answered (flow-core §4.4e).
 - **`key`** *(tools only)* — a unique, never-painted name on any line a later `panel_patch` may replace or delete (`title`, `mr-1`, `now`, `next`, `decision`, `block-1`).
 
 **No headings over the train.** A shipped MR/PR is *open, waiting to merge*; `mark` says it per entry — `wait` shipped, `current` being worked, `done` only merged.

package/adapters/opencode/commands/flow-work-resume.md

@@ -115,7 +115,7 @@ After a break the panel is most likely stale, and a resumed session is exactly w
 
 - `phase` = the phase you are resuming into (`meta.json.phase` does not yet say it).
 - `Now` in prose; `Next` names the command §4 suggested.
-- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's.
+- `Decision` marked `wait` is always set after a resume — nothing is running, the next move is the user's. It goes the moment they make it (flow-core §4.4e), not at the next stop.
 - `block` lines for the blockers §4 surfaced (`contract_handoff` `pending` in a sibling repo, a red pipeline, an unmerged dependency).
 - Train: one entry per `meta.json.mrs[]`, not-started collapsed into one `#a–#z` line; omit without `mrs`.
 - `updated_at` from `date -Iseconds` when the panel goes to the file; every fact from `meta.json` and the artifacts; language of the work's artifacts.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flow-workflows",
-  "version": "0.71.0",
+  "version": "0.73.0",
   "description": "Guided feat/bug workflows (start→ship), post-deploy monitoring and multi-agent code review, stack-agnostic. Each repo uses a shared FLOW.md plus optional harness overlay.",
   "type": "module",
   "bin": {

package/plugins/flow/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "flow",
   "displayName": "Flow — guided dev workflows",
   "description": "Guided feat/bug workflows (start→ship), post-deploy monitoring and multi-agent code review, stack-agnostic. Each repo uses a shared FLOW.md plus optional harness overlay.",
-  "version": "0.71.0",
+  "version": "0.73.0",
   "author": {
     "name": "Alberto Vioque",
     "email": "mashware@gmail.com"

package/plugins/flow/CHANGELOG.md

@@ -5,6 +5,40 @@ plugin and is what `/flow:news` reads to show you what changed since your previo
 
 The canonical, richest notes live in the [GitHub Releases](https://github.com/mashware/flow-workflows/releases).
 
+## v0.73.0 — The panel kept asking what you had already answered  ·  2026-09-22
+
+**In short**
+- **An answered question now clears the panel at once.** The `Decision` line and the pane's claim on your attention go the moment the answer arrives — before the work resumes, not at the next stop.
+- **Same for a blocker that lifted** and for a `wait` line whose MR/PR merged: the panel said "waiting for you" long after nothing was.
+- **Every line that names an MR/PR carries its link** — the train, a blocker about somebody else's MR/PR, a `Now` about the open one — so the reader can paint `!10327` as something you can click. A number typed into the text is a number the reader cannot use.
+
+A panel that still asks what you answered five minutes ago is worse than one that never asked: you
+answered, and the screen says it did not land. The rule that produced it was honest — publish before
+a stop, before a long stretch, at every close — and an answer is none of those three: it arrives
+mid-turn, between two pieces of work, and the next publication was whenever the phase happened to
+end. So the claim on the user outlived the question by an entire phase, and a tab whose card shows
+the strongest claim among its panes kept flagging itself.
+
+The link rule is the same failure in the other direction. `!10327` written into a line's text reads
+correctly and does nothing; the field exists so the reader can shorten a URL and make it clickable,
+and flow knows the URL — it is in `meta.json`. Where nothing recorded one, the number stays plain
+text and the fix is to record it.
+
+## v0.72.0 — The tools were there, under a name nobody looked for  ·  2026-09-22
+
+**In short**
+- **A session with the panel tools connected kept writing the file.** The rule named them `panel_set` / `panel_patch`, and a harness namespaces an MCP server's tools — so the agent looked for a name that exists nowhere and concluded, reasonably, that there was no panel.
+- **Now the search is the rule**: once per session, in pre-flight, look for a tool whose name *ends* in `panel_set` — `mcp__panel__panel_set` on Claude Code, another prefix elsewhere.
+- **A deferred tool is a tool that is there.** Listed by name with no schema, it reads as absent to anything that does not check that list; flow loads the three schemas and publishes.
+- **The file is the answer only after that search comes back empty**, and `/flow:doctor` names the tools as they are actually called here.
+
+v0.71.0 gave the panel a second transport and described it with the names the server declares.
+Neither the plugin nor the agent reading it ever sees those: a harness prefixes them, and it may
+hand them over as names alone, uncallable until their schemas are loaded. Both together are
+indistinguishable from an absent server — and the fallback, "write the file exactly as before", is
+the most obeyed sentence in the section. So the transport chosen itself was the file, every time,
+on the one terminal that had the panel.
+
 ## v0.71.0 — The panel was a file because nothing better was listening  ·  2026-09-22
 
 **In short**