opencode-plugin-flow 8.1.2 → 8.2.0

package/CHANGELOG.md

@@ -2,6 +2,57 @@
 
 One short entry per release, written for users deciding whether to upgrade.
 
+## [8.2.0] - 2026-08-31
+
+Reviewer selection is now native plugin configuration, and Flow reports enough
+derived evidence for a bounded delivery handoff.
+
+- OpenCode plugin tuple options can select the reviewer model and step budget.
+  Flow resolves the selection once per process and reports it in `/flow-status`.
+  Environment variables remain fallback configuration.
+- Every accepted close returns a deterministic, versioned delivery summary with
+  feature attempts, outcomes, terminal findings, changed-artifact declarations,
+  and tiered assurance. The handoff grants no external action authority.
+- A new quickstart and structured external pilot cover installation, reviewer
+  selection, first-run checks, recovery, and feedback without telemetry.
+- Report-only evals now measure repository gate discovery and task-specific risk
+  questions. Eval host configuration uses the same reviewer tuple as production,
+  and release notes derive their provider evidence from retained artifacts.
+- **Session v5 schema:** unchanged. Runtime tools, commands, guides, and agents
+  keep their existing names and inputs.
+
+Install or update:
+
+```bash
+opencode plugin opencode-plugin-flow@8.2.0 --global --force
+```
+
+## [8.1.3] - 2026-08-28
+
+Release claims now come from retained evidence instead of trusted summaries.
+
+- Declared gate assertions must be satisfied before final review and completed
+  closure. New named evidence writes JUnit to the plan-bound
+  `.flow/results.xml`; execution cannot substitute another path. Reports are read once
+  from a stable, bounded workspace file without following symlinks.
+- Eval failures identify the evaluator, provider, host, or persistence boundary
+  that produced them. The release matrix uses repository-owned policy with enough
+  attempts to measure its 90% and 100% thresholds.
+- Exact-artifact canary results are derived from one OpenCode session lineage.
+  Release qualification seals all attempts, transcripts, provenance, canary,
+  artifact, and grader source into an immutable bundle that CI independently
+  reopens and regrades.
+- Publication requires the tag and packed artifact to match the release evidence.
+  npm and GitHub operations are bounded and idempotent, refuse conflicting bytes,
+  and recover through an exact draft without destructive asset replacement.
+- **Session v5 schema:** unchanged. Runtime commands and tools are unchanged.
+
+Install or update:
+
+```bash
+opencode plugin opencode-plugin-flow@8.1.3 --global --force
+```
+
 ## [8.1.2] - 2026-08-26
 
 Long Grok eval turns no longer fail at Bun's implicit five-minute fetch cutoff.

package/README.md

@@ -40,7 +40,7 @@ expensive, and it is overhead when it is not.
 Install the exact npm release through OpenCode:
 
 ```bash
-opencode plugin opencode-plugin-flow@8.1.2 --global --force
+opencode plugin opencode-plugin-flow@8.2.0 --global --force
 ```
 
 Omit `--global` for project scope. Version pins are exact and never update on
@@ -51,10 +51,28 @@ The equivalent manual project configuration is:
 ```json
 {
   "$schema": "https://opencode.ai/config.json",
-  "plugin": ["opencode-plugin-flow@8.1.2"]
+  "plugin": ["opencode-plugin-flow@8.2.0"]
 }
 ```
 
+For an explicit reviewer model, use OpenCode's plugin tuple options:
+
+```json
+{
+  "$schema": "https://opencode.ai/config.json",
+  "plugin": [
+    [
+      "opencode-plugin-flow@8.2.0",
+      { "reviewer": { "model": "provider/model", "steps": 80 } }
+    ]
+  ]
+}
+```
+
+The tuple values take precedence over `OPENCODE_FLOW_REVIEWER_MODEL` and
+`OPENCODE_FLOW_REVIEWER_STEPS`. `/flow-status` reports the process-local
+selection, but only a successful reviewer run confirms model availability.
+
 Restart OpenCode after changing configuration. OpenCode owns installation and
 configuration; see its
 [plugin documentation](https://opencode.ai/docs/plugins/). Flow has no installer
@@ -68,6 +86,9 @@ remain inert history, and there is no migration or rollback layer.
 
 ## Quick start
 
+For a clean installation and reviewer-configuration check, follow the
+[quickstart](docs/quickstart.md).
+
 ```text
 /flow-auto add rate limiting to the public API
 ```
@@ -127,9 +148,10 @@ you granted.
 6. A passing review advances the plan. A failed feature is never picked up again
    implicitly — Flow reports the blocker and waits for an explicit retry or an
    independent-feature choice. The last passing feature allows closure, and every
-   accepted close returns a delivery summary derived from recorded state: each
-   feature's attempts, latest outcome, terminal findings, and tiered assurance with
-   explicit limitations.
+   accepted close returns a versioned delivery summary derived from recorded state:
+   each feature's attempts, latest outcome, terminal findings, and tiered assurance
+   with explicit limitations. Delivery grants no PR, merge, publish, or release
+   authority.
 
 Findings keep stable ids across retries, and a failed review must carry every
 still-live finding forward — the runtime rejects a submission that drops one. A