flow-workflows 0.65.0-rc.3 → 0.65.0-rc.4

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.65.0-rc.3`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.4`.** 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
@@ -27,6 +27,16 @@ a command relies on is simply absent in that session, and nothing else will repo
 
 ## 0. Effective FLOW config — base plus harness overlay
 
+- **Look before you read.** The first thing a phase does about configuration is list what is there:
+  `ls <root>/FLOW*.md` (the root being the one the next bullet resolves). One call, and it is not
+  optional — **an overlay you did not list is an overlay you did not read**, and nothing downstream
+  will notice. This is not a hypothetical: every command below, and every artifact they write,
+  refers to the effective configuration as "`FLOW.md`", which is a file that exists, so reading it
+  and stopping feels finished. Two real sessions in a row read the base in full and never went
+  looking for the overlay sitting beside it — the models it set were silently the defaults, and
+  both runs reported the keys as unset with no way to tell that apart from a repo that never set
+  them. **Name the files this listing found the first time a phase reports any configured value**,
+  so a missed overlay is visible in the artifact rather than invisible everywhere.
 - Read `FLOW.md` at the repo root as the base, then the optional overlay for the harness running
   this command: `FLOW.claude.md`, `FLOW.codex.md`, `FLOW.opencode.md`, `FLOW.gemini.md`, or
   `FLOW.hermes.md`. The
@@ -50,7 +60,8 @@ a command relies on is simply absent in that session, and nothing else will repo
   to the normal empty-key fallback — this is how Codex can inherit its session model while a legacy
   `FLOW.md` still names a Claude model. A list-valued key is replaced as a whole, never appended.
   `conventions` is the one unkeyed section: its overlay lines are added after the base lines, so
-  both sets apply. Keep the source file of every effective value; `doctor` reports it and later
+  both sets apply. **Every value carries the file it came from**, and a phase that prints a value
+  prints that file with it — "`agents: opus` (`FLOW.claude.md`)", never the value alone. `doctor` reports it and later
   edits preserve it.
 - The sections in either file are tracker, git, autonomy, quality, agents, models, data,
   conventions, notes, knowledge, and observability. Both files missing, or an effective empty key

package/adapters/codex/skills/flow-bug-review/SKILL.md

