opencode-plugin-flow 4.1.5 → 4.1.7

package/CHANGELOG.md

@@ -3,6 +3,14 @@
 One short line per release. For the full rationale behind each entry, see the
 commit history and review evidence.
 
+## [4.1.7] - 2026-06-17
+
+Teach Flow's managed skill lore to test, commit, and trigger more precisely while keeping release state and `.flow/**` artifacts guarded by explicit maintainer intent.
+
+## [4.1.6] - 2026-06-16
+
+Make Flow's pinned installer path force-aware, so OpenCode replaces older global plugin entries instead of leaving stale versions behind.
+
 ## [4.1.5] - 2026-06-16
 
 Make Flow installation follow OpenCode's native plugin installer, with pre-start skill sync and older-version fallback.

package/README.md

@@ -1,6 +1,6 @@
 # Flow Plugin for OpenCode
 
-`opencode-plugin-flow` is a skills-first workflow helper for OpenCode. The skills carry planning, execution, validation, cleanup, UI quality, review, and orchestration judgment. The plugin code stays deliberately small: it keeps a durable `.flow/session.json` ledger and enforces the hard gates prompts should not be trusted to remember.
+`opencode-plugin-flow` is a skills-first workflow helper for OpenCode. The skills carry planning, execution, validation, cleanup, UI quality, review, safe commit preparation, and orchestration judgment. The plugin code stays deliberately small: it keeps a durable `.flow/session.json` ledger and enforces the hard gates prompts should not be trusted to remember.
 
 Flow v4 is a breaking simplification. It does not preserve v3 session layouts or retired tool aliases.
 
@@ -8,24 +8,26 @@ Flow v4 is a breaking simplification. It does not preserve v3 session layouts or
 
 - A resumable one-feature-at-a-time loop for larger coding work.
 - Skill-guided planning, running, validation, review, cleanup, and UI quality.
+- First-class validation guidance through `flow-test`, plus user-triggered safe
+  commit preparation through `flow-commit`.
 - Hidden evidence, review, validation, audit, verifier, and candidate workers for broad work.
 - Structured handoffs with coverage, evidence, confidence, and gaps.
 - Runtime gates for approval immutability, validation evidence, review evidence, and safe session closure.
 
 The manager still owns every Flow state change. Workers gather evidence; they do not approve plans, complete features, or close sessions.
 
-## Install
+## Install or update
 
 Use OpenCode's plugin installer when your OpenCode version supports it:
 
 ```bash
-opencode plugin opencode-plugin-flow@4.1.5 --global
-npx -y opencode-plugin-flow@4.1.5 sync
+opencode plugin opencode-plugin-flow@4.1.7 --global --force
+npx -y opencode-plugin-flow@4.1.7 sync
 ```
 
-The first command adds Flow to your global OpenCode plugin config. The `sync`
-command pre-installs Flow's managed skills so the next OpenCode startup can load
-the refreshed skill registry.
+The first command adds Flow to your global OpenCode plugin config or replaces an
+older pinned Flow entry. The `sync` command pre-installs Flow's managed skills so
+the next OpenCode startup can load the refreshed skill registry.
 
 Then start or restart OpenCode. On startup, the plugin syncs its global skills
 into:
@@ -34,9 +36,11 @@ into:
 ~/.config/opencode/skills/flow/SKILL.md
 ~/.config/opencode/skills/flow-plan/SKILL.md
 ~/.config/opencode/skills/flow-run/SKILL.md
+~/.config/opencode/skills/flow-test/SKILL.md
 ~/.config/opencode/skills/flow-review/SKILL.md
 ~/.config/opencode/skills/flow-deslop/SKILL.md
 ~/.config/opencode/skills/flow-ui-quality/SKILL.md
