flow-workflows 0.86.0 → 0.88.0

package/plugins/flow/CHANGELOG.md

@@ -5,6 +5,35 @@ 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.88.0 — A study made for handoff ends at the handoff, not at build  ·  2026-10-02
+
+**In short**
+- **With `git.handoff_branch` set, finishing a study leads to handing it off.** The plan, the design
+  of a small task, a bug's investigation, an XS start — and `resume` — point at
+  `/flow:work:handoff` instead of building here. In `manual` the question recommends **Hand off the
+  study** and keeps **Build here** second; `guided` and `auto` go on to the handoff by themselves,
+  whose push question is the only one added.
+- **Pair the key with `autonomy.mode: auto`** and the whole study runs without launching each phase,
+  stopping only on a real doubt or a serious design finding, up to the push.
+- **A refused handoff names the way on**, building here included.
+- Nothing changes on the server (`unattended`) nor in repos without the key. Closes #189.
+
+## v0.87.0 — A finished study is handed off from the laptop, and summarised in its ticket  ·  2026-10-01
+
+**In short**
+- **`/flow:work:handoff` hands a study to whoever builds it elsewhere.** It pushes this work's
+  folder, and nothing else, as a commit with no history to the branch `git.handoff_branch` names
+  (e.g. `study/{TICKET}`). Your current branch, staged changes and other works are never touched,
+  even when `.claude/work/` is git-ignored.
+- **It refuses a study that cannot stand on its own** — its design or plan not closed, a question
+  pending, a clarification open — and writes down first what this session decided but no file says.
+- **It asks before the push, and never forces**: a branch that already exists is refused, with what
+  to do next.
+- **A summary for the ticket**, offered after the push: what and why, criteria, design in brief,
+  MR/PR plan and risks, in a marked block that keeps the ticket's own text and is replaced on a
+  second run. GitHub and GitLab out of the box; new key `tracker.edit_cmd`.
+- Completes #186.
+
 ## v0.86.0 — An unattended run builds a study made on another machine  ·  2026-10-01
 
 **In short**

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

@@ -48,6 +48,7 @@ How tickets are identified and read.
                       # they are asked before running in `autonomy.mode: manual` and run automatically in `guided`/`auto`;
                       # a failure or an already-in-state ticket warns and continues, never blocks. They run only in
                       # ticket mode with a real tracker id (skipped for ticket-less / local-only works).
+- `edit_cmd:`         # optional, rewrites a ticket's BODY from a file: `/flow:work:handoff` writes its study summary with it. `{TICKET}` and `{BODY_FILE}` substituted. Empty = derived for `gh` (`gh issue edit {TICKET} --body-file {BODY_FILE}`) and `glab` (`glab issue update {TICKET} --description-file {BODY_FILE}`); other trackers get no summary — flow cannot read their body back to keep its text.
 - `followup_ask_max:` # how many parked findings one finished work may turn into questions at `ship`'s Close (flow-core §7). Empty = 2. `0` = never ask, log everything. A ticket where
                       #   seven phases each notice something is not seven problems: with 3+ candidates a skeptic tries to refute each one (burden of proof on the finding), the ones
                       #   without a named subject are dropped, and only the strongest survivors up to this number are put to you. Raise it if you would rather triage than be handed a log.
@@ -86,6 +87,8 @@ Branch and Pull/Merge Request conventions.
                       #   - make database-update
                       #   - make frontend
 
+- `handoff_branch:`   # branch `/flow:work:handoff` pushes a finished study to, holding only that work's folder. `{TICKET}` substituted. Empty = the command refuses: where a study goes is the receiver's convention. e.g. `study/{TICKET}`. Set → the study phases end at `/flow:work:handoff` instead of `build`/`fix` (not in `unattended`); pair it with `autonomy.mode: auto` and the study runs on its own up to the push.
+
 ## autonomy
 How much the flow advances on its own vs. stopping to ask you.