@@ -162,7 +162,7 @@ Cost line: count every subagent this command launched — reviewers = §2.1 buil
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `$flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which the tier used, and — when the diff landed within 10% under a tier threshold — that fact (§2.0)>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread"; agents named in `agents.<role>` keep their own definition's model>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed; agents named in `agents.<role>` keep their own definition's model>
 - Defaults used: <every empty `FLOW.md` key this round resolved with its default — one per line as `key → default` — or "none". In `guided`/`auto` each is also an entry in `meta.json.defaults_used[]` (flow-core §0); in `manual` the phase may offer one of them at its stop.>
 - Skipped for budget: <phases dropped by §2.0's give-up order, or "none">
 - Blockers: N

package/adapters/codex/skills/flow-feat-review/SKILL.md

@@ -310,7 +310,7 @@ Write `.claude/work/<TICKET>/06-review.md`. The `Cost:` line of `## Summary` is
 - Review tier: <full | proportional | light — which reviewers ran, at what built-in effort (medium/high/xhigh/max), and why, per §2.0>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which of the two the tier used, and — when the diff pointed higher — that the work may be misclassified. When the diff landed within 10% under a tier threshold, say so here (§2.0).>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread" — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed — "unset" without them reads the same whether the overlay was empty or never opened — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
 - Cost: <n>/<budget_max> subagents launched (<k> reviewers · <m> reinforcements · <s> skeptics), tier <light|proportional|full>, effort <medium|high|xhigh|max>
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `$flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Agents launched: <ran vs defined — `N/M` of the `review_skill`/`reviewers` roster, naming any that did not run (with the reason) and any substitution; "built-in only" if §2.0 selected no panel>

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.65.0-rc.3`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.4`.** 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
@@ -26,6 +26,16 @@ a command relies on is simply absent in that session, and nothing else will repo
 
 ## 0. Effective FLOW config — base plus harness overlay
 
+- **Look before you read.** The first thing a phase does about configuration is list what is there:
+  `ls <root>/FLOW*.md` (the root being the one the next bullet resolves). One call, and it is not
+  optional — **an overlay you did not list is an overlay you did not read**, and nothing downstream
+  will notice. This is not a hypothetical: every command below, and every artifact they write,
+  refers to the effective configuration as "`FLOW.md`", which is a file that exists, so reading it
+  and stopping feels finished. Two real sessions in a row read the base in full and never went
+  looking for the overlay sitting beside it — the models it set were silently the defaults, and
+  both runs reported the keys as unset with no way to tell that apart from a repo that never set
+  them. **Name the files this listing found the first time a phase reports any configured value**,
+  so a missed overlay is visible in the artifact rather than invisible everywhere.
 - Read `FLOW.md` at the repo root as the base, then the optional overlay for the harness running
   this command: `FLOW.claude.md`, `FLOW.codex.md`, `FLOW.opencode.md`, `FLOW.gemini.md`, or
   `FLOW.hermes.md`. The
@@ -49,7 +59,8 @@ a command relies on is simply absent in that session, and nothing else will repo
   to the normal empty-key fallback — this is how Codex can inherit its session model while a legacy
   `FLOW.md` still names a Claude model. A list-valued key is replaced as a whole, never appended.
   `conventions` is the one unkeyed section: its overlay lines are added after the base lines, so
-  both sets apply. Keep the source file of every effective value; `doctor` reports it and later
+  both sets apply. **Every value carries the file it came from**, and a phase that prints a value
+  prints that file with it — "`agents: opus` (`FLOW.claude.md`)", never the value alone. `doctor` reports it and later
   edits preserve it.
 - The sections in either file are tracker, git, autonomy, quality, agents, models, data,
   conventions, notes, knowledge, and observability. Both files missing, or an effective empty key

package/adapters/gemini/commands/flow/bug/review.toml

@@ -158,7 +158,7 @@ Cost line: count every subagent this command launched — reviewers = §2.1 buil
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow:work:status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which the tier used, and — when the diff landed within 10% under a tier threshold — that fact (§2.0)>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread"; agents named in `agents.<role>` keep their own definition's model>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed; agents named in `agents.<role>` keep their own definition's model>
 - Defaults used: <every empty `FLOW.md` key this round resolved with its default — one per line as `key → default` — or "none". In `guided`/`auto` each is also an entry in `meta.json.defaults_used[]` (flow-core §0); in `manual` the phase may offer one of them at its stop.>
 - Skipped for budget: <phases dropped by §2.0's give-up order, or "none">
 - Blockers: N

package/adapters/gemini/commands/flow/feat/review.toml

@@ -306,7 +306,7 @@ Write `.claude/work/<TICKET>/06-review.md`. The `Cost:` line of `## Summary` is
 - Review tier: <full | proportional | light — which reviewers ran, at what built-in effort (medium/high/xhigh/max), and why, per §2.0>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which of the two the tier used, and — when the diff pointed higher — that the work may be misclassified. When the diff landed within 10% under a tier threshold, say so here (§2.0).>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread" — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed — "unset" without them reads the same whether the overlay was empty or never opened — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
 - Cost: <n>/<budget_max> subagents launched (<k> reviewers · <m> reinforcements · <s> skeptics), tier <light|proportional|full>, effort <medium|high|xhigh|max>
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow:work:status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Agents launched: <ran vs defined — `N/M` of the `review_skill`/`reviewers` roster, naming any that did not run (with the reason) and any substitution; "built-in only" if §2.0 selected no panel>

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.65.0-rc.3`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.4`.** 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
@@ -27,6 +27,16 @@ a command relies on is simply absent in that session, and nothing else will repo
 
 ## 0. Effective FLOW config — base plus harness overlay
 
