flow-workflows 0.83.1 → 0.85.0

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.83.1",
+  "version": "0.85.0",
   "author": {
     "name": "Alberto Vioque",
     "email": "mashware@gmail.com"

package/plugins/flow/CHANGELOG.md

@@ -5,6 +5,48 @@ 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.85.0 — An unattended run answers its reviewers and fixes its own pipeline  ·  2026-10-01
+
+**In short**
+- **Review comments on a draft no longer stop an unattended run.** Relaunched with `why = review`,
+  `/flow:work:run` hands the run to `/flow:work:respond`, which reads the threads from the
+  orchestrator (`events --json`), answers each one through it (`reply --thread … --body-file …`),
+  commits what was agreed and hands the work back with `publish` — or `done` when only replies were
+  needed. It still never resolves a thread.
+- **A red pipeline is fixed at the root, or named.** Relaunched with `why = pipeline`,
+  `/flow:work:green` reads the failed jobs and their log tails from the orchestrator, fixes and
+  verifies locally, and ends with `publish`. A flake, an infrastructure failure, a conflict, or
+  anything that needs a rebase or a force-push ends `blocked` with the reason: reruns and the
+  red-round limit belong to the orchestrator. Green-washing stays forbidden in every mode.
+- **What only a person can settle is asked once, before anything is posted**: one question for
+  every thread that needs a product decision or a call the recorded design does not make.
+- Nothing changes in `manual`, `guided` or `auto`. Completes #177.
+
+## v0.84.0 — An unattended run talks to its orchestrator through one command  ·  2026-10-01
+
+**In short**
+- **Whoever launches an unattended run now names one command, and flow talks to it through that
+  command alone.** Set `autonomy.orchestrator_cmd` (for example `orch`): the run asks it why it was
+  launched, reads the ticket and the answer from it, and ends with exactly one order — `ask` a
+  question, `publish` the finished work, say it is `blocked`, or say it is `done`.
+- **flow no longer pushes or opens MR/PRs in this mode, and needs no forge credentials.** When the
+  work is ready it commits on its own branch and hands over a title and a body; the orchestrator
+  pushes the branch and opens the draft. A split task says which part it is (`--part 2 --of 3`).
+- **One entry for every run: `/flow:work:run`.** It starts a new feature or bug from the ticket the
+  orchestrator serves, continues after an answer exactly where the run stopped, or builds the next
+  part once the previous one merged. Review comments and red pipelines end the run as "not
+  supported yet" until the next version.
+- **The stop and answer files are gone** — `.claude/work/stop.json`, `.claude/work/answer.json`, the
+  `running` mark, the person pickup and `autonomy.unattended_ship`. A pending question is recorded
+  in `meta.json.pending`; every free text (question, options, title, body, reason) travels in a
+  file, never on a command line, so a backtick in a ticket title cannot reach a shell.
+- **`unattended` without `orchestrator_cmd` runs nothing** and says why; `/flow:doctor` flags it.
+- The Codex/OpenCode smoke runner now judges the call log of a fake orchestrator
+  (`script/tests/fixtures/fake-orchestrator.sh`) instead of the stop file.
+
+Breaking for anyone running `unattended` on 0.82/0.83: add `orchestrator_cmd` and launch
+`/flow:work:run`. Nothing changes in `manual`, `guided` or `auto`. Tracked in #177; makes #176 moot.
+
 ## v0.83.1 — Every unattended phase reads its stop-file rules whole  ·  2026-09-30
 
 **In short**

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

@@ -100,11 +100,10 @@ How much the flow advances on its own vs. stopping to ask you.
                       #   auto   — as guided, plus auto-resolves the remaining decision points with sensible
                       #            (recorded) defaults, chaining phases without pausing.
                       #   unattended — as auto, for a run nobody watches (script, container, headless CLI):
-                      #            never asks; each hard gate is recorded, becomes a draft MR/PR, or ends
-                      #            the run with a question in .claude/work/stop.json for a runner to
-                      #            post; its answer comes back in .claude/work/answer.json and the run
-                      #            continues, or a person picks it up. One MR/PR per run. Only when set explicitly —
-                      #            in a FLOW file only the runner's environment reads.
+                      #            never asks; driven by `orchestrator_cmd`. Each hard gate is recorded or
+                      #            ends the run with one order to that command (ask · publish · blocked ·
+                      #            done); flow never pushes or opens an MR/PR. One MR/PR per run. Only when
+                      #            set explicitly — in a FLOW file only the orchestrator's environment reads.
                       # HARD GATES stop and ask in manual/guided/auto, no exceptions: any push or MR/PR (ship),
                       # branch creation with an ambiguous base, DB schema changes/migrations, a review
                       # with high-severity findings, and the business brief confirmed just before the
@@ -113,10 +112,10 @@ How much the flow advances on its own vs. stopping to ask you.
                       # (panels, challengers, how many reviewers), WIP commits, continuing a train when
                       # the train's next MR/PR in `guided`/`auto`, size confirmation, and anything already decided
                       # and recorded — only new contradicting evidence reopens a settled decision.
-- `unattended_ship:`  # What `ship` does in `unattended`: `draft` | `stop`. Empty = `stop`.
-                      #   draft — push the work branch and open the MR/PR as draft; never merge, never ready.
-                      #   stop  — nothing is pushed; ship ends the run with a question in stop.json.
-                      # Read only when mode is `unattended`.
+- `orchestrator_cmd:` # Required in `unattended`: the command that run talks to, e.g. `orch`.
+                      #   It says why the run was launched, serves the ticket and the answer, and takes
+                      #   the run's one closing order (`ask`, `publish`, `blocked`, `done`). Read only
+                      #   in that mode. The orders: flow-core §2.1.
 
 ## quality
 Repo commands for quality gates, whatever the stack — `make test`, `./gradlew test`, `dotnet test`,