Be honest about opencode: feature is upstream-pending, not just unshipped

opencode 1.14.48 has no plugin-side statusline hook. I enumerated the
full event surface in @opencode-ai/plugin's dist/index.d.ts to be sure:
chat.{headers,message,params}, command.execute.before, experimental.*
(messages/system transform, compaction, text), permission.ask,
shell.env, tool.{definition,execute.before,execute.after}. All
behavioral hooks. No render surface. tui.showToast is transient.
chat.message injection works but costs context tokens — exactly what
upstream issue anomalyco/opencode#8619 was filed to avoid.

So opencode is upstream-blocked, not waiting on us. The installer was
printing 'opencode wired' on success, which misled users into thinking
the statusline would appear. It now prints a clear 'pending upstream'
warning with the issue link. Config keys are still written
speculatively so a future upstream ship auto-activates without
re-install.

README + AGENTS.md status rows updated to match.

Author: kinncj

AGENTS.md

@@ -41,7 +41,7 @@ Be honest in user-facing docs about which of these installers is wiring somethin
 |--------------|-----------------------------|-------|
 | Claude Code  | ✓ shipped                   | `settings.json.statusLine = {type:"command", command, padding}` — official. |
 | Copilot CLI  | ✓ shipped                   | Config lives in `~/.copilot/config.json`. The neighbouring `settings.json` is read for unrelated user prefs and a misleading header comment ("User settings belong in settings.json") — its `statusLine` key is **ignored**. Requires the experimental feature gate, which we persist with `"experimental": true` in the same file (equivalent to launching `copilot --experimental`). The `command` path must be **absolute** (no `~`, no env var expansion) and the script must be executable with a valid shebang. config.json starts with `//` comment lines that jq can't parse — installer strips them before merging. Verified against Copilot CLI 1.0.46 and griches/copilot-hud's setup skill. |
-| OpenCode     | ⚠ not shipped               | Feature request open at anomalyco/opencode#8619. Our installer writes `.statusline` and `.experimental.statusline` keys speculatively so a future ship lands without a re-install. Today the runtime ignores them; the AGENTS.md drop is what carries weight. |
+| OpenCode     | ✗ upstream-pending          | Verified against opencode 1.14.48: no plugin-side statusline hook exists. Full event surface from `@opencode-ai/plugin` 1.14.48's `dist/index.d.ts`: `chat.{headers,message,params}`, `command.execute.before`, `experimental.{chat.messages.transform,chat.system.transform,compaction.autocontinue,session.compacting,text.complete}`, `permission.ask`, `shell.env`, `tool.{definition,execute.before,execute.after}`. All behavioral, none persist UI. Tracking: anomalyco/opencode#8619 (still open). Our installer writes `.statusline.command` and `.experimental.statusline.command` keys speculatively so a future upstream ship lands without re-install — until then the runtime ignores them and we print a "pending upstream" warning. |
 | Pi           | ✓ shipped (native extension)| `~/.pi/agent/extensions/kinncj-statusline/` — an `ExtensionFactory` (`statusline.mjs`) that subscribes to `session_start`/`turn_end`/`tool_execution_end`/`agent_end`/`model_select`, synthesizes a Claude-shaped payload from `ctx.cwd` + `ctx.model` + `ctx.getContextUsage()`, execs the sibling `statusline.sh`, and renders the stdout as a multi-line widget under the editor via `ctx.ui.setWidget(key, lines, {placement:"belowEditor"})`. Auto-discovered by Pi from `<agentDir>/extensions/` — no settings to edit. Renders below Pi's native footer rather than replacing it, so both lines coexist. Verified against `@earendil-works/pi-coding-agent` 0.73.1 (formerly `@mariozechner/pi-coding-agent`). |
 | Hermes       | ✗ no scriptable statusline  | Built-in TUI; only `display.tui_status_indicator` is tunable. AGENTS.md + skill only. |
 

CHANGELOG.md