+~/.config/opencode/skills/flow-commit/SKILL.md
 ```
 
 If your OpenCode version does not have `opencode plugin`, add Flow to your
@@ -44,14 +48,18 @@ OpenCode config manually instead:
 
 ```json
 {
-  "plugin": ["opencode-plugin-flow@4.1.5"]
+  "plugin": ["opencode-plugin-flow@4.1.7"]
 }
 ```
 
+When updating through this fallback, replace the older
+`opencode-plugin-flow@...` entry with the new pinned version instead of adding a
+duplicate entry.
+
 Then run the same pre-start skill sync and start or restart OpenCode:
 
 ```bash
-npx -y opencode-plugin-flow@4.1.5 sync
+npx -y opencode-plugin-flow@4.1.7 sync
 ```
 
 Project-local skill overrides still work through OpenCode's normal lookup:
@@ -66,18 +74,17 @@ the skill registry for the running process, so a just-synced skill can exist on
 disk while still being unavailable to that process. Flow reports this through
 `flow_status` as `setup.skills.status: "restart_required"`.
 
-To update a pinned Flow version, replace the existing OpenCode plugin entry and
-sync the matching skill bundle:
+To update a pinned Flow version later, rerun the same install command with the
+new version.
 
-```bash
-opencode plugin opencode-plugin-flow@4.1.5 --global --force
-npx -y opencode-plugin-flow@4.1.5 sync
-```
+`--force` is intentional here: OpenCode keeps an existing same-package plugin
+entry unless replacement is requested, so the flag avoids leaving an older pinned
+version in your global `opencode.json`.
 
 To inspect the installed skill set:
 
 ```bash
-npx -y opencode-plugin-flow@4.1.5 doctor
+npx -y opencode-plugin-flow@4.1.7 doctor
 ```
 
 If a command reports `Skill "flow-review" not found. Available skills...` or a
@@ -85,14 +92,14 @@ similar Flow skill-loading error, run `/flow-status` or the doctor command above
 first. Missing, incomplete, or outdated managed skills can be repaired with:
 
 ```bash
-npx -y opencode-plugin-flow@4.1.5 sync
+npx -y opencode-plugin-flow@4.1.7 sync
 ```
 
 Then restart OpenCode so the refreshed registry is loaded. `sync` manages all
-bundled Flow skills: `flow`, `flow-plan`, `flow-run`, `flow-review`,
-`flow-deslop`, and `flow-ui-quality`. If doctor reports a foreign or edited
-managed skill folder, Flow leaves it in place and asks for a user decision
-instead of overwriting local work.
+bundled Flow skills: `flow`, `flow-plan`, `flow-run`, `flow-test`,
+`flow-review`, `flow-deslop`, `flow-ui-quality`, and `flow-commit`. If doctor
+reports a foreign or edited managed skill folder, Flow leaves it in place and
+asks for a user decision instead of overwriting local work.
 
 ## Commands
 
@@ -106,6 +113,10 @@ Commands are thin pointers into skills:
 | `/flow-review` | Run a read-only review. |
 | `/flow-status` | Show the active session and next action. |
 
+`flow-test` and `flow-commit` are managed helper skills, not public commands in
+this release. `flow-commit` is user-triggered only and stays outside the
+autonomous Flow runtime loop.
+
 ## Tools
 
 The runtime exposes seven tools:
@@ -148,9 +159,9 @@ Planning quality, decomposition, review depth, validation adequacy, orchestratio
 .flow/session.lock/
 ```
 
-Versioning `.flow` state is opt-in. Edit `.flow/.gitignore` or use
-`git add -f` only when a repository intentionally wants to archive Flow session
-evidence.
+Versioning `.flow` state is opt-in. Keep it ignored by default, and archive only
+exact Flow session artifacts when a maintainer intentionally asks for them; avoid
+broad forced adds of `.flow/**`.
 
 ## Development
 
@@ -177,7 +188,7 @@ First remove `opencode-plugin-flow` from your OpenCode plugin config so future
 OpenCode startups stop loading Flow. Then remove Flow-owned synced skills:
 
 ```bash
-npx -y opencode-plugin-flow@4.1.5 uninstall
+npx -y opencode-plugin-flow@4.1.7 uninstall
 ```
 
 Restart OpenCode after both steps. This removes Flow-owned synced skills when