+- **Look before you read.** The first thing a phase does about configuration is list what is there:
+  `ls <root>/FLOW*.md` (the root being the one the next bullet resolves). One call, and it is not
+  optional — **an overlay you did not list is an overlay you did not read**, and nothing downstream
+  will notice. This is not a hypothetical: every command below, and every artifact they write,
+  refers to the effective configuration as "`FLOW.md`", which is a file that exists, so reading it
+  and stopping feels finished. Two real sessions in a row read the base in full and never went
+  looking for the overlay sitting beside it — the models it set were silently the defaults, and
+  both runs reported the keys as unset with no way to tell that apart from a repo that never set
+  them. **Name the files this listing found the first time a phase reports any configured value**,
+  so a missed overlay is visible in the artifact rather than invisible everywhere.
 - Read `FLOW.md` at the repo root as the base, then the optional overlay for the harness running
   this command: `FLOW.claude.md`, `FLOW.codex.md`, `FLOW.opencode.md`, `FLOW.gemini.md`, or
   `FLOW.hermes.md`. The
@@ -50,7 +60,8 @@ a command relies on is simply absent in that session, and nothing else will repo
   to the normal empty-key fallback — this is how Codex can inherit its session model while a legacy
   `FLOW.md` still names a Claude model. A list-valued key is replaced as a whole, never appended.
   `conventions` is the one unkeyed section: its overlay lines are added after the base lines, so
-  both sets apply. Keep the source file of every effective value; `doctor` reports it and later
+  both sets apply. **Every value carries the file it came from**, and a phase that prints a value
+  prints that file with it — "`agents: opus` (`FLOW.claude.md`)", never the value alone. `doctor` reports it and later
   edits preserve it.
 - The sections in either file are tracker, git, autonomy, quality, agents, models, data,
   conventions, notes, knowledge, and observability. Both files missing, or an effective empty key

package/adapters/hermes/skills/flow-bug-review/SKILL.md

@@ -162,7 +162,7 @@ Cost line: count every subagent this command launched — reviewers = §2.1 buil
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which the tier used, and — when the diff landed within 10% under a tier threshold — that fact (§2.0)>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread"; agents named in `agents.<role>` keep their own definition's model>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed; agents named in `agents.<role>` keep their own definition's model>
 - Defaults used: <every empty `FLOW.md` key this round resolved with its default — one per line as `key → default` — or "none". In `guided`/`auto` each is also an entry in `meta.json.defaults_used[]` (flow-core §0); in `manual` the phase may offer one of them at its stop.>
 - Skipped for budget: <phases dropped by §2.0's give-up order, or "none">
 - Blockers: N

package/adapters/hermes/skills/flow-feat-review/SKILL.md

@@ -310,7 +310,7 @@ Write `.claude/work/<TICKET>/06-review.md`. The `Cost:` line of `## Summary` is
 - Review tier: <full | proportional | light — which reviewers ran, at what built-in effort (medium/high/xhigh/max), and why, per §2.0>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which of the two the tier used, and — when the diff pointed higher — that the work may be misclassified. When the diff landed within 10% under a tier threshold, say so here (§2.0).>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread" — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed — "unset" without them reads the same whether the overlay was empty or never opened — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
 - Cost: <n>/<budget_max> subagents launched (<k> reviewers · <m> reinforcements · <s> skeptics), tier <light|proportional|full>, effort <medium|high|xhigh|max>
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Agents launched: <ran vs defined — `N/M` of the `review_skill`/`reviewers` roster, naming any that did not run (with the reason) and any substitution; "built-in only" if §2.0 selected no panel>

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.65.0-rc.3`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.4`.** 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
@@ -26,6 +26,16 @@ a command relies on is simply absent in that session, and nothing else will repo
 
 ## 0. Effective FLOW config — base plus harness overlay
 
