feat: opencode v2 local compression kernel — mode parity with `bili pi` (compress executes inside opencode, no proxy)

[ranxianglei]

Background

PR #824 delivered opencode v2 support; #850/#885 added the proxy / launcher / native-spawn modes plus the /acp command. But bili pi users get a fundamentally better shape: the agent-side plugin owns compression locally — no proxy hop, no BILLION_CONTEXT_PROXY, wire traffic goes straight to the real upstream. opencode v2 had no equivalent (its "native" mode still self-spawns a proxy).

User request (paraphrased from session): "bili pi is what we want — bili opencode is the remote mode. pi implements modes 1 (proxy) + 2 (launcher); make opencode match, with pure-local mode 3." Reference for the pure-local shape: https://github.com/ranxianglei/opencode-acp

What this adds

src/agent/opencode-local.ts — an opencode v2 plugin that runs the acp-kernel compression pipeline IN-PROCESS:

• session registry keyed by conversation id, session.hook rebuilds the wire view through the kernel (folded messages, acp tags on text parts)
• chat.params.tools injects the kernel's compress/decompress/acp_status tool set; chat.parameters enforces the compress system prompt
• tool execution goes through the kernel (executeTool), so acp_status renders the same panel as /acp
• No proxy, no MITM, no env vars: the user's model config is untouched; context compression happens between opencode and the model, invisible on the wire except tags

Verification done

• unit tests (tests/opencode-local.test.ts, 11 tests) + full suite 1673 pass
• Docker-isolated E2E with real opencode v2 + local sglang upstream: 4 postures (proxy / launcher / native-spawn / pure local) all green
• compression stress test in-container: model read ~200K tokens of real source, self-triggered compress 7 times (105K folded), refs strictly monotonic, no id reuse, two successful recall-from-summary answers, no tag leakage

Fixes ride on the same branch and are recorded in #906 (abort-guard, system-array push).

[ranxianglei]

PR: #909 (stacked on #850, same as #885)

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到。正在拉取 2026-09-17_opencode-v2-local-kernel（#909，stacked on #850）做本地核对：代码 vs issue 验收标准、typecheck / 全量测试 / build、CI 状态。结论稍后回帖。

[ranxianglei]

🤖 Powered by ework · qwen3.8-27b

PR #909 已拉取并本地全量核对完毕（分支 2026-09-17_opencode-v2-local-kernel@22c7361，stacked on #850）。

本地 preflight（全绿）

• typecheck ✓；npm test：1675 = 1673 pass / 0 fail / 2 skip（与 PR 声明一致）；build ✓，dist/agent/opencode-local.js 正常产出（自包含 bundle）
• CI：head commit 上 1 个 check-run（real codex e2e vs fake upstream）completed/success；stacked 分支上没有单独的 typecheck/test CI run，已由本地补齐覆盖

验收标准逐条核对（代码层面全部落实）

• src/agent/opencode-local.ts：kernel 进程内运行；session registry 与 proxy 共用同一 registry + StateStore（后续 proxy attach 可无缝接管）；wire seam session.hook("context") 原地改写投影；工具经 tool.transform 注入 compress/decompress/search_context/acp_status(+absorb)，执行走与 proxy 完全相同的共享机制（applyRanges / resolveDecompress / executeSearchContext / handleAcpStatus / executeAbsorb）
• acp_status 默认先渲染面板再附结构化报告（与 /acp 同面板），hostLabel 身份一致 ✓
• plugin-mode carrier 规则正确（stripCarriedSummaries：block 的 compressCallId 已被 view 中 tool call 携带时丢弃重复 acp_summary）；nudge 为临时注入不落盘；echo tag 在 ingest 时剥离；native compaction → markCompactionBoundary + archive；kill switch BILLION_CONTEXT_PLUGIN=0
• tsup entry 已加新文件；bili plugin install opencode-local 切换 plugin dir 入口到 dist/agent/opencode-local.js、跳过 MCP shell、status 显示 "installed (local kernel)"
• 11 个单测覆盖 issue 列的行为（含 v2 no-id tool-result 回归、完整 compress 生命周期、内部 agent 跳过、tag echo 剥离）；loop/core.ts abort guard 的 signal 是请求级 AbortSignal 参数，与既有 retry guard（L255/290/364/403/678）同模式，undefined 时行为不变 ✓

