Repository navigation
v0.74.0
Audit: gaps closed, dead code out. A full read of the extension, core and playbook parser after 0.73.0's reset.
Fixed
flow approve --yoloandflow release --no-versionnow take effect only after the operator answers the checkpoint. Before, a refused or headless call still saved yolo/no-version, so it applied to the next gate.- A session opened inside a feature worktree now drives the main checkout's flow. Before,
flowgates, the footer, the context injection, compaction and claims read the worktree's own.dev-flow/; only the guards resolved the main checkout. flow healthnow runs aflow-check healthblock (it used to requirehealth =). The health probe insideflow checknow seeds first and retries withinhealthWait, the same probe verify runs.- A
health =key plus aflow-check healthblock no longer produce twohealthchecks. - The drafted mockup checklist item is now
(ui)-only, so non-UI features no longer have to confirm it. - Aborting a plan-stage feature that has a written plan now needs the operator's word (
--confirmed, or a dialog).
Removed
- The unreachable
donestage.flow finishdeletes the state, so nothing ever wrote it. - Legacy compatibility:
- the
project.jsonrefusal and doctor finding; - the
.currentcleanup; - the
github/release.githubalias forreleases; release.*keys under## global(use## release/## pre-release);- inline
(plugin)markers in flatreflections.mdfiles; - release-done re-reading the manifest for flows approved before the release gate recorded their version.
- the
- Re-running
flow initon an existing playbook no longer offers to regenerate it. It always refused for a hand-edited file anyway, and now it prints the doctor's findings. - An edit-tool write in a worktree no longer wipes recorded checks on the spot. The worktree fingerprint at verify/release is the single staleness check, and it already catches bash edits.
- An auto-compaction no longer queues a
reflections.mditem.
Changed
- Repeated git, forge and registry probes now go through shared helpers.
flow helpis shorter.- The checkout guard sees a branch behind leading flags (
git checkout -f feat/x) and ignores paths after--.