+- **Look before you read.** The first thing a phase does about configuration is list what is there:
+  `ls <root>/FLOW*.md` (the root being the one the next bullet resolves). One call, and it is not
+  optional — **an overlay you did not list is an overlay you did not read**, and nothing downstream
+  will notice. This is not a hypothetical: every command below, and every artifact they write,
+  refers to the effective configuration as "`FLOW.md`", which is a file that exists, so reading it
+  and stopping feels finished. Two real sessions in a row read the base in full and never went
+  looking for the overlay sitting beside it — the models it set were silently the defaults, and
+  both runs reported the keys as unset with no way to tell that apart from a repo that never set
+  them. **Name the files this listing found the first time a phase reports any configured value**,
+  so a missed overlay is visible in the artifact rather than invisible everywhere.
 - Read `FLOW.md` at the repo root as the base, then the optional overlay for the harness running
   this command: `FLOW.claude.md`, `FLOW.codex.md`, `FLOW.opencode.md`, `FLOW.gemini.md`, or
   `FLOW.hermes.md`. The
@@ -49,7 +59,8 @@ a command relies on is simply absent in that session, and nothing else will repo
   to the normal empty-key fallback — this is how Codex can inherit its session model while a legacy
   `FLOW.md` still names a Claude model. A list-valued key is replaced as a whole, never appended.
   `conventions` is the one unkeyed section: its overlay lines are added after the base lines, so
-  both sets apply. Keep the source file of every effective value; `doctor` reports it and later
+  both sets apply. **Every value carries the file it came from**, and a phase that prints a value
+  prints that file with it — "`agents: opus` (`FLOW.claude.md`)", never the value alone. `doctor` reports it and later
   edits preserve it.
 - The sections in either file are tracker, git, autonomy, quality, agents, models, data,
   conventions, notes, knowledge, and observability. Both files missing, or an effective empty key

package/adapters/opencode/commands/flow-bug-review.md

@@ -160,7 +160,7 @@ Cost line: count every subagent this command launched — reviewers = §2.1 buil
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which the tier used, and — when the diff landed within 10% under a tier threshold — that fact (§2.0)>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread"; agents named in `agents.<role>` keep their own definition's model>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed; agents named in `agents.<role>` keep their own definition's model>
 - Defaults used: <every empty `FLOW.md` key this round resolved with its default — one per line as `key → default` — or "none". In `guided`/`auto` each is also an entry in `meta.json.defaults_used[]` (flow-core §0); in `manual` the phase may offer one of them at its stop.>
 - Skipped for budget: <phases dropped by §2.0's give-up order, or "none">
 - Blockers: N

package/adapters/opencode/commands/flow-feat-review.md

@@ -308,7 +308,7 @@ Write `.claude/work/<TICKET>/06-review.md`. The `Cost:` line of `## Summary` is
 - Review tier: <full | proportional | light — which reviewers ran, at what built-in effort (medium/high/xhigh/max), and why, per §2.0>
 - Effective size: <diff size (N changed lines) vs `meta.json.size`, which of the two the tier used, and — when the diff pointed higher — that the work may be misclassified. When the diff landed within 10% under a tier threshold, say so here (§2.0).>
 - Review path: <the two paths this round actually took: `flow bundle` or git for the material, `flow review` or the agentic panel for the reviewers — each with the reason when it was the fallback (no CLI, non-zero exit, `agents.exec_cmd` empty, every role empty). Without this line a round that skipped the CLI reads exactly like one that used it.>
