Skip to content

Ticket #233/#234: native probe version set and stale live harness — verification ​

  • Date: 2026-11-11
  • Branch: ticket/233-e2e-harness
  • Base: integration/native-first at 59fe20c
  • Issues: #233, #234
  • Unit gate: npm run verify (strict typecheck + full test suite)

Fixes ​

  1. #233 — src/v2/native-host-fixture.test.ts accepted only OpenCode 2.2.6. It now accepts the re-verified patch set 2.2.6 and 2.2.7, still validates the committed 2.2.6 fixture, and records the fresh 2.2.7 run in the native host contract record without replacing the 2.2.6 evidence.
  2. #234a — scripts/live-check-fake.sh expected › Model after G in General settings. The Native mirror row is now last, so the check expects › Native mirror and still proves gg returns to › Name.
  3. #234b — scripts/live-lifecycle-fake.sh reached Work selection (NORMAL │ Work list) and pressed f without entering Work interaction. It now uses live_focus_work_interact, requires the j/k cards interaction hint, and then toggles and verifies WORK HISTORY │.

No product behavior changed.

Results ​

CommandResult
npm run verifyPass — strict typecheck; 1811 tests passed, 0 failed, 0 skipped, 0 todo
npm run test:live:probePass — isolated OpenCode 2.2.7 host + fake provider; 14/14 contract tests against the fresh record
npm run test:live:fake:allPass — fake 456 s, fake-empty 9 s; 2 passed, 0 failed, 0 skipped
npm run test:live:lifecyclePass — heartbeat at 70 s, delivery deadline crossed at 313626 ms while working, backlog stayed pending, both turns replied, HISTORY retained both cards
git merge integration/native-firstAlready up to date at 59fe20c

Before the harness fixes, G timed out waiting for › Model, and the lifecycle f key did not toggle HISTORY. After the fixes, both suites pass without weakening their assertions.

#233 and #234 can close: the supported probe version set is explicit, the 2.2.6 fixture remains valid, and every acceptance command passes.

Released under the MIT License.