opencode-plugin-flow 4.2.0 → 4.3.0

package/CHANGELOG.md

@@ -2,6 +2,49 @@
 
 One short entry per release, written for users deciding whether to upgrade.
 
+## [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.
+
+## [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.
+
 ## [4.2.0] - 2026-07-01
 
 Safety and usability overhaul across the runtime, packaging, skills, and docs:

package/README.md

@@ -11,11 +11,14 @@ review, and orchestration judgment, while the plugin runtime stays deliberately
 small — it keeps the session ledger and enforces the hard gates prompts should
 not be trusted to remember.
 
+Full project documentation is available in the
+[Flow OpenCode wiki](https://github.com/ddv1982/flow-opencode/wiki).
+
 ## Quick start
 
 ```bash
-opencode plugin opencode-plugin-flow@4.2.0 --global --force
-npx -y opencode-plugin-flow@4.2.0 sync
+opencode plugin opencode-plugin-flow@4.3.0 --global --force
+npx -y opencode-plugin-flow@4.3.0 sync
 ```
 
 Restart OpenCode, then give Flow a goal:
@@ -71,7 +74,8 @@ Commands are bundled entrypoints: they carry their own instructions, so they
 keep working even when OpenCode's native skill discovery lags behind a fresh
 install (see [docs/troubleshooting.md](docs/troubleshooting.md)).
 
-`flow-test` and `flow-commit` are managed helper skills, not public commands.
+`flow-test`, `flow-deslop`, `flow-ui-quality`, and `flow-commit` are managed
+helper skills, not public commands.
 `flow-commit` is user-triggered only and stays outside the autonomous loop.
 
 ## Tools
@@ -131,7 +135,7 @@ To update a pinned Flow version, rerun the install command with the new
 version. To inspect skill health:
 
 ```bash
-npx -y opencode-plugin-flow@4.2.0 doctor
+npx -y opencode-plugin-flow@4.3.0 doctor
 ```
 
 ## Experimental: compaction context