v4.3.4

[4.3.4] - 2026-07-07

Planning and final-review lore sharpened without changing the runtime surface:

• flow-plan now has a pre-approval quality gate that checks outcome,
  requirements, decisions, uncertainty, feature shape, bounded targets,
  validation levels, dependencies, and review policy before a plan is saved or
  approved.
• Planning examples now cover bugfix, UI/frontend, runtime/schema, docs-only,
  audit-first, and stronger validation patterns, giving agents better few-shot
  guidance for common Flow sessions.
• Final review now includes a convergence scan that traces the original goal,
  approved requirements, every planned feature, changed artifacts, and
  validation evidence before returning a passing finalReview.
• The new planning checklist is shipped through synced skills and bundled
  /flow-plan and /flow-auto command instructions, so fresh and stale skill
  discovery paths get the same guidance.

v4.3.3

[4.3.3] - 2026-07-07

Verification only — no behavior change:

• The live OpenCode smoke test now proves the hidden read-only workers'
  isolation actually binds at runtime: against a real server it asserts each
  worker's resolved permission rules deny the state-changing flow_* tools,
  task, skill, and edit, while keeping flow_status readable. This
  confirms OpenCode compiles Flow's tool-name and wildcard permission keys
  (which are absent from the SDK's simplified permission type) rather than
  silently dropping them, closing the one unverified question from the 4.3.2
  review.

v4.3.2

[4.3.2] - 2026-07-07

Correctness and safety hardening from a full-project review, repairing two
edges introduced in 4.3.1 and several older ones:

• Uninstall no longer deletes a user file that merely resembles a backup name:
  a file counts as removable Flow residue only when its name and its content
  checksum both match Flow's backup format. Doctor applies the same check.
• Sync no longer overwrites a user-owned skill folder that has files at managed
  paths but no SKILL.md — any managed folder without a Flow marker is left
  untouched, not clobbered without a backup.
• An empty HOME no longer makes the skills root a current-directory-relative
  path (which sync wrote into and uninstall removed); it falls back to the OS
  home. engines now requires Node >=20.12 (doctor/uninstall rely on it).
• The CLI no longer aborts on a stray flow-* file in the skills root, and a
  CRLF-converted skill marker is no longer misreported as outdated.
• Session locks recover from more failure modes: a far-future or foreign-host
  lock timestamp and a recycled process id are now reclaimable instead of
  wedging every Flow call, and stale-lock reclamation no longer races two
  waiters into holding the lock at once.
• flow_status re-checks the session under the lock before quarantining, so a
  session written by a concurrent process can't be quarantined by mistake; a
  session file with an archive-unsafe id now routes to quarantine recovery
  instead of wedging every archive; and its output is framed as data to blunt
  instruction-injection from a cloned repo's session file.
• A user command named like an object built-in (e.g. /toString) no longer
  crashes command preflight, and a Flow command invoked with an attachment now
  keeps its worker isolated instead of double-running the instructions.
• Session history is bounded so long autonomous loops cannot grow the session
  file without limit. Docs corrected to match the current uninstall/doctor
  behavior.

v4.3.1

[4.3.1] - 2026-07-06

Doctor and uninstall now account for the .backup files Flow writes when it
retires a locally-edited managed skill file:

• doctor reports leftover .backup files as action-required instead of
  saying "ok", lists each one, and explains that they hold your earlier edits
  and can be deleted once you no longer need the saved copy.
• uninstall treats a folder that is pristine apart from Flow-created
  .backup residue as removable and names the removed backup files, so the
  cleanup is no longer silently blocked or silently destructive.

v4.3.0

[4.3.0] - 2026-07-06

Parallel orchestration reworked into a single pass playbook, plus sharper
planning and routing:

• The parallel-orchestration references collapse into one playbook with an
  explicit loop — orient, slice, manifest, fan out, account, verify,
  synthesize, extend or stop — so a manager reads one file instead of four
  cross-linked ones. Every bundled public Flow command got smaller as a result.
• A new pass manifest doubles as the pre-fan-out coverage gate and the
  accounting contract: one row per slice with its scope, expected coverage, and
  verification tier, and N rows spawned means N handoffs accounted for before
  synthesis.
• A worker-failure ladder handles a slice that errors, blocks, or returns
  partial: re-spawn once narrower, cover it directly, or carry it into the
  synthesis explicitly as not-covered — never as if coverage were complete.
• flow-plan gains uncertainty-typed decomposition: resolve specification
  uncertainty by stating an assumption (or asking when a wrong guess is costly)
  and environment uncertainty by inspecting, never by asking.
• Frontmatter descriptions for flow-plan, flow-run, and flow-review now
  describe only when to reach for each skill, so single-phase asks route
  cleanly.

v4.2.1

[4.2.1] - 2026-07-05

Skill routing and boundary clarity across the managed skill set:

• Frontmatter descriptions now route single-phase asks cleanly: flow
  defers plan-only work to flow-plan and single-feature execution to
  flow-run, flow-test no longer claims every testing intent,
  flow-deslop leaves review verdicts to flow-review, and
  flow-ui-quality hands browser-run mechanics to flow-test.
• flow-deslop and flow-ui-quality now state explicitly that they are
  helper skills: they contribute evidence only, and the manager owns every
  state-changing flow_* call.
• The flow skill gained a routing note covering plan-only, single-feature,
  and status-only asks, and flow-review names its manager context
  accurately (the flow/flow-run skills or a bundled public Flow command).
• The repo-local contribution preflight now states its output is commit/push
  readiness evidence only and never substitutes for Flow validation or
  review evidence.
• README lists all four managed non-command helper skills.

v4.2.0

[4.2.0] - 2026-07-01

Safety and usability overhaul across the runtime, packaging, skills, and docs:

• Uninstall no longer deletes managed skill folders that contain your own
  files or have a damaged version marker; uninstall --dry-run previews
  removals.
• Crashed sessions recover: stale session locks expire automatically and the
  lock timeout error names the manual fix; corrupt or older-version
  session.json files are quarantined into .flow/history/ with recovery
  guidance instead of failing every tool with a raw validation dump.
• Fixed a batch of small correctness bugs: $-sequences in goals no longer
  get mangled, attachments to Flow commands are preserved, failed plan saves
  no longer discard the previous session, replacing a draft plan archives it,
  and needs_input no longer reports a stale prior error.
• OpenCode compatibility: the peer dependency is now a range
  (>=1.17.3 <2) so newer OpenCode versions install cleanly; a live smoke
  test boots a real OpenCode server against the packed tarball in CI; CI runs
  on macOS and Node 20/22/24; published bundles are no longer minified and
  ship sourcemaps.
• Skills: repo-specific content removed from distributed skills, duplicated
  orchestration rules consolidated (smaller command prompts), the read-only
  reviewer no longer receives instructions it cannot execute, and managers
  are told to paste handoff templates into worker prompts.
• New opt-in FLOW_EXPERIMENTAL_COMPACTION=1 injects the active session
  summary into OpenCode session compaction; the default stays hook-free.
• README rewritten around a quick start; install/repair depth moved to
  docs/troubleshooting.md.

v4.1.18

[4.1.18] - 2026-07-01

Teach Flow's skill review lore to keep audit fallback bundled, commit preflight staged-only, and long references navigable.

v4.1.17

[4.1.17] - 2026-06-28

Teach Flow's parallel pass lore to verify worker handoffs, prune retired managed skill files, and keep manager-owned synthesis explicit.

v4.1.16

[4.1.16] - 2026-06-22

Quote Flow skill frontmatter lore so GitHub previews parse cleanly and CI guards future YAML slips.