合并前需要处理的问题

1. ⚠️ 误删无关文件（必须恢复）：commit e59776b 删掉了 scripts/update-codex-models-snapshot.mjs、scripts/update-registry-snapshot.mjs、tools/analyze-dumps.mjs —— 三个文件在 master 上都在、与本 PR 目的无关、commit message 和 CHANGELOG 均未提及，疑似 history rewrite 时的连带损失。合并前需从 master 恢复这三个文件。
2. 与 issue 验收标准的交付方式偏差（需你拍板）：issue 写的是"opencode launcher 支持纯 local 第三 posture（env-var based，同 pi）" + "README opencode 节补 local 条目 + launcher 命令"；实际交付是 bili plugin install opencode-local（无 env var、launcher.ts 零改动），且 README 完全没动。功能上 mode parity 已达成，但用户没有任何文档入口发现 local mode。建议至少补 README（含最低 opencode v2 版本要求，见下条）；是否另加 launcher --local/env-var posture 由你定。
3. 版本悬崖需文档化：opencode-local.ts:15 注释写明 context hook seam "probed live on 2.0.4"，而 README L269 / opencode-v2.ts 文档的是 2.0.1+2.0.3 proven。若 session.hook("context") 仅 ≥2.0.4 支持，在 2.0.3 上装 local mode 会静默 inert（optional chaining 吞掉注册失败，无任何报错）。README 应明确 local mode 最低版本，最好 hook 注册失败时给一条显式 warning。

小问题（不阻塞，可顺手修）

• src/compress-tool.ts:133 LOCAL_TAG_FORMAT_NOTE 字符串字面量用了裸 <acp> 字符，违反仓库 hex-escape 约定（\x3c/\x3e）——将来编辑该行时有被编辑工具静默剥掉的真实风险
• src/plugin-install.ts ~L459：无花括号 else 后悬空注释再接 try，风格问题
• tests/opencode-local.test.ts L165-166/170-171/182/196-199/203 缩进错乱
• 非阻塞 nit：system prompt 的 replace-style 防住了跨请求累积，但若 host 在同一请求内对同一 event object 双触发 hook，prompt 仍会叠一份（A→A+p→A+p+p）；可给注入的 system part 打 marker field、append 前先 filter 彻底幂等

说明：以上发现按 repro/位置报在本线程，没有直接往 PR 分支推 commit——有并行的 #909 会话正在同一分支上工作，避免推送冲突；如需我代修第 1 项（恢复三个文件），说一声即可。

---

一句话摘要：#909 实现质量高、本地 typecheck/测试(1673 pass)/build 全绿且与验收标准逐条吻合；但发现误删了 3 个无关维护脚本（合并前必须恢复）、README/launcher 交付方式与 issue 规格有偏差、local mode 存在未文档化的 2.0.4 版本悬崖——建议补齐这三点后合并，其余为小样式问题。

[ranxianglei]

Closing as not-planned — decision reversed after real-session testing.

The in-process local kernel (PR #909) shipped a working compress/acp_status/panel surface, but forensics on real sessions (opencode.db) showed model-forged <acp …> tags leaking into the TUI and persisted history: an in-process host has no stream seam, so it cannot do the stream-time echo stripping that protects every other mode (loop/tag-echo-filter.ts, #206/#717).

Decision: opencode v2 aligns on the same architecture as bili pi — self-spawned local proxy + per-request URL rewrite via the v2 session.hook("http.request") seam. That already exists on master as src/agent/opencode-native.ts (#885), which keeps the wire layer (echo stripping, plugin-mode headers, forwardTool) and therefore does not leak.

The mode-independent loop bug found along the way (client abort miscounted as weak overflow) is re-landed on master as #910.