-- Agent models: <the value of `models.workers`/`models.agents` when set; otherwise "inherited from this thread" — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
+- Agent models: <the value of `models.workers`/`models.agents` **with the file each came from** (flow-core §0) when set; otherwise "inherited from this thread", naming the config files you listed — "unset" without them reads the same whether the overlay was empty or never opened — plus, when the panel ran, that agents named in `agents.<role>` kept the model their own definition sets. The values as they are, no judgement on them>
 - Cost: <n>/<budget_max> subagents launched (<k> reviewers · <m> reinforcements · <s> skeptics), tier <light|proportional|full>, effort <medium|high|xhigh|max>
 - Measured cost: <what the harness reported for this round, when it reported anything — `flow review --record` writes it to `meta.json.cost[]` and `/flow-work-status` and `flow cost` read it back. A harness that reports no figure is recorded as "not reported": the subagent count above is a headcount, not a cost, and a guess is worse than a gap.>
 - Agents launched: <ran vs defined — `N/M` of the `review_skill`/`reviewers` roster, naming any that did not run (with the reason) and any substitution; "built-in only" if §2.0 selected no panel>

package/bin/cli.mjs

@@ -271,6 +271,17 @@ function configRoot(repo) {
   return main !== repo && existsSync(join(main, 'FLOW.md')) ? main : repo
 }
 
+// Which config files a run actually read. The pack says so out loud because the failure it
+// makes visible is silent by nature: a phase that read the base and never looked for the
+// overlay reports every key it set as unset, which is what a repo with no overlay reports too.
+function configFiles(repo, harness) {
+  const root = configRoot(repo)
+  const names = ['FLOW.md', harness && `FLOW.${harness}.md`].filter(Boolean)
+  const found = names.filter((n) => existsSync(join(root, n)))
+  const where = root === repo ? '' : ` (from ${root})`
+  return found.length ? found.join(' + ') + where : `none found${where || ` in ${repo}`}`
+}
+
 // Base file plus the overlay of the harness running this, exactly as flow-core §0 resolves
 // it: a key present in the overlay replaces the base value.
 function flowConfig(repo, harness) {
@@ -387,6 +398,7 @@ function buildBundle(argv) {
   out.push(`# flow bundle — ${branch}`)
   out.push('')
   out.push(`Base \`${base}\` · merge base \`${from.slice(0, 12)}\` · generated by \`flow bundle\`.`)
+  out.push(`Config read: ${configFiles(repo, flag('--harness'))}.`)
   out.push('Committed and uncommitted changes together. Nothing here is parsed or summarised.')
   out.push('')
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flow-workflows",
-  "version": "0.65.0-rc.3",
+  "version": "0.65.0-rc.4",
   "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.65.0-rc.3",
+  "version": "0.65.0-rc.4",
   "author": {
     "name": "Alberto Vioque",
     "email": "mashware@gmail.com"

package/plugins/flow/CHANGELOG.md

@@ -88,7 +88,19 @@ to the main checkout, which `--git-common-dir` locates from anywhere. And **a qu
 quotes**, so the `- '*.lock'` the template itself documents became a pathspec matching a filename
 with quotes in it — `git.diff_exclude` excluded nothing for anyone who copied the example.
 
-None of the three could be seen from the repo, and none of them failed. That is the argument for
+The third candidate then found the one that had been hiding behind them. A harness overlay —
+`FLOW.claude.md` and its siblings, where a model id belongs so it never reaches another harness —
+**was never read**. Not once, in two full runs, on two different models: both read the base file in
+full and neither went looking for the overlay beside it, so the models it set were silently the
+defaults and both artifacts reported the keys as *unset* — which is exactly what a repo that never
+set them reports. The instruction to merge an overlay has always been there; what was missing was
+anything that made a phase **look**. Every command, and every artifact they write, calls the
+effective configuration "`FLOW.md`", and that is a real file, so reading it and stopping feels
+finished. Step 0 now begins by listing `FLOW*.md` — one call, not optional — every printed value
+carries the file it came from, and `bundle` states in its header which files the run read, so an
+overlay that was never opened is a line in the pack instead of nothing at all.
+
+None of the four could be seen from the repo, and none of them failed. That is the argument for
 driving a candidate through a real work rather than reading it: the run that found them is also the
 one whose review then read the diff from git and caught five blocking defects anyway, because the
 fallback is a real path and not an apology.