Ensemble v5 acceptance — 2026-11-01
Ticket: #47, parent #42. Tested from feat/v5-47, based on integration commit 5bb01fe5a260977cbd1b61254c46c437d2b4d3df. No product changes were needed.
Environment and commands
Working directory: /tmp/opencode/ensemble-worktrees/47-acceptance. Every npm/Node command used:
export PATH=/home/tristan/.nvm/versions/node/v26.12.1/bin:/home/tristan/.local/bin:$PATHnode --version: v26.12.1; npm --version: 12.2.1; opencode --version: opencode v2.2.3. Linux, /usr/bin/tmux, and fd were available. npm ls @opencode/plugin @opentui/core @opentui/solid solid-js confirmed 2.2.1 / 0.7.0 / 0.7.0 / 1.9.12 respectively. Pinned host types 2.2.1 and tested host 2.2.3 are distinct evidence, not a claim of version identity or universal compatibility.
| Exact command | Result |
|---|---|
npm ci | Exit 0; 376 packages added. Audit warning below. |
npm run check | Exit 0; strict no-emit TypeScript check. |
npm test | Exit 0; 122 passed, 0 failed, 0 skipped, including doctor diagnosis/CLI tests. |
ENSEMBLE_LIVE_DEBUG=1 npm run test:live | Exit 0; live-check passed; no prerequisite or model-dependent skip. |
ENSEMBLE_LIVE_DEBUG=1 npm run test:live:fake | Exit 0 twice independently; both printed fake live-check passed; no skips. |
TMPDIR=/tmp/opencode node --test --experimental-strip-types src/v2/doctor-cli.test.ts | Exit 0; all 7 passed. Spawned CLI agreement exits 0, synthetic config/storage membership mismatch exits 1, invalid snapshot/auth/usage/connection failures exit 2. |
npm run verify | Exit 0; check plus 122 passing tests, no skips. |
Negative compiler check: temporarily added src/v2/acceptance-typecheck-probe.ts with const acceptanceTypecheckProbe: string = 47 and an export. npm run check exited 1, reporting TS2322 at line 2. Removed only that probe; npm run verify then passed. The probe is not committed.
The real scenario exercised agent/workspace wizards, completions, sending, command palette, RPC deletion, help, and return to native TUI. Its send assertion is not proof of a successful external model response. Both fake runs used only the configured loopback fake provider (single-model assertion, clean child environment, external model catalog/free models disabled): streamed rich Markdown, finalization, single reply markers, no remaining streaming label, help/search, Linux Ctrl labels, and no stale markers after leaving. This is behavior/content evidence, not pixel-perfect styling, every resize/long-history case, or live macOS verification.
Real-location doctor
Executed with exit propagation and summary-only output to avoid sharing runtime identities or content:
set -o pipefail
npm run doctor -- /home/tristan/dev/ensemble /home/tristan/dev/vera-app | grep '^Summary:'Exit 0: Summary: 0 mismatches across 2 locations. A separate JSON invocation (npm run --silent doctor -- --json /home/tristan/dev/ensemble /home/tristan/dev/vera-app, filtered in memory to summary/caveats) reported ok: true, 2 locations, 1 service, 0 mismatches, crossLocation: true, crossService: false. No real-location invoke/repair/reset/delete command was used.
Snapshot caveat: doctor calls only snapshot and does not itself write files, but server-side snapshot discovery can reconcile and persist state. This is post-reconciliation agreement, not proof of a write-free observation or prior agreement. Queries are sequential, not atomic; the selected descriptor reaches one service, not all independent processes. Missing lazy bindings and retained former-member bindings alone are healthy. Synthetic CLI tests separately prove mismatch reporting without modifying real workspace data; they also assert snapshot-only requests, unchanged fixture config, and omission of test credentials/private-content markers from output.
Cleanup and limits
- Successful harness cleanup removed exactly the run-owned fixtures
/tmp/opencode/ensemble-real-0fPNux,/tmp/opencode/ensemble-fake-qbiDCf, and/tmp/opencode/ensemble-fake-6Lqa60; existence checks confirmed all three absent. Both before and after the runs,tmux list-sessions -F '#S'reported no server on the default socket (expected exit 1). No broad session cleanup or real workspace deletion was performed. Unit/CLI fixtures use their ownfinallycleanup. No preserved failures remain. - Reviewed runtime guide, harness instructions, root instructions, and CI workflow. CI declares push/pull-request triggers, Node 26.12.1,
npm ci, andnpm run verify. Hosted CI was not triggered or executed by this local acceptance; only its equivalent local commands were run. Live suites intentionally remain outside CI/verify. This record adds no documentation test framework. npm ciand inspection ofnpm audit --jsonreported 28 advisories: 25 moderate, 3 critical. Critical package entries were@opentui/solid,solid-js, and transitiveseroval; audit reported no available fix for these entries. This is not a clean security audit or exploitability assessment. Nonpm audit fix, dependency upgrade, or compatibility-boundary change was attempted in this acceptance ticket.- No secrets, service descriptors, auth headers, real snapshots, conversation content, runtime memories, pane captures, or private runtime dumps are committed. No product regression was observed at the exercised seams; untested platforms/process topologies remain outside this evidence.