flow-workflows 0.65.0-rc.6 → 0.65.0-rc.7

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.6`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.7`.** 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

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.6`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.7`.** 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

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.6`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.7`.** 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

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.6`.** Compare it once, at the start of the session, against
+**This file belongs to flow `0.65.0-rc.7`.** 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

package/bin/cli.mjs

@@ -263,14 +263,16 @@ function parseFlow(text) {
 // resolve every key to its fallback and say nothing. Prefer the root we are in (a repo that
 // commits its config gets it in every worktree, and a worktree may legitimately differ), and
 // fall back to the main checkout, which `--git-common-dir` points into from anywhere.
-function configRoot(repo) {
-  if (existsSync(join(repo, 'FLOW.md'))) return repo
+function rootHolding(repo, probe) {
+  if (existsSync(join(repo, probe))) return repo
   const common = git(['rev-parse', '--path-format=absolute', '--git-common-dir'], repo).trim()
   if (!common) return repo
   const main = dirname(common)
-  return main !== repo && existsSync(join(main, 'FLOW.md')) ? main : repo
+  return main !== repo && existsSync(join(main, probe)) ? main : repo
 }
 
+const configRoot = (repo) => rootHolding(repo, 'FLOW.md')
+
 // The overlay names flow-core §0 recognises. A `--harness` outside this set reads no
 // overlay and looks exactly like a repo that has none, so it stops the run instead: a typo
 // here is worth one error message and never worth a review round nobody can trust.
@@ -322,8 +324,12 @@ function flowConfig(repo, harness) {
   return base
 }
 
+// `.claude/work` is git-ignored like the FLOW files, so a worktree does not carry it either — and
+// the two things that read it fail silently when it is missing: the pack drops its `## Work`
+// section, which it advertises and no reviewer knows to miss, and `--record` writes the figure
+// nowhere and exits 0. Same resolution as the config: here first, the main checkout otherwise.
 function workFolder(repo, branch) {
-  const root = join(repo, '.claude', 'work')
+  const root = join(rootHolding(repo, join('.claude', 'work')), '.claude', 'work')
   if (!existsSync(root)) return null
   for (const entry of readdirSync(root, { withFileTypes: true })) {
     if (!entry.isDirectory() || entry.name === '_archive') continue

package/package.json

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

package/plugins/flow/CHANGELOG.md

@@ -123,7 +123,21 @@ and re-opening its file would pay for the same words twice; the folder is where
 call separates a round that was lost from a round that was never done, and only the second is worth
 another agent.
 
-None of the six could be seen from the repo, and none of them failed. That is the argument for
+The first real run of the CLI panel — the half of this release nothing had exercised — found the
+last one, and it is the worktree bug again in the place nobody looked. **`.claude/work` is
+git-ignored exactly like the FLOW files**, so a phase running in a worktree does not have it
+either: `bundle` silently dropped the `## Work` section it advertises, sending every reviewer a
+pack with no handoff and no `meta.json`, and `review --record` wrote the figure nowhere and exited
+0 — which is indistinguishable from a harness that reported no cost. The work folder now resolves
+the way the config does: here first, the main checkout otherwise.
+
+That same run is the argument for the whole release. Four one-shot reviewers, four and a half
+minutes, **$4.24 measured** over a 1 360-line diff, and they found a major regression the agentic
+panel had missed on the same branch: `Option<&RawValue>` collapses a JSON `null` into "key absent",
+so a reply that carried an explicit null lost the distinction the code around it documents. Not
+found by reading the plugin — found by running it.
+
+None of the seven 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.