flow-workflows 0.76.0 → 0.78.0

package/plugins/flow/CHANGELOG.md

@@ -5,6 +5,42 @@ 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.78.0 — The specialist was installed; the flow asked for a generalist  ·  2026-09-23
+
+**In short**
+- **An empty agent role now goes to the installed agent that fits it.** The harness already lists
+  your agents with what each is for; a role you left blank picks from that list, by role and by
+  stack, and falls back to `general-purpose` only when nothing fits clearly.
+- **`agents.selection: open` lets the model pick past the roles you named** — a better-fitting
+  installed agent for a piece, or a specialist for a piece no role covers — recording each
+  substitution in the phase artifact. Empty keeps your roles as orders.
+- **With `open`, a missing specialist is created for the work** — an expert brief written for this
+  stack and this piece, run on the general-purpose agent — and **offered for saving as a real agent
+  when `ship` closes**, after the MR/PR and the knowledge save, only if it contributed something.
+- **Flow stops offering to fill agent roles mid-phase**: they are optional overrides now, not gaps.
+- **`build` may delegate on small works too**, when a specialist would clearly do a piece better,
+  instead of only consulting one when blocked.
+
+Left alone, a current model reads the agent list and hands a React component to the React expert.
+Inside a flow command it could not: every empty role said `general-purpose`, so the command's text
+overrode the judgement the harness was set up to use. The review roster is untouched — it runs as
+defined in both modes — and the challengers and blinded checks stay generalists on purpose.
+
+## v0.77.0 — The steps of the MR/PR you are on are on the panel  ·  2026-09-22
+
+**In short**
+- **The live panel shows the plan steps of the MR/PR being built**, indented under its entry in the
+  train: finished, current and pending, updated as each one lands — on every harness that feeds the
+  panel, not only on the one that has a task list.
+- **A harness task list becomes an extra.** `build` and `fix` still seed it where it exists, but
+  nothing depends on it, and `/flow:doctor` reports it as information rather than a warning.
+
+v0.76.0 made the step list findable on Claude Code, where it only exists behind
+`CLAUDE_CODE_ENABLE_TODO_TOOLS` and costs context in every session. The panel already had the words
+for it (`done` · `current` · `pending`) and is fed the same way from Codex, OpenCode or zcode. The
+ticks in the phase artifact stay the record; the panel and any task list follow them. Steps past three
+on either side collapse into one line, so the block never takes more than five.
+
 ## v0.76.0 — The plan was written for a list the terminal was never given  ·  2026-09-22
 
 **In short**

package/plugins/flow/examples/FLOW.template.md

@@ -170,8 +170,16 @@ scripts, Gradle, dotnet, Xcode, Flutter, pyproject, Cargo, go.mod) and reports w
 Role→agent map for steps that delegate to a specialist (`design`, `investigate`,
 `validate`, `plan`, `build`, `fix`, `watch`, and the area reinforcements in `review`). Agents
 must exist and be discoverable on the machine (`~/.claude/agents`, `.agents/agents` in the repo, or
-another plugin) — this only states **which** one to invoke, it does not create it. **Empty role = the command uses
-`Agent general-purpose` with the role in the prompt, or skips the step if it was optional.**
+another plugin) — this only states **which** one to invoke, it does not create it. **Empty role = the command picks
+the installed agent that fits the role and the stack, else `Agent general-purpose` with the role in the prompt, or skips
+the step if it was optional** (flow-core §6.6).
+
+- `selection:`      # your roles as orders or as defaults. Empty = `configured` (named roles used as is); `open` = the model may pick past them
+                    #   Empty roles are picked from the installed agents either way. `open` = a named role is a default: the model
+                    #   may use an installed agent that fits a piece plainly better, or a specialist for a piece no role
+                    #   covers, and records each substitution. Nothing installed fits → it writes an expert brief and runs it
+                    #   on the general-purpose agent; a useful one is offered for saving as an agent when `ship` closes.
+                    #   Never touches `quality.reviewers`/`review_skill`
 
 - `architecture:`   # design/layers/architecture
 - `persistence:`    # DB/ORM/mappings/migrations/queries