@@ -7,6 +7,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.3] - 2026-05-13
+
+### Changed
+- `installers/opencode.sh` no longer claims "opencode wired" on success.
+  OpenCode 1.14.48 has no statusline plugin hook — verified by enumerating
+  the full event surface in `@opencode-ai/plugin`'s `dist/index.d.ts`
+  (`chat.*`, `tool.execute.*`, `permission.ask`, etc. — all behavioral,
+  none render). The installer still writes the proposed config keys
+  speculatively so a future upstream ship (tracking
+  anomalyco/opencode#8619) auto-activates, but it now prints a clear
+  "pending upstream" warning and links the issue so users aren't
+  confused when their built-in footer keeps rendering.
+- README and AGENTS.md updated to reflect the real opencode status: not
+  pending-implementation, but pending-upstream — there's no plugin-side
+  workaround that avoids burning context tokens.
+
 ## [0.2.2] - 2026-05-12
 
 ### Fixed
@@ -123,7 +139,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   launch. Cleans up the dead `statusLine`/`footer` keys older installer
   versions left in `settings.json`. Verified against Copilot CLI 1.0.46.
 
-[Unreleased]: https://github.com/kinncj/statusline/compare/v0.2.2...HEAD
+[Unreleased]: https://github.com/kinncj/statusline/compare/v0.2.3...HEAD
+[0.2.3]: https://github.com/kinncj/statusline/releases/tag/v0.2.3
 [0.2.2]: https://github.com/kinncj/statusline/releases/tag/v0.2.2
 [0.2.1]: https://github.com/kinncj/statusline/releases/tag/v0.2.1
 [0.2.0]: https://github.com/kinncj/statusline/releases/tag/v0.2.0

README.md

@@ -60,14 +60,14 @@ The installer renders a boxed, animated TUI by default. Animations auto-disable
 |----------------------------|:----------:|:---------:|------------------------------------------|
 | **Claude Code**            | ✓          | ✓         | `~/.claude/settings.json`                |
 | **GitHub Copilot CLI**     | ✓          | ✓         | `~/.copilot/config.json` (requires `experimental: true`, which the installer sets) |
-| **OpenCode**               | ⚠ pending  | ✓         | `~/.config/opencode/opencode.json` (FR: anomalyco/opencode#8619) |
+| **OpenCode**               | ✗ upstream | ✓         | `~/.config/opencode/opencode.json` — feature not yet shipped by opencode; tracked at [anomalyco/opencode#8619](https://github.com/anomalyco/opencode/issues/8619). Installer writes the proposed schema speculatively so a future ship auto-activates; today, opencode's built-in footer is what renders. |
 | **Pi (pi.dev)**            | ✓          | ✓         | `~/.pi/agent/extensions/kinncj-statusline/` (native Pi extension; auto-discovered, no settings to edit) |
 | **Hermes (nousresearch)**  | —          | ✓ + skill | `~/.hermes/` (full TUI, no script hook)  |
 
 - **Pi** is wired via a native extension (`extensions/pi/statusline.mjs`) that Pi auto-discovers from `~/.pi/agent/extensions/`. The extension bridges Pi's session context (`ctx.cwd`, `ctx.model`, `ctx.getContextUsage()`) into the same `statusline.sh` we use everywhere else and renders the output as a widget below the editor. Pi's own native footer stays as-is, so you get both lines.
 - **Hermes** ships a fixed built-in TUI with skin-level theming only and no extension point. We install AGENTS.md + the `statusline-edit` skill so the repo's instructions travel with you.
 
-**OpenCode** doesn't ship the hook yet — the installer writes the two proposed key shapes speculatively so it'll work as soon as anomalyco/opencode#8619 ships.
+**OpenCode** has no statusline hook in 1.14.48 — verified against the binary's full plugin event list (`chat.*`, `tool.execute.*`, `permission.ask`, etc., all behavioral, none render). The feature is tracked upstream at [anomalyco/opencode#8619](https://github.com/anomalyco/opencode/issues/8619) — still open. The installer prints a clear "pending upstream" warning, drops our `statusline.sh` into the config dir, and writes both proposed key shapes (`statusline.command` and `experimental.statusline.command`) into `opencode.json` so whichever the upstream merge picks will auto-activate without a re-install. Until then, opencode's built-in footer is what you see and our script sits idle. Building a plugin against today's API doesn't help — the only display surface is `chat.message`, which costs context tokens (the exact problem #8619 was filed to fix).
 
 ## What's in line 2
 

installers/opencode.sh

@@ -35,5 +35,8 @@ json_set "$SETTINGS" \
         "experimental": (.experimental // {} | . + {"statusline": {"command": $cmd}})
     }'
 
-ok "opencode wired"
-info "restart opencode to pick up the new statusline"
+warn "opencode upstream has NOT shipped a statusline hook yet"
+info "tracking issue: https://github.com/anomalyco/opencode/issues/8619"
+info "we wrote the proposed config keys speculatively so a future ship auto-activates"
+info "today, opencode renders its built-in footer and ignores these keys"
+ok "opencode config written (statusline pending upstream)"