Skip to content

Clean-install release candidate via opencode plugin add ​

Status: FAIL for 0.1.0-rc.1 — install and server PASS; TUI load blocked Date: 2026-11-16 Ticket: #270 Parent spec: #268 Built-package follow-up: #279 Branch: ticket/270-clean-install

Follow-up: the built 0.1.0-rc.2 package in the #279 record passes the installed TUI route, /ensemble command, six server tools, and plugin list source/version. The TUI criterion in this record is superseded by that pass; the source-package failure below stays as the evidence that motivated the built package.

Scope ​

This record covers the 0.1.0-rc.1 clean-install proof only: packing the candidate, serving it from a loopback-only npm registry, installing it with opencode plugin add into an isolated OpenCode 2.2.7 host, and checking the installed package source, server tools, and TUI route/command. No public npm publish, real credential, workspace link, or repository plugin path is used. The OpenCode configuration, HOME, XDG directories, project, and mock agent are temporary and were not the user's global configuration.

Environment ​

ItemValue
HostLinux 6.12.116+deb13-amd64
Node26.12.1
npm12.2.1
OpenCode CLI2.2.7
tmux3.5a
Package@heyimteee/ensemble@0.1.0-rc.1
RC channelEphemeral 127.0.0.1 npm registry serving the packed tarball

The package version is now 0.1.0-rc.1; package-lock.json records the same version. The README and implementation notes call the release candidate unpublished, not a released version.

Command ​

sh
npm run test:install:rc

This runs scripts/live-install-check.sh. The script packs the candidate, starts scripts/lib/local-npm-registry.mjs on a loopback port, writes an isolated .npmrc, runs opencode plugin add @heyimteee/ensemble@0.1.0-rc.1, checks opencode plugin list, starts the isolated fake provider and server, drives one host turn, then starts the isolated TUI and opens /ensemble. src/v2/local-npm-registry.test.ts covers the loopback registry's packument and tarball seam inside npm run verify, so a route regression cannot silently break the installer integrity check.

Results ​

CheckResultEvidence
npm packPASS@heyimteee/ensemble@0.1.0-rc.1; 123 files; 547,814-byte tarball
Local registry installPASSplugin add recorded @heyimteee/ensemble@0.1.0-rc.1 in the isolated config
opencode plugin listPASSensemble.v2 0.1.0-rc.1 @heyimteee/ensemble@0.1.0-rc.1
Server plugin loadPASSPackage source active; entrypoint under the isolated package cache
Server toolsPASSOne host turn reported ensembleToolCount: 6, the native surface
TUI plugin loadFAILPlugin load error; /ensemble and the Ensemble route never load
No workspace linkPASSConfig carries only the package spec; the host opened the mock project only
npm run verifyPASSStrict typecheck; 2,052 tests, 0 failed/skipped
npm run docs:checkPASSContract v7; OpenCode 2.2.6/2.2.7; Node >=22.23.4

opencode plugin list:

text
ID           VERSION     SOURCE
ensemble.v2  0.1.0-rc.1  @heyimteee/ensemble@0.1.0-rc.1

Server plugin record from /api/plugin (paths omitted):

json
{"id":"ensemble.v2","source":{"type":"package","target":"@heyimteee/ensemble@0.1.0-rc.1","version":"0.1.0-rc.1"},"features":{"server":true,"tui":true,"rpc":true},"state":{"status":"active"}}

Server load evidence from the isolated host log:

text
msg="loading plugin" id=@heyimteee/ensemble@0.1.0-rc.1
entrypoint=file://<isolated-cache>/cache/opencode/npm/@heyimteee/ensemble@0.1.0-rc.1/<install>/node_modules/@heyimteee/ensemble/src/v2/server.ts

The features.tui flag is the package declaration; it is not proof that the TUI entry loaded. The load failure below overrides it.

TUI failure ​

The isolated TUI shows Plugin failed: @heyimteee/ensemble@0.1.0-rc.1, and its log reports:

text
plugin operation failed ... stage=load
error="Cannot find package 'react' imported from
<isolated-cache>/cache/opencode/npm/@heyimteee/ensemble@0.1.0-rc.1/<install>/node_modules/@heyimteee/ensemble/src/v2/tui/index.tsx"

The installed source package has no tsconfig.json, so the host loader uses the classic JSX runtime and asks for react. In a throwaway copy of the installed package, adding @jsxImportSource @opentui/solid to the three TSX entries moved the failure to:

text
error="Cannot find package '@opentui/solid' imported from
<isolated-cache>/.../src/v2/tui/index.tsx"

The optional peers @opentui/core, @opentui/solid, and solid-js are not in the plugin cache. The source package therefore cannot load its TUI part from the real install location even though the same files load from a checkout with the repository tsconfig.json and node_modules.

Per the ticket, the source package was not replaced silently with a built package and no success is claimed. Follow-up #279 covers the built server/TUI artifact, bundled or declared TUI runtime dependencies, a runtime-only pack allowlist for built files, and a fresh 0.1.0-rc.2 clean-install proof.

Skips ​

  • Public npm publish is intentionally out of scope; no registry credential was used.
  • macOS/Herdr verification remains ticket #277.
  • The TUI acceptance criterion in #270 remains open until #279 lands.

Released under the MIT License.