Files
pipelines/docs/install-review.md
T

52 lines
3.1 KiB
Markdown

# Installation review
Two independent reviewers examined installation conventions and stable OpenCode
compatibility. Both agreed that removing the V2 gate alone would hide real API
incompatibility rather than fix it.
## Findings addressed
- Installation mixed binary building with Docker provisioning, provider login,
private npm installation, service registration, and startup. It is now a thin
standard `go install ./cmd/...` operation, with no runtime checks or side effects.
- Go's repository import path did not match `go.mod`. The module now matches the
repository, enabling normal module installation (with `GOPRIVATE` for private access).
- Generic `server`/`tui` commands required renaming and a custom layout. They are
now `pipelines-server` and `pipelines-tui`, installed directly by Go.
- Runtime configuration was guessed relative to the binary, and a saved PATH
overrode the caller. Standard locations/explicit flags now select data; legacy
setup requires an explicit `PIPELINES_PREFIX`, and the caller's PATH is preserved.
- Native stable OpenCode has no equivalent to the V2 CLI/API contract. It now has
a separate HTTP adapter, using the existing executable/account, strict JSON
contracts, explicit models, translated scoped permissions, and an owned loopback
service. The existing V2 adapter is retained rather than pretending APIs match.
- Crash ownership must include the backend and native service. Additive metadata
records those references without rewriting immutable definitions or histories.
- The skill name did not match its directory. It is now `pipelines`. Installation
installs/updates the global skill; authoring references it directly instead of
preloading instructions or making preliminary session/API calls.
- Ownership persistence failure could leak created agent sessions. That failure
path cleans up its owned session. Authoring no longer pre-creates sessions.
## Deliberately removed from default installation
Private dependency installs, login prompts, mandatory notifications, automatic
LAN HTTP exposure, generated system bin symlinks, private binary prefixes, and a
second background supervisor. Configure optional services separately using normal
OS tools. The old managed installation helper remains only for explicit legacy
data/lifecycle access; it is not the standard installer.
Optional autostart is a separate explicit `pipelines service enable` step. It
uses the OS user manager directly, supports a
side-effect-free preview, and captures only documented environment settings.
Uninstallation refuses to remove binaries while its autostart definition remains;
disable the service first. Installation itself still registers or starts nothing.
## Verification limitations
The reviewer checked official stable OpenCode 1.18.35 in isolation and found V2
bridge URLs that return HTTP 200 **HTML**. The adapter rejects non-JSON responses.
No live inference or real model tool-permission enforcement was run. See
[verification scope](installation-verification.md); do not confuse successful
installation or stored permission rules with proven model execution.