OpenCode 2.3.0 compatibility
Ticket #286. This record covers the host-range expansion from 2.2.6 || 2.2.7 to 2.2.6 || 2.2.7 || 2.3.0.
Environment
| Item | Value |
|---|---|
| Base | 4ccc410 (ticket/286-opencode-230) |
| Platform | Linux/tmux 3.5a |
| Node | 26.12.1 |
| OpenCode | 2.3.0 and 2.2.7 |
| Isolation | scripts/lib/live-harness.sh; fresh HOME/XDG roots, project, workspace, fake provider, and host per run |
Scope
The runtime behavior is unchanged. The host contract probe on 2.3.0 passes every check; the only pre-existing failure was the version gate. The deterministic fake E2E exposed one host-theme difference: focused headings and borders use the host's high-contrast text tone (#eeeeee, SGR 38;2;238;238;238) instead of exact white. The harness now accepts both tones for focus while keeping unfocused grey distinct.
Evidence
| Command | Host | Result |
|---|---|---|
npm run test:live:fake:all (ENSEMBLE_LIVE_REQUIRE=1) | 2.3.0 | PASS — fake 407 s and fake-empty 9 s, 2 passed, 0 failed, 0 skipped, 0 retries |
npm run test:live:fake:all (ENSEMBLE_LIVE_REQUIRE=1) | 2.2.7 | PASS — fake 407 s and fake-empty 9 s, 2 passed, 0 failed, 0 skipped, 0 retries |
npm run test:live:probe | 2.3.0 | PASS — 14/14 contract tests; all direct, workspace, retry, interruption, attachment, synthetic, subagent, delivery, move, and session-list scopes matched |
npm run test:live:sizes | 2.3.0 | PASS — 80x24, 100x30, 120x40, and 160x50, including white focused / grey unfocused headings and borders |
npm run test:install:rc | 2.3.0 | PASS — @heyimteee/ensemble@0.1.0-rc.2, 507,907-byte tarball, loopback registry, opencode plugin add, six server tools, TUI route and /ensemble |
npm run verify | — | PASS — 2120 tests, typecheck clean |
npm run docs:check | — | PASS — contract v7; OpenCode 2.2.6, 2.2.7, 2.3.0; Node >=22.23.4; live Node 26.12.1 |
Required CI at a7f1eb3 | 2.2.6, 2.2.7, 2.3.0 | PASS — Compatibility and all required workflows green on the first attempt, no job rerun |
The fake runs use the committed fake provider only; no real model catalog and no network model calls are involved. The probe writes a sanitized JSONL record to a temporary path and does not refresh the committed 2.2.6 fixture.
CI contract
.github/workflows/compatibility.ymlruns the host probe and deterministic fake smoke for2.2.6,2.2.7, and2.3.0.REQUIRED_STATUS_CHECKSanddocs/operations/release.mdincludeOpenCode 2.3.0; ruleset27380159includes that context, and thea7f1eb3run made it green on the first attempt.verify.ymlandnightly.ymlpinOPENCODE_VERSION: "2.3.0"because the contract checker requires the latest supported host.2.2.6and2.2.7remain supported and in the compatibility matrix.
Remaining limitations
- macOS/Herdr is verified on OpenCode 2.2.7 only (#277); 2.3.0 macOS is not claimed. This record is Linux/tmux evidence for 2.3.0.
- OpenCode releases newer than
2.3.0remain untested and load with the runtime warning. - The committed native host fixture remains the 2.2.6 recording; the 2.3.0 probe matched the same contract and was not written over it.