v9.0.1

[9.0.1] - 2026-09-18

Internal runtime refactor. No new commands, tools, or settings.

• Flow now checks its workspace when the plugin loads instead of on the first
  flow_* call. Starting OpenCode with the filesystem root or your home
  directory as the project refuses to load Flow and logs the reason, where it
  previously loaded and then failed the first tool call.
• Sending an identical flow_feature_complete request twice returns the same
  response as before; the replay now takes the session lock once.
• The application, persistence, and auto-drive code is split into smaller
  modules with one source of truth for session validation and review
  readiness. Persisted .flow/session.json files from 9.0.0 load unchanged.
• Session v5 schema, validation gates, reviewer authority, and continuation
  routing are unchanged. No live model eval or paid canary was run for this
  candidate.

Upgrade with opencode plugin opencode-plugin-flow@9.0.1 --global --force.

Reviewed offline feature qualification

Policy: runtime-refactor-v1, for 9.0.1 only. Reviewed code: 8d275b7.
Candidate artifact: sha256:96f90ae380ed9dd155b4973be850ecc42205d180bdda4e3c2049c5bbe3ac7478. Qualification record: sha256:498bf32c9d01cbe24bd9fc5096c6ee52e83de310333f9bdf903dde2615597402.
No live model evals or canary were run for 9.0.1. Reviewed code, deterministic checks, replay and provider-free OpenCode UI/configuration checks support this feature release; they do not establish its live model behavior.
Prior measured artifact (8.3.0): sha256:f2cad40877d616a25df9f675ddbd4aeb0e0a6a342ef246e5d109a3978c891563.
Prior bundle: sha256:80df0f91aa3d8be2742383ca42c6b1a6b15e5450eaca7a9c2bc422f3ec75782a. Prior canary: sha256:8de004b8718714f73b361695d0cc54c423c711064ee79decf5d4d233e5950bd6.
Prior results only: 76/76. These are not measurements of 9.0.1, and no release after 8.3.0 has been measured live.
Scope approval: Operator approval in this Claude Code session, 2026-09-18. Explicitly authorized offline qualification for the 9.0.1 runtime refactor, after being told a funded live campaign was the alternative and that this entry freezes most of the runtime rather than one reviewed feature, which is the widest claim any release has made on an exception written for individually reviewed features. The candidate splits the application, persistence and auto-drive layers with no new tool, command or setting; the two behavior changes are workspace validation moving to plugin load and an identical feature-completion replay taking the session lock once. The operator also authorized reading a cited baseline canary as retained evidence, which is what made this release possible at all: the 8.3.0 canary expired on 2026-09-16 and the wall-clock rule had already made every published offline release unverifiable. The last live-measured release remains 8.3.0; 8.4.0, 8.5.0, 8.6.0 and 9.0.0 were also qualified offline and are not treated as baselines. No new live model eval or canary was authorized or run.