IcyDate · Nov 6, 2026 · Nov 6, 2026 · Nov 6, 2026 · Nov 6, 2026 · Nov 6, 2026
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/README.md b/README.md
@@ -201,13 +201,31 @@ skipping bili commands entirely:
   without `dist/` and the bundle never loads) — same end state either way
   (pnpm into the profile, bundled patch layer mounted by dsh itself); remove
   through the same channel. See the dsh section below.
-- **opencode:** add the bare npm name to your real config's plugin list —
-  `"plugin": ["billion-context"]` (npm form only; a git checkout has no
-  published entry). The package publishes `exports["./server"]` →
-  `dist/agent/opencode-native.js`, so opencode loads it through its own
-  Npm.add machinery and the plugin self-spawns exactly like the
-  bili-installed form. Do the two things the bili installer would have done
-  for you too: set `"compaction": { "auto": false }` in the same config
+- **opencode:** easiest is `bili plugin install opencode` (it picks the
+  right entry form for your host version). Hand-install without bili (npm
+  form only; a git checkout has no published entry):
+  - **OpenCode 1.x** — add the bare npm name to your real config's plugin
+    list: `"plugin": ["billion-context"]`. The package publishes
+    `exports["./server"]` → `dist/agent/opencode-native.js`, so opencode
+    loads it through its own Npm.add machinery and the plugin self-spawns
+    exactly like the bili-installed form.
+  - **OpenCode 2.x** — the bare name does NOT work: 2.x resolves it through
+    the package `main` field (`dist/index.js`, the CLI — no plugin
+    definition), so the module load fails (#3976). Instead, put a one-line
+    re-export in a directory and point the config's `plugins` list at that
+    directory:
+
+    ```js
+    // <shim dir>/index.js
+    export { default } from "<abs path to the global install>/dist/agent/opencode-native.js";
+    ```
+
+    ```json
+    { "plugins": ["<shim dir>"] }
+    ```
+
+  Either generation: do the two things the bili installer would have done
+  for you too — set `"compaction": { "auto": false }` in the same config
   (otherwise OpenCode's native auto-compaction double-compresses) and keep a
   manual backup of the file first.
 - **claude:** this repository doubles as a Claude Code plugin marketplace —

diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -169,7 +169,20 @@ bili plugin remove <client>     # 卸载(dsh 经同一通道移除;配置快照
 客户端有自己的插件通道时,也可以原生安装、完全不用 bili 命令:
 
 - **dsh:** `dsh plugin --profile <name> add billion-context` 正是 `bili plugin install dsh` 按 profile 驱动的那条命令(仅 npm 形态;git checkout 没有已发布入口 —— 直接填 GitHub 地址装到的是没有 `dist/` 的源码,bundle 永远加载不出来)—— 两种走法终态一致(pnpm 装进 profile、patch 层由 dsh 自己挂载);经同一通道卸载。见下文 dsh 段。
-- **opencode:** 把裸 npm 包名直接写进你真实配置的插件列表 —— `"plugin": ["billion-context"]`(仅 npm 形态;git checkout 没有已发布入口)。包通过 `exports["./server"]` → `dist/agent/opencode-native.js` 暴露插件入口,opencode 用自己的 Npm.add 机制加载,插件自拉起的行为与 bili 安装的形态完全一致。另外要做两件 bili 安装器会替你做的事:在同一份配置里设 `"compaction": { "auto": false }`(否则 OpenCode 的原生自动压缩会双重压缩),并先手工备份该配置文件。
+- **opencode:** 最省事是 `bili plugin install opencode`(它会按宿主版本选对入口形态)。不用 bili 手工安装(仅 npm 形态;git checkout 没有已发布入口):
+  - **OpenCode 1.x** —— 把裸 npm 包名直接写进你真实配置的插件列表:`"plugin": ["billion-context"]`。包通过 `exports["./server"]` → `dist/agent/opencode-native.js` 暴露插件入口,opencode 用自己的 Npm.add 机制加载,插件自拉起的行为与 bili 安装的形态完全一致。
+  - **OpenCode 2.x** —— 裸包名**不行**:2.x 走包的 `main` 字段(`dist/index.js`,是 CLI、没有插件定义)解析,模块加载失败(#3976)。正确写法是在一个目录里放一行重导出,再把配置的 `plugins` 列表指向这个目录:
+
+    ```js
+    // <shim 目录>/index.js
+    export { default } from "<全局安装的绝对路径>/dist/agent/opencode-native.js";
+    ```
+
+    ```json
+    { "plugins": ["<shim 目录>"] }
+    ```
+
+  两个版本都要做两件 bili 安装器会替你做的事:在同一份配置里设 `"compaction": { "auto": false }`(否则 OpenCode 的原生自动压缩会双重压缩),并先手工备份该配置文件。
 - **claude:** 本仓库同时是一个 Claude Code 插件市场 —— `/plugin marketplace add ranxianglei/billion-context`,再 `/plugin install billion-context@billion-context`,然后运行 `/billion-context:bili-setup`(它会替你驱动 `bili plugin install claude` 并提示重启)。终态与 bili 安装器一致;插件自身不携带 hooks 或 MCP 条目,不会双重注册。
 
 pi / omp / kimi / claude 没有客户端侧通道 —— 它们的配置条目由 `bili plugin install <client>` 代写(kimi 的声明式 `kimi.plugin.json` + 注册记录、claude 的受管 settings 块等)。

diff --git a/announcements/remote.json b/announcements/remote.json
@@ -1,4 +1,27 @@
 {
   "v": 1,
-  "entries": []
+  "entries": [
+    {
+      "id": "dsh-live-compact-conflict",
+      "kind": "warning",
+      "tone": "warn",
+      "title": {
+        "en": "DSH: dsh-live-compact conflicts with bili compression",
+        "zh-CN": "DSH：dsh-live-compact 与 bili 压缩冲突"
+      },
+      "desc": {
+        "en": "If your dsh profile has the third-party plugin dsh-live-compact installed, it acts as a competing compaction engine that bili's compaction-disabling overlay cannot see — its checkpoints can land outside bili's knowledge and destroy the compression substrate (#5984). The conflict scan now flags it as a known conflict. If bili should own compression, remove the plugin and restart the profile: dsh plugin remove dsh-live-compact",
+        "zh-CN": "如果你的 dsh profile 安装了第三方插件 dsh-live-compact，它是一个 bili 压缩禁用 overlay 看不见的竞争压缩引擎——它的压缩 checkpoint 可能落在 bili 知识之外、摧毁压缩基底（#5984）。冲突扫描现在会把它标记为已知冲突。若要让 bili 持有压缩，请卸载插件并重启 profile：dsh plugin remove dsh-live-compact"
+      },
+      "hint": {
+        "en": "Source-level analysis in issue #5984: the plugin takes over dsh's stock compaction engine, and its row name never matches bili's overlay.",
+        "zh-CN": "源码级分析见 issue #5984：该插件顶替 dsh 的 stock 压缩引擎，其行名永远对不上 bili 的 overlay。"
+      },
+      "ctaLabel": "See #5984",
+      "ctaUrl": "https://github.com/ranxianglei/billion-context/issues/5984",
+      "dismiss": "persistent",
+      "priority": 70,
+      "publishedAt": "2026-11-11T10:40:00Z"
+    }
+  ]
 }
diff --git a/docs/architecture/pipeline.md b/docs/architecture/pipeline.md
@@ -1,6 +1,6 @@
 # Module: request pipeline (`src/server` + `src/loop`)
 
-> Part of the [architecture hub](../architecture.md) · 中文: [pipeline.zh-CN.md](./pipeline.zh-CN.md) · as of 2026-11-08, master
+> Part of the [architecture hub](../architecture.md) · 中文: [pipeline.zh-CN.md](./pipeline.zh-CN.md) · as of 2026-11-10, master
 
 ![Request pipeline module](./assets/pipeline.en.svg)
 (bitmap fallback: [pipeline.en.png](./assets/pipeline.en.png))
@@ -25,13 +25,13 @@ Every model-traffic request that reaches the proxy passes through this module: i
 
 **Unified loop (`src/loop`).** A protocol-neutral core with four wire adapters performs tool adjudication and the prose tag-echo filter (`tag-echo-filter.ts` — prose only, arguments untouched). This is where the two compression modes keep the same code path (KDD #7): plugin mode suppresses tool + nudge injection because the agent owns compression; proxy mode emits the `acp_summary` carrier, re-voiced as a user message so strict backends keep a stable prefix.
 
-**Egress.** `stream-*` rewrites the upstream SSE per wire (chunk framing, cache-control breakpoints #1637, `wire-body` trailing-user-turn append). Protocol headers (pf-*/envelope) never leave the proxy — the upstream hop-header list strips them.
+**Egress.** `stream-*` rewrites the upstream SSE per wire (chunk framing, cache-control breakpoints #1637, `wire-body` trailing-user-turn append). On the request side, a user-registerable `egressTransforms[]` pipeline (`src/egress-transforms.ts`, #6003) runs ESM plugins over every outbound model-request body after session processing and before re-sign/v1Wrap — fail-open per plugin, hot-reloadable via `/__bili/config/reload`, an exact no-op when unconfigured. Protocol headers (pf-*/envelope) never leave the proxy — the upstream hop-header list strips them.
 
 **Gates & recovery.** `preflight.ts` (hold grace, dead-end cooldown), `reasoning-guard` (signed payloads are never fold inputs), `request-body-budget` (receive/decode/send byte caps, availability over performance #3128), `content-encoding` (decompression-bomb guard, 413). Error shapes: `stream-error` (minimal SSE error + finish), `fake-completion` (opt-in retry hint), `degenerate-turn` / `degenerate-retry`, and `exit-matrix` (wire-exit × concerns, #588).
 
 ## Key entries
 
-`src/server/handle.ts` (triage) · `src/server/prepare-*.ts` (per-wire request prep) · `src/marker/` (inbound tag strip) · `src/loop/` (unified core + adapters) · `src/server/stream-*.ts` (per-wire egress) · `src/server/preflight.ts` · `src/server/exit-matrix.ts`
+`src/server/handle.ts` (triage) · `src/server/prepare-*.ts` (per-wire request prep) · `src/marker/` (inbound tag strip) · `src/loop/` (unified core + adapters) · `src/server/stream-*.ts` (per-wire egress) · `src/egress-transforms.ts` (user egress body-rewrite plugins, #6003) · `src/server/preflight.ts` · `src/server/exit-matrix.ts`
 
 ## Related
 

diff --git a/docs/architecture/pipeline.zh-CN.md b/docs/architecture/pipeline.zh-CN.md
@@ -1,6 +1,6 @@
 # 模块：请求管道（`src/server` + `src/loop`）
 
-> [架构总览](../architecture.zh-CN.md) 的一个模块 · English: [pipeline.md](./pipeline.md) · 截至 2026-11-08，master
+> [架构总览](../architecture.zh-CN.md) 的一个模块 · English: [pipeline.md](./pipeline.md) · 截至 2026-11-10，master
 
 ![请求管道模块](./assets/pipeline.zh-CN.svg)
 （位图备选：[pipeline.zh-CN.png](./assets/pipeline.zh-CN.png)）
@@ -25,13 +25,13 @@
 
 **统一 loop（`src/loop`）。** 协议中立核心 + 4 个 wire 适配器，做工具裁决与散文 tag-echo 过滤（`tag-echo-filter.ts`——只滤散文、参数不动）。两种压缩模式在这里共用同一条代码路径（KDD #7）：plugin 模式抑制 tool + nudge 注入（agent 自己压）；proxy 模式发 `acp_summary` 载体、改口为 user 消息，让严格后端保持前缀稳定。
 
-**出站。** `stream-*` 按 wire 改写上游 SSE（块框架、cache-control 断点 #1637、`wire-body` 尾 user 回合补位）。协议头（pf-*/信封）永不出代理——上游 hop 头白名单剥掉它们。
+**出站。** `stream-*` 按 wire 改写上游 SSE（块框架、cache-control 断点 #1637、`wire-body` 尾 user 回合补位）。请求侧另有用户可注册的 `egressTransforms[]` 管道（`src/egress-transforms.ts`，#6003）：ESM 插件在所有会话处理之后、re-sign/v1Wrap 之前改写每个出站模型请求体——逐插件 fail-open，可经 `/__bili/config/reload` 热重载，未配置时严格 no-op。协议头（pf-*/信封）永不出代理——上游 hop 头白名单剥掉它们。
 
 **闸门与恢复。** `preflight.ts`（hold 宽限、死路冷却）、`reasoning-guard`（签名载荷永不进折叠输入）、`request-body-budget`（收/解/发字节预算，可用性大于性能 #3128）、`content-encoding`（解压炸弹守卫，413）。错误形态：`stream-error`（最小 SSE 错误+收尾）、`fake-completion`（可选重试提示）、`degenerate-turn` / `degenerate-retry`、`exit-matrix`（wire 出口 × 关注点，#588）。
 
 ## 关键入口
 
-`src/server/handle.ts`（分诊） · `src/server/prepare-*.ts`（按 wire 请求准备） · `src/marker/`（入站剥标签） · `src/loop/`（统一核心+适配器） · `src/server/stream-*.ts`（按 wire 出站） · `src/server/preflight.ts` · `src/server/exit-matrix.ts`
+`src/server/handle.ts`（分诊） · `src/server/prepare-*.ts`（按 wire 请求准备） · `src/marker/`（入站剥标签） · `src/loop/`（统一核心+适配器） · `src/server/stream-*.ts`（按 wire 出站） · `src/egress-transforms.ts`（用户出站体改写插件，#6003） · `src/server/preflight.ts` · `src/server/exit-matrix.ts`
 
 ## 相关
 

diff --git a/docs/architecture/webui.md b/docs/architecture/webui.md
@@ -21,7 +21,7 @@ Everything a human sees about the proxy: the session browser, logs, config, upda
 
 **Data sources.** The live session pool plus storage rows (tier tree, #3917); `acp_status` ranges/nudge are recomputed LIVE per render, never cached stale (`acp-status.ts`); the cache ledger economics (`cache-ledger.ts`, #1536); billing at USD prices with the payback view (#4899); notice dismissal receipts in unified storage (kv_store namespace `notices`).
 
-**Render.** Server-rendered HTML shell (`page.ts`) + one JS bundle (`client.ts`) + styles; `i18n.ts` carries the zh-CN/en message tables (dead keys are test-guarded); `markdown.ts` is escape-safe; `report.ts` builds dependency-free MD+SVG session reports; `diagnostics.ts` produces the paste-ready blob for issue reports (#3040).
+**Render.** Server-rendered HTML shell (`page.ts`) + one JS bundle (`client.ts`) + styles; `i18n.ts` carries the zh-CN/en message tables (dead keys are test-guarded); `mdrender.ts` is the single escape-first Markdown + syntax-highlight core (hand-rolled lexers for json/diff/js/ts/py/sh, GitHub light+dark palettes, zero runtime deps — inlined into the browser IIFE via `.toString()` exactly like the JSONC helpers), and `markdown.ts` wraps it for the server side (blog articles + handoff fallback); `report.ts` builds dependency-free MD+SVG session reports; `diagnostics.ts` produces the paste-ready blob for issue reports (#3040).
 
 **Notices.** `mergedNotices()` (`src/announcements.ts`) merges the three sources; the remote feed is this repo's `announcements/remote.json`, polled on the ~3-minute watcher cadence, fail-open (fetch problems keep the last-known-good snapshot; model traffic is never affected); builtin notices are dead-key-guarded by `tests/notice-registry.test.ts`.
 

diff --git a/docs/architecture/webui.zh-CN.md b/docs/architecture/webui.zh-CN.md
@@ -21,7 +21,7 @@
 
 **数据源。** 活会话池 + 存储行（层树，#3917）；`acp_status` 的 ranges/nudge 每次渲染**现算**、从不缓存陈旧（`acp-status.ts`）；缓存账本经济性（`cache-ledger.ts`，#1536）；USD 价格计费与回本视图（#4899）；通告关闭回执在统一存储（kv_store namespace `notices`）。
 
-**渲染。** 服务端渲染 HTML 壳（`page.ts`）+ 一个 JS 包（`client.ts`）+ 样式；`i18n.ts` 承载 zh-CN/en 文案表（死键有测试守卫）；`markdown.ts` 转义安全；`report.ts` 生成零依赖 MD+SVG 会话报告；`diagnostics.ts` 产出可粘贴的诊断块供报 issue（#3040）。
+**渲染。** 服务端渲染 HTML 壳（`page.ts`）+ 一个 JS 包（`client.ts`）+ 样式；`i18n.ts` 承载 zh-CN/en 文案表（死键有测试守卫）；`mdrender.ts` 是唯一的转义优先 Markdown + 手写语法高亮核心（json/diff/js/ts/py/sh 词法器，GitHub 明/暗双配色，零运行时依赖——与 JSONC 辅助函数完全相同的方式经 `.toString()` 内联进浏览器 IIFE），`markdown.ts` 在服务端（博客文章 + 交接文档 fallback）包一层；`report.ts` 生成零依赖 MD+SVG 会话报告；`diagnostics.ts` 产出可粘贴的诊断块供报 issue（#3040）。
 
 **通告。** `mergedNotices()`（`src/announcements.ts`）合并三个源；远端 feed 是本仓 `announcements/remote.json`，按 ~3 分钟 watcher 节拍轮询、fail-open（取不到就留最后已知良好快照；模型流量永不受影响）；内置通告由 `tests/notice-registry.test.ts` 死键守卫。