@andares/pi-toolkits 0.9.7 → 0.9.8

package/README.md

@@ -10,12 +10,12 @@
 [![Pi package gallery](https://img.shields.io/badge/pi.dev-package%20gallery-6f42c1)](https://pi.dev/packages/@andares/pi-toolkits)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Package Manager](https://img.shields.io/badge/package%20manager-pnpm-orange?logo=pnpm)](https://pnpm.io)
-[![pi >= 1.0](https://img.shields.io/badge/pi-%3E%3D1.0.0%20%3C1.12.0-blueviolet)](https://github.com/earendil-works/pi)
+[![pi >= 0.99](https://img.shields.io/badge/pi-%3E%3D0.99.0-blueviolet)](https://github.com/earendil-works/pi)
 [![GitHub](https://img.shields.io/badge/github-andares%2Fpi--toolkits-181717?logo=github)](https://github.com/andares/pi-toolkits)
 
 In a nutshell: seven ready-to-use capabilities — **read-only consult mode** `ask`, **session-scoped boundary permission** `ask-perm`, **model favorites** `favorites`, **prompt stash** `stash`, **third-party code review** `third-review`, **dedicated compaction model** `compact-model` and **session startup automation** `autostart` — with more to come.
 
-**Requirements**: pi `>=1.0.0 <1.12.0` — the four most recently released minor lines (1.0.x / 1.1.x / 1.2.x / 1.3.x) are supported best-effort, and the upper bound encodes the forward probe: on every host release we check up to **8 minor lines** beyond the newest one (now 1.4 … 1.11) and never claim past that cap. **Measured natural compatibility: 1.3.0** (the newest release at the time of writing — nothing newer exists to probe yet). A single command, `pnpm check:compat`, derives that version set from the registry and runs, per version, in a sandbox under the system temp dir with the whole `@earendil-works/*` family pinned to the version under test: install → `tsc --noEmit` → full test suite → keybinding audit → hash-compare of the host `dist` files this package patches or mirrors. Results over 1.0.0 → 1.3.0 (all 8 published versions): typecheck, 473 tests and the keybinding audit pass on every one; the tracked host files drift only in `core/agent-session.js` (1.3.0 changed the tool-restore path; `cycleModel` untouched), `core/keybindings.js` and `core/compaction/utils.js` (both changed in 1.2.0, table semantics for our keys unchanged), and `extensions/types.d.ts` (additive) — `ModelSelectorComponent`, `core/compaction/compaction.js` and `core/usage-totals.js` are byte-identical across the whole window. Smoke-loading on real pi 1.3.0 produces no warnings. Note: pi ≥ 0.99 hosts require host-provided packages to be declared in `peerDependencies` with a `"*"` range — `@earendil-works/pi-tui` and `typebox` (the `scratchpad` tool builds a TypeBox schema) are declared that way; an installed copy in `dependencies` would make pi warn.
+**Requirements**: pi `>=0.99.0`. Every published pi release from 0.99.0 through 1.4.0 has been verified with the full gate (install → `tsc --noEmit` → full test suite → keybinding audit → hash compare of the host files this package patches), each in a sandbox with the whole `@earendil-works/*` family pinned to the version under test. Newer releases are verified as they ship and the floor moves only when the measurement says so; `pnpm check:compat` reproduces the result. Note: pi ≥ 0.99 hosts require host-provided packages to be declared in `peerDependencies` with a `"*"` range — `@earendil-works/pi-tui` and `typebox` (the `scratchpad` tool builds a TypeBox schema) are declared that way; an installed copy in `dependencies` would make pi warn.
 
 ---
 
@@ -255,11 +255,11 @@ pi's `/compact` and auto-compact summarize the context **with the current sessio
 | auto-compact threshold reached | summarized by the compaction model |
 | context overflow recovery | summarized by the compaction model, retry behavior unchanged |
 
-**Parts that are identical to pi's built-in behavior after takeover** (the built-in implementation is mirrored verbatim — copied from 0.87.1, byte-identical across every published version of the supported window, 1.0.0 → 1.3.0 — and only the executing model changes; the conversation serializer itself is imported from the host, so it follows whatever the running host does, e.g. 1.2.0 stops feeding assistant thinking back into the summarization request):
+**Parts that are identical to pi's built-in behavior after takeover** (the built-in implementation is mirrored verbatim — copied from 0.87.1, byte-identical across 1.1.0 → 1.4.0 apart from the two 1.4.0 fixes adopted here: summaries request the model's output limit instead of a fixed fraction of `reserveTokens`, and `/compact <instructions>` also reaches the split-turn prefix — and only the executing model changes; the conversation serializer itself is imported from the host, so it follows whatever the running host does, e.g. 1.2.0 stops feeding assistant thinking back into the summarization request):
 
 - **Summary format** — the structured Goal / Progress / Key Decisions checkpoint; when a summary already exists, the iterative-update prompt is used so information carries over instead of being lost
 - **Split behavior** — the `keepRecentTokens` retention policy, and `firstKeptEntryId` / `tokensBefore` passed back unchanged
-- **Output budget** — the same formula as the built-in (history segment 0.8×, split-prefix segment 0.5× of `reserveTokens`, then capped by the model's max output)
+- **Output budget** — summaries ask for the model's own output limit, exactly like the built-in since 1.4.0 (#9512: a fixed 0.8×/0.5× `reserveTokens` cap made long reasoning fail the summary with "generation hit the token cap"); `reserveTokens` only decides when compaction starts
 - **File-list tail** — `<read-files>` / `<modified-files>` tags are appended to the summary as usual, with details maintained in the same shape
 - **Usage accounting** — the compaction model's tokens/cost are counted in the session statistics
 - **Cancellable** — `Esc` during compaction cancels cleanly (the signal is passed through to the underlying call)
@@ -336,7 +336,7 @@ An **identical command line** declared by both sources runs once: a duplicate is
 
 **Key constraint: extension commands only**. Commands registered via `registerCommand` such as `/add-dir` (pi-add-dir) and `/cd` (pi-cd) work; built-in commands (`/compact`, `/reload`, `/resume`, …) are dispatched in the TUI layer and cannot be triggered from the extension layer; skill commands (`/skill:name`) are an expansion mechanism rather than an execution mechanism. The target extension you depend on (e.g. pi-add-dir) must be installed first.
 
-> **Implementation notes**: execution uses `sendUserMessage(cmd, { expandPromptTemplates: true })` — that option routes `/cmd args` into command dispatch instead of the model prompt path (the wrapper defaults to `false`; `sendUserMessage` and `_tryExecuteExtensionCommand` are byte-identical across 1.0.0–1.3.0, see the host-compatibility discipline in AGENTS.md). Pre-validation uses `pi.getCommands()` (accepting only `source: "extension"`). Depends on `smol-toml` (zero-dependency, ~10KB, TOML 1.0).
+> **Implementation notes**: execution uses `sendUserMessage(cmd, { expandPromptTemplates: true })` — that option routes `/cmd args` into command dispatch instead of the model prompt path (the wrapper defaults to `false`; `sendUserMessage` and `_tryExecuteExtensionCommand` are byte-identical across 1.1.0–1.4.0, see the host-compatibility discipline in AGENTS.md). Pre-validation uses `pi.getCommands()` (accepting only `source: "extension"`). Depends on `smol-toml` (zero-dependency, ~10KB, TOML 1.0).
 
 ---
 
@@ -352,7 +352,7 @@ pnpm typecheck    # tsc --noEmit
 pnpm test         # vitest (all feature unit tests)
 
 pnpm check:keybindings   # audit this plugin's keys against the host's own dispatch table
-pnpm check:compat        # verify the declared pi range: last 4 minor lines + 8-line forward probe
+pnpm check:compat        # mandatory 4-line window + backward probe (4 more lines) → public floor
 ```
 
 ### Project structure
@@ -414,7 +414,7 @@ PRs and issues welcome. A few conventions:
 - **Built-in patches** (favorites) must stay **version-guarded and idempotent** — verify the target prototype members exist before patching, guard against double-apply, degrade with a `console.warn` instead of breaking the extension
 - **Built-in prompt sync** (compact) — the summarization prompts in `src/features/compact/prompt.ts` are copied verbatim from pi's built-in compaction; when upgrading the pi dependency, diff `dist/core/compaction/compaction.js` (and `utils.js`) and update the strings + assembly helpers to match, keeping takeover output byte-compatible with stock
 - **Keybindings** — before picking a new shortcut, check pi defaults + reserved keys, terminal control chars, and OS/terminal-emulator grabs; prefer `ctrl+alt+<letter>` for cross-platform safety. Do not stop at "it works on my machine in the main screen": in `fullscreen` mode (pi's default since 1.0) the alt-screen layer consumes `tui.altScreen.*` **before** dialogs see the key, and on Windows/WSL several of those bindings differ from the Linux defaults. Run `pnpm check:keybindings [candidate...]` (and `pnpm check:keybindings --all` after a pi upgrade) — it probes the installed host's resolved keybinding table with the host's own `matchesKey`. A key free in the host table can still be taken at the machine layer: Windows Terminal binds `ctrl+v` (paste) and `ctrl+shift+f` (find), and third-party Windows tools commonly grab `ctrl+alt+<letter>` (a screenshot tool once took `ctrl+alt+f`) — so try the key for real on the target machine before shipping it.
-- **Host compatibility** — the peer range is a measured statement, not a wish: the four most recently released pi minor lines are supported best-effort, the upper bound encodes the forward probe cap (newest line + 8 minor lines), and the README annotation must name the highest version actually verified. Re-run `pnpm check:compat` whenever the host dependency moves and read its verdict block (it fails if the declared range drifts from the policy). See the pi 宿主兼容 section of AGENTS.md; keybinding collisions found during an upgrade are reported to the maintainer for a decision, never re-keyed silently.
+- **Host compatibility** — the peer range is a measured statement, not a wish, and it only points backwards: the four most recently released pi minor lines are a mandatory window (fix our code, never raise the floor), below it we probe up to four older lines to find where compatibility actually ends, and the single number users see is the resulting floor (`pi >= <floor>`, no upper bound). Re-run `pnpm check:compat` whenever the host dependency moves and read its verdict block (it fails if the declared floor drifts from the measured one). See the pi 宿主兼容 section of AGENTS.md; keybinding collisions found during an upgrade are reported to the maintainer for a decision, never re-keyed silently.
 - **Quality gate** — `pnpm typecheck && pnpm test` must pass before submitting
 
 ---

package/README.zh-CN.md

@@ -10,12 +10,12 @@
 [![Pi package gallery](https://img.shields.io/badge/pi.dev-package%20gallery-6f42c1)](https://pi.dev/packages/@andares/pi-toolkits)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Package Manager](https://img.shields.io/badge/package%20manager-pnpm-orange?logo=pnpm)](https://pnpm.io)
-[![pi >= 1.0](https://img.shields.io/badge/pi-%3E%3D1.0.0%20%3C1.12.0-blueviolet)](https://github.com/earendil-works/pi)
+[![pi >= 0.99](https://img.shields.io/badge/pi-%3E%3D0.99.0-blueviolet)](https://github.com/earendil-works/pi)
 [![GitHub](https://img.shields.io/badge/github-andares%2Fpi--toolkits-181717?logo=github)](https://github.com/andares/pi-toolkits)
 
 一句话介绍:目前包含七个开箱即用的功能——**只读咨询模式** `ask`、**会话级边界权限** `ask-perm`、**模型收藏** `favorites`、**提示词暂存** `stash`、**第三方代码评审** `third-review`、**独立压缩模型** `compact-model`、**会话启动自动化** `autostart`,后续持续追加。
 
-**版本要求**:pi `>=1.0.0 <1.12.0` —— 最近 4 个中版本线(1.0.x / 1.1.x / 1.2.x / 1.3.x)尽力支持,上界编码「向后探针」的硬上限:宿主每发一版,我们最多向后查 **8 条中版本线**(当前 1.4 … 1.11),再晚不宣称。**实测自然兼容最高 1.3.0**(写此文时的最新版本,更新的还没发布、无物可探)。一条命令 `pnpm check:compat` 从 registry 推导目标集合,逐版本在系统临时目录沙箱中(把整个 `@earendil-works/*` 家族钉在待测版本)跑:安装 → `tsc --noEmit` → 全量测试 → 键位审计 → 对 patch/mirror 的宿主 `dist` 文件做哈希比对。1.0.0 → 1.3.0 全部 8 个已发布版本:typecheck、473 个测试、键位审计全绿;被跟踪的宿主文件仅在 `core/agent-session.js`(1.3.0 改了 tool-restore 路径,`cycleModel` 未动)、`core/keybindings.js` 与 `core/compaction/utils.js`(二者都是 1.2.0 变的,我们按键的解析结果不变)、`extensions/types.d.ts`(纯增量)上有差异 —— `ModelSelectorComponent`、`core/compaction/compaction.js` 与 `core/usage-totals.js` 在窗口内字节级不变。真实 pi 1.3.0 冒烟加载无警告。注:pi ≥ 0.99 的宿主要求「宿主提供的包」一律声明为 peerDependencies `"*"` —— `@earendil-works/pi-tui` 与 `typebox`(ask 的 `scratchpad` 用它构造参数 schema)都按此声明;若放进 `dependencies`,pi 会告警。
+**版本要求**:pi `>=0.99.0`。0.99.0 到 1.4.0 的每一个已发布版本都用完整门禁实测过(install → `tsc --noEmit` → 全量测试 → 键位审计 → 对 patch 目标宿主文件做哈希比对),每个版本都在沙箱中把整个 `@earendil-works/*` 家族钉在同一版本。更新的版本随发布逐个验证,下限只在实测结果允许时移动;`pnpm check:compat` 可复现该结论。注:pi ≥ 0.99 的宿主要求「宿主提供的包」一律声明为 peerDependencies `"*"` —— `@earendil-works/pi-tui` 与 `typebox`(ask 的 `scratchpad` 用它构造参数 schema)都按此声明;若放进 `dependencies`,pi 会告警。
 
 ---
 
@@ -255,11 +255,11 @@ pi 的 `/compact` 与 auto-compact 默认**用当前会话模型**做上下文
 | auto-compact 阈值触发 | 压缩模型总结 |
 | context overflow 恢复 | 压缩模型总结,重试行为不变 |
 
-**接管后与 pi 内建行为完全一致的部分**(逐字同步 pi 内建实现,复制自 0.87.1、在支持区间内全部已发布版本(1.0.0 → 1.3.0)字节级不变,只换执行模型;对话序列化函数(`serializeConversation`)是直接从宿主导入的,因此跟随宿主行为 —— 例如 1.2.0 起不再把 assistant thinking 回填进摘要请求):
+**接管后与 pi 内建行为完全一致的部分**(逐字同步 pi 内建实现,复制自 0.87.1、在 1.1.0 → 1.4.0 内字节级不变 —— 除了此处采纳的两项 1.4.0 修正:摘要请求使用模型自身的输出上限而非 `reserveTokens` 的固定比例,以及 `/compact <instructions>` 也会进入 split-turn 前缀;只换执行模型;对话序列化函数(`serializeConversation`)是直接从宿主导入的,因此跟随宿主行为 —— 例如 1.2.0 起不再把 assistant thinking 回填进摘要请求):
 
 - **摘要格式** —— Goal / Progress / Key Decisions 结构化 checkpoint;已有摘要时用迭代更新版 prompt,信息延续不丢
 - **切分行为** —— 保留最近 `keepRecentTokens` 的策略、`firstKeptEntryId` / `tokensBefore` 原样回传,不动
-- **输出预算** —— 与内建同公式(历史段 0.8×、切分前缀段 0.5× `reserveTokens`,再按模型输出上限收敛)
+- **输出预算** —— 摘要请求使用模型自身的输出上限,与 1.4.0 起的内建一致(#9512:过去按 0.8×/0.5× `reserveTokens` 设上限,长思考会把摘要顶到 "generation hit the token cap" 而失败);`reserveTokens` 只决定何时开始压缩
 - **文件清单尾部** —— `<read-files>` / `<modified-files>` 标签照常拼在摘要尾部,details 同形状维护
 - **用量统计** —— 压缩模型的 token/cost 计入 session 统计
 - **可取消** —— 压缩进行中 `Esc` 干净取消(信号透传到底层调用)
@@ -336,7 +336,7 @@ run = [
 
 **关键约束:只支持扩展命令**。`/add-dir`(pi-add-dir)、`/cd`(pi-cd)等 `registerCommand` 注册的命令可以;内置命令(`/compact`、`/reload`、`/resume`…)在 TUI 层分发,扩展层触发不了;skill 命令(`/skill:name`)是展开机制而非执行机制。依赖的目标扩展(如 pi-add-dir)需要先安装。
 
-> **实现说明**:执行用 `sendUserMessage(cmd, { expandPromptTemplates: true })` —— 该选项把 `/cmd args` 路由到命令分发而不是模型 prompt 路径(包装层默认 `false`,`sendUserMessage` 与 `_tryExecuteExtensionCommand` 在 1.0.0–1.3.0 全区间字节级一致,见 AGENTS.md 宿主兼容纪律)。预校验用 `pi.getCommands()`(只认 `source: "extension"`)。依赖 `smol-toml`(零依赖、~10KB、TOML 1.0)。
+> **实现说明**:执行用 `sendUserMessage(cmd, { expandPromptTemplates: true })` —— 该选项把 `/cmd args` 路由到命令分发而不是模型 prompt 路径(包装层默认 `false`,`sendUserMessage` 与 `_tryExecuteExtensionCommand` 在 1.1.0–1.4.0 全区间字节级一致,见 AGENTS.md 宿主兼容纪律)。预校验用 `pi.getCommands()`(只认 `source: "extension"`)。依赖 `smol-toml`(零依赖、~10KB、TOML 1.0)。
 
 ---
 
@@ -352,7 +352,7 @@ pnpm typecheck    # tsc --noEmit
 pnpm test         # vitest(全部功能单元测试)
 
 pnpm check:keybindings   # 用宿主自己的分发表审计本插件的按键
-pnpm check:compat        # 校验声明的 pi 区间:最近 4 条中版本线 + 向后 8 条线探针
+pnpm check:compat        # 校验声明的 pi 下限:强制 4 条线窗口 + 向后 4 条线探针 → public floor
 ```
 
 ### 项目结构
@@ -412,7 +412,7 @@ pnpm release:github --audit    # 列出 npm 版本 vs GitHub Release vs 远端 t
 - **内建 patch**(favorites)必须保持**版本守卫 + 幂等** —— 打 patch 前先确认目标原型成员存在,防止重复应用,失败时用 `console.warn` 降级而不是把扩展搞挂
 - **内建提示词同步**(compact) —— `src/features/compact/prompt.ts` 里的总结 prompt 逐字抄自 pi 内建压缩;升级 pi 依赖时 diff `dist/core/compaction/compaction.js`(及 `utils.js`),同步字符串与组装辅助函数,保持接管输出与内建字节级一致
 - **键位** —— 定新快捷键前先查 pi 默认键位 + 保留键、终端控制字符、OS/终端模拟器占用;跨平台安全优先选 `ctrl+alt+<字母>`。**不得只验证「主屏下我这台机器能用」**:自 pi 1.0 起默认 `fullscreen`,alt-screen 层在对话框看到按键**之前**就消费 `tui.altScreen.*`,且 Windows/WSL 上多个绑定与 Linux 默认值不同。用 `pnpm check:keybindings [候选键...]` 核查(pi 升级后跑 `pnpm check:keybindings --all`),它用宿主自己的 `matchesKey` 探测已安装宿主的**已解析**键位表。**宿主表空闲 ≠ 机器层空闲**:Windows Terminal 默认占 `ctrl+v`(粘贴)与 `ctrl+shift+f`(查找),第三方 Windows 工具常绑 `ctrl+alt+<字母>`(截图工具占过 `ctrl+alt+f`)——定键后必须在真机试按,确认按键真的到得了应用。
-- **宿主兼容** —— peer 区间是实测结论而非愿望:最近 4 个已发布中版本线尽力支持,上界编码「向后探 8 条中版本线」的上限,README 必须标注**实测支持到的最高版本**。宿主依赖一动就重跑 `pnpm check:compat`,读它的 verdict 段(区间与策略不一致会直接判失败)。详见 AGENTS.md「pi 宿主兼容」;升级中发现的键位冲突**上报崔总决策**,不得顺手换键。
+- **宿主兼容** —— peer 区间是实测结论而非愿望,而且只往回指:最近 4 个已发布中版本线是**强制窗口**(不兼容就改我们的代码,绝不抬下限),窗口之下再向后探最多 4 条线找出兼容实际停在哪里,对使用者只展示一个数:由此得到的**下限**(`pi >= <floor>`,无上界)。宿主依赖一动就重跑 `pnpm check:compat`,读它的 verdict 段(声明下限与实测不一致会直接判失败)。详见 AGENTS.md「pi 宿主兼容」;升级中发现的键位冲突**上报崔总决策**,不得顺手换键。
 - **质量门禁** —— 提交前必须通过 `pnpm typecheck && pnpm test`
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andares/pi-toolkits",
-  "version": "0.9.7",
+  "version": "0.9.8",
   "description": "Integrated toolkit extension for pi — ask mode (read-only Q&A), session-scoped permission checks, model favorites, prompt stash, third-party code review, session autostart, and a dedicated compaction model",
   "type": "module",
   "license": "MIT",
@@ -33,7 +33,7 @@
     "boundary"
   ],
   "peerDependencies": {
-    "@earendil-works/pi-coding-agent": ">=1.0.0 <1.12.0",
+    "@earendil-works/pi-coding-agent": ">=0.99.0",
     "@earendil-works/pi-tui": "*",
     "typebox": "*"
   },
@@ -43,9 +43,9 @@
     "smol-toml": "^1.9.0"
   },
   "devDependencies": {
-    "@earendil-works/pi-ai": "^1.3.0",
-    "@earendil-works/pi-coding-agent": "^1.3.0",
-    "@earendil-works/pi-tui": "^1.3.0",
+    "@earendil-works/pi-ai": "^1.4.0",
+    "@earendil-works/pi-coding-agent": "^1.4.0",
+    "@earendil-works/pi-tui": "^1.4.0",
     "@types/node": "^26.6.2",
     "typebox": "^1.3.27",
     "typescript": "^5.6.0",

package/src/features/ask/reasons.ts

@@ -2,7 +2,7 @@
  * ask feature — actionable rejection messages.
  *
  * The `tool_call` hook's `reason` is delivered to the model as the tool result
- * (verified against pi 1.3.0: `extensions/runner.js` returns the `{block,
+ * (verified against pi 1.4.0: `extensions/runner.js` returns the `{block,
  * reason}` result unchanged and pi-agent-core's `agent-loop.js` turns it into
  * `createErrorToolResult(reason)`; both paths are byte-identical to 1.2.0), so
  * it is the best place to name the nearest allowed alternative and stop the model

package/src/features/autostart/autostart.ts

@@ -48,7 +48,7 @@ export const RUNNABLE_REASONS: ReadonlySet<string> = new Set([
  * `-r` (`--resume`), `--session <path>` and `--fork <path>` all open an
  * existing session *before* the first runtime exists, and that runtime is
  * created without an explicit session_start event, so extensions see pi's
- * default reason — `startup` — not `resume` (verified on pi 1.0.0–1.3.0:
+ * default reason — `startup` — not `resume` (verified on pi 1.1.0–1.4.0:
  * `main.js` builds the initial session manager from those flags and calls
  * `createAgentSessionRuntime` with no `sessionStartEvent`;
  * `agent-session.js` defaults it to `{ reason: "startup" }`). `resume` is only

package/src/features/autostart/index.ts

@@ -27,7 +27,7 @@
  * that flag is what routes "/cmd args" through _tryExecuteExtensionCommand
  * instead of the model prompt path. The wrapper defaults it to false in this
  * package (each byte-identical across every published version of the supported
- * window, 1.0.0 → 1.3.0; see AGENTS.md host-compat discipline for the version
+ * window, 1.1.0 → 1.4.0; see AGENTS.md host-compat discipline for the version
  * matrix).
  *
  * Only extension commands can run this way. Built-in commands (/compact,

package/src/features/compact/compact.test.ts

@@ -418,27 +418,25 @@ describe("session_before_compact handler", () => {
 			.calls[0] as [
 			AvailableModel,
 			unknown,
-			{ maxTokens: number; signal: AbortSignal },
+			{ maxTokens?: number; signal: AbortSignal },
 		];
 		expect(modelKey(model)).toBe("google/gemini-2.5-flash");
-		// 0.8 × reserveTokens(16000) = 12800, under the model cap (8192).
-		expect(options.maxTokens).toBe(8192);
+		// pi 1.4.0 (#9512): no fixed output cap — the request omits maxTokens
+		// so the provider uses the model's own output limit.
+		expect(options).not.toHaveProperty("maxTokens");
 		expect(options.signal).toBe(event.signal);
 	});
 
-	it("clamps the budget by reserveTokens when the model cap is larger", async () => {
+	it("does not derive an output budget from reserveTokens", async () => {
 		getCompactStore().setModel("google/gemini-2.5-flash");
 		const { handler } = registeredHandler();
 		const bigCapModel = { ...MODELS[0], maxTokens: 65536 };
 		const { ctx, complete } = fakeCtx({ models: [bigCapModel] });
 		await handler(fakeEvent() as never, ctx);
 		const [, , options] = (complete as ReturnType<typeof vi.fn>).mock
-			.calls[0] as [
-			AvailableModel,
-			unknown,
-			{ maxTokens: number },
-		];
-		expect(options.maxTokens).toBe(12800);
+			.calls[0] as [AvailableModel, unknown, { maxTokens?: number }];
+		// reserveTokens (16000) used to cap this at 12800; the cap is gone.
+		expect(options).not.toHaveProperty("maxTokens");
 	});
 
 	it("falls back with a warning on an empty summary", async () => {
@@ -568,6 +566,31 @@ describe("session_before_compact handler", () => {
 		expect(prompts[0]).toContain("Additional focus: 保留命令输出细节");
 	});
 
+	it("passes customInstructions to the split-turn prefix summary too", async () => {
+		getCompactStore().setModel("google/gemini-2.5-flash");
+		const { handler } = registeredHandler();
+		const prompts: string[] = [];
+		const { ctx } = fakeCtx({
+			complete: vi.fn(async (_model, context) => {
+				prompts.push(
+					(context.messages[0]?.content as Array<{ text?: string }>)[0]?.text ??
+						"",
+				);
+				return fakeResponse("## Goal\n- x");
+			}),
+		});
+		const event = fakeEvent({
+			messagesToSummarize: [],
+			turnPrefixMessages: [userMessage("prefix msg")],
+			isSplitTurn: true,
+		});
+		Object.assign(event, { customInstructions: "保留命令输出细节" });
+		await handler(event as never, ctx);
+		expect(prompts).toHaveLength(1);
+		expect(prompts[0]).toContain("# Instructions");
+		expect(prompts[0]).toContain("Additional focus: 保留命令输出细节");
+	});
+
 	it("switches to the update prompt when a previous summary exists", async () => {
 		getCompactStore().setModel("google/gemini-2.5-flash");
 		const { handler } = registeredHandler();

package/src/features/compact/index.ts

@@ -9,13 +9,15 @@
  *  - takeover point: the `session_before_compact` extension event, which pi
  *    emits for ALL three trigger reasons (manual / threshold / overflow)
  *    before running its own compaction
- *  - prompts, message assembly, split-turn handling, output budgets, and the
- *    summary file-list tail are verbatim pi built-in behavior (copied from
- *    0.87.1, byte-identical across every published version of the supported
- *    window, 1.0.0 → 1.3.0) — only the executing model differs. The one
- *    exception is `serializeConversation`, which is imported from the host
- *    instead of mirrored, so it tracks whatever the running host does
- *    (1.2.0 stopped feeding assistant thinking into the request).
+ *  - prompts, message assembly, split-turn handling, summary budgets, and
+ *    the summary file-list tail are verbatim pi built-in behavior (copied
+ *    from 0.87.1; `core/compaction/compaction.js` stayed byte-identical
+ *    1.0.0 → 1.3.0, and 1.4.0 changed only the summary output budget and
+ *    the split-turn focus handling mirrored below) — only the executing
+ *    model differs. The one exception is `serializeConversation`, which is
+ *    imported from the host instead of mirrored, so it tracks whatever the
+ *    running host does (1.2.0 stopped feeding assistant thinking into the
+ *    request).
  *  - lossless fallback: unset config, unavailable model, empty/failed
  *    summary, or user abort → return undefined and pi's default compaction
  *    (session model) runs untouched. The extension can never make
@@ -75,7 +77,6 @@ async function completeSummary(
 	ctx: ExtensionContext,
 	model: AvailableModel,
 	promptText: string,
-	maxTokens: number,
 	signal: AbortSignal,
 ): Promise<{ text: string; usage: CompleteUsage }> {
 	const response = await ctx.modelRegistry.complete(
@@ -91,7 +92,10 @@ async function completeSummary(
 			],
 		},
 		{
-			maxTokens,
+			// No `maxTokens`: since pi 1.4.0 (#9512) the built-in compaction asks
+			// for the model's own output limit instead of a fixed fraction of
+			// reserveTokens, so a long reasoning block can no longer eat the cap
+			// and fail the summary with "generation hit the token cap".
 			signal,
 			cacheRetention: "none",
 			sessionId: uuidv7(),
@@ -118,30 +122,26 @@ async function completeSummary(
 	return { text, usage: response.usage };
 }
 
-/**
- * pi's output-budget formula (compaction.js, 0.87.1 → 1.3.0 unchanged): a
- * fraction of reserveTokens clamped by the model's own output cap.
- */
-function summarizationBudget(
-	fraction: number,
-	reserveTokens: number,
-	modelMaxTokens: number,
-): number {
-	return Math.min(
-		Math.floor(fraction * reserveTokens),
-		modelMaxTokens > 0 ? modelMaxTokens : Number.POSITIVE_INFINITY,
-	);
-}
-
 /**
  * Run the full compaction summarization with the configured model,
- * replicating pi's compact() (0.87.1, byte-identical across the supported
- * 1.0.0 → 1.3.0 window):
+ * replicating pi's compact() as of 1.4.0 (byte-identical to 0.87.1's shape
+ * apart from the two 1.4.0 fixes adopted for the whole window, see below):
  * history summary (first-connection or iterative-update prompt, custom
  * focus appended), plus a separate turn-prefix checkpoint when the cut point
  * splits a turn, merged into one summary with the file-list tail. Returns
  * undefined on any failure after notifying (pi default compaction then takes
  * over).
+ *
+ * 1.4.0 changed two things this mirror covers, and we follow 1.4.0 for every
+ * host in the supported window (1.1.0 → 1.4.0) because both are bug fixes
+ * rather than behavior we could sensibly keep per version:
+ *  - summaries no longer cap maxTokens at 0.8/0.5 × reserveTokens; the
+ *    request omits maxTokens so the provider uses the model's output limit
+ *    (#9512 — long reasoning made summaries fail with "generation hit the
+ *    token cap"). `reserveTokens` now only decides when compaction starts.
+ *  - `/compact <instructions>` also reaches the split-turn prefix summary
+ *    (#11058; before 1.4.0 the focus was dropped when the split turn was the
+ *    only new content).
  */
 async function runCompactModelCompaction(
 	ctx: ExtensionContext,
@@ -157,7 +157,6 @@ async function runCompactModelCompaction(
 		firstKeptEntryId,
 		previousSummary,
 		fileOps,
-		settings,
 	} = preparation;
 
 	try {
@@ -177,11 +176,6 @@ async function runCompactModelCompaction(
 						previousSummary,
 						customInstructions,
 					),
-					summarizationBudget(
-						0.8,
-						settings.reserveTokens,
-						model.maxTokens,
-					),
 					signal,
 				);
 				historyText = history.text;
@@ -192,8 +186,8 @@ async function runCompactModelCompaction(
 				model,
 				buildTurnPrefixPromptText(
 					serializeConversation(convertToLlm(turnPrefixMessages)),
+					customInstructions,
 				),
-				summarizationBudget(0.5, settings.reserveTokens, model.maxTokens),
 				signal,
 			);
 			summaryText = `${historyText}\n\n---\n\n**Turn Context (split turn):**\n\n${turnPrefix.text}`;
@@ -212,7 +206,6 @@ async function runCompactModelCompaction(
 					previousSummary,
 					customInstructions,
 				),
-				summarizationBudget(0.8, settings.reserveTokens, model.maxTokens),
 				signal,
 			);
 			summaryText = history.text;

package/src/features/compact/prompt.ts

@@ -6,14 +6,15 @@
  * summaries produced by the configured compact model are formatted exactly
  * like pi's own compaction output. Only the executing model differs.
  * Verified byte-identical against every published version of the supported
- * window (1.0.0 → 1.3.0): dist/core/compaction/compaction.js and
- * core/usage-totals.js are unchanged files across that span, and the only
- * utils.js change (1.2.0 dropping assistant thinking from
+ * window (1.1.0 → 1.4.0): core/usage-totals.js is unchanged across that
+ * span, the only utils.js change (1.2.0 dropping assistant thinking from
  * serializeConversation) does not touch the strings mirrored here — that
- * serializer is imported from the host, not mirrored. 0.87.0 shipped a
- * different split-turn prefix prompt; the text mirrored here is 0.87.1's
- * fix, and the mirror is the only variant any supported host gets —
- * intentional.
+ * serializer is imported from the host, not mirrored — and compaction.js
+ * changed once, in 1.4.0, in the output budget and the split-turn focus
+ * handling (both adopted here, see buildTurnPrefixPromptText). 0.87.0
+ * shipped a different split-turn prefix prompt; the text mirrored here is
+ * 0.87.1's fix, and the mirror is the only variant any supported host gets
+ * — intentional.
  *
  * Update these strings whenever pi changes its built-in prompts (diff
  * dist/core/compaction/compaction.js between versions).
@@ -146,11 +147,21 @@ export function buildHistoryPromptText(
 
 /**
  * Build the split-turn prefix prompt text (pi 0.87.1
- * generateTurnPrefixSummary): `# Conversation` block followed by
- * `# Instructions`.
+ * generateTurnPrefixSummary, extended in 1.4.0): `# Conversation` block
+ * followed by `# Instructions`, with the `/compact <instructions>` focus
+ * appended as `Additional focus: ...`. 1.4.0 added that last line (#11058:
+ * the focus used to be dropped when the split turn was the only new
+ * content since the last compaction); we use the fixed form on every host.
  */
-export function buildTurnPrefixPromptText(conversationText: string): string {
-	return `# Conversation\n${conversationText}\n\n# Instructions\n${TURN_PREFIX_SUMMARIZATION_PROMPT}`;
+export function buildTurnPrefixPromptText(
+	conversationText: string,
+	customInstructions?: string,
+): string {
+	let promptText = `# Conversation\n${conversationText}\n\n# Instructions\n${TURN_PREFIX_SUMMARIZATION_PROMPT}`;
+	if (customInstructions) {
+		promptText = `${promptText}\n\nAdditional focus: ${customInstructions}`;
+	}
+	return promptText;
 }
 
 /** File-operation sets extracted by pi's prepareCompaction. */
@@ -203,7 +214,7 @@ export function formatFileOperations(
 /**
  * Combine two provider usage records field-wise (pi 0.87.1 compaction.js
  * combineUsage, moved verbatim to core/usage-totals.js in 0.99.0 and
- * unchanged through 1.3.0): used when
+ * unchanged through 1.4.0): used when
  * a split turn produces two summarization calls.
  */
 export function combineUsage<T extends UsageLike>(first: T, second: T): T {

package/src/features/favorites/constants.ts

@@ -8,8 +8,8 @@
  * bindings — only the cycle semantics change (patch-cycle.ts), so no
  * keybinding conflicts arise.
  *
- * Verified against every published version of the supported window
- * (1.0.0 → 1.3.0) keybinding
+ * Verified against every published version of the supported range
+ * (0.99.0 → 1.4.0) keybinding
  * tables + pi-tui input dispatch on WSL2 + Windows Terminal; re-run
  * `pnpm check:keybindings` after every host upgrade before trusting this.
  */
@@ -30,11 +30,12 @@ export const FAVORITES_FILE = "pi-toolkits-favorites.json";
  * Windows/WSL `tui.altScreen.search` resolves to ctrl+f, and
  * `TuiAltScreen.handleViewportInput()` checks it before
  * `shouldDeferViewportInputToOverlay()`, so the keystroke opens transcript
- * search and the selector never sees it (verified in pi-tui 1.3.0
+ * search and the selector never sees it (verified in pi-tui 1.4.0
  * `dist/tui-alt-screen.js`: the search check is the first key branch and
- * returns `{ consume: true }` unconditionally).
+ * returns `{ consume: true }` unconditionally; the 1.4.0 changes to that
+ * file are exit/teardown only).
  *
- * Why ctrl+alt+f was discarded: clean at the pi layer across 1.0–1.3 (only
+ * Why ctrl+alt+f was discarded: clean at the pi layer across 1.1–1.4 (only
  * ctrl+alt+] is taken from that family) and byte-distinguishable without
  * kitty — but grabbed at the OS/app layer on the author's machine by a
  * Windows screenshot tool, so it never reached the terminal. Lesson: a key

package/src/features/favorites/patch-cycle.ts

@@ -15,7 +15,8 @@
  *    model available" feedback); otherwise jump to it
  *  - the apply logic mirrors pi's _cycleScopedModel/_cycleAvailableModel
  *    (byte-identical across every published version in the supported window
- *    1.0.0 → 1.3.0:
+ *    1.1.0 → 1.4.0 — `cycleModel` itself is untouched by 1.4.0's recovery and
+ *    tool-restore rewrites:
  *    state swap, session persistence, default-model persistence only when
  *    `options.persist` is set, thinking-level re-clamp, model_select emit
  *    with source "cycle")
@@ -31,9 +32,9 @@ import { getFavoritesStore, modelKey } from "./store.js";
 
 /**
  * pi's `Model<any>` — the exact type of `ModelCycleResult.model`
- * (pi-coding-agent 1.0–1.3; the field is unchanged across that span).
+ * (pi-coding-agent 1.1–1.4; the field is unchanged across that span).
  * Derived here instead of importing `Model` from @earendil-works/pi-ai,
- * whose index.d.ts (1.0 through 1.3.0 alike) re-exports it via an
+ * whose index.d.ts (1.1 through 1.4.0 alike) re-exports it via an
  * extensioned `"./types.ts"` specifier that not every TS resolver substitutes
  * to `types.d.ts` (tsc 5.9 bundler does; other tsserver builds don't).
  */

package/src/features/favorites/patch-selector.ts

@@ -21,8 +21,8 @@
  * upgraded internals), patches are skipped with a warning — the extension
  * keeps loading and ctrl+p falls back to stock behavior. The prototype
  * shape touched here (handleInput/updateList/filterModels and the instance
- * fields below) is byte-identical across every published version in
- * pi 1.0.0 → 1.3.0 (and 0.99.0 → 1.2.0 before the floor moved).
+ * fields below) is byte-identical across the mandatory window
+ * pi 1.1.0 → 1.4.0 (and exercised by the 0.99.0 → 1.0.4 backward probes).
  */
 import {
 	ModelSelectorComponent,

package/src/features/stash/stash.ts

@@ -21,7 +21,7 @@ import type { KeyId } from "@earendil-works/pi-tui";
 /**
  * Stash hotkey.
  *
- * Compatibility rationale (verified against pi 1.0.0–1.3.0 keybindings, live
+ * Compatibility rationale (verified against pi 0.99.0–1.4.0 keybindings, live
  * matchesKey probes and terminal/OS behavior):
  *  - pi: no default binding for ctrl+alt+<letter> (only ctrl+alt+] is taken);
  *    extension shortcuts dispatch first while the editor is focused

package/src/lib/gates.ts

@@ -17,6 +17,10 @@
  *    slot; a second presentation would mount over the first and strand its
  *    promise. The queue serializes our own presentations; the host slot is
  *    still shared with other extensions (pi does not arbitrate globally).
+ *    pi 1.4.0 stacks extension dialogs so a second one no longer strands the
+ *    first (#11166), but the 1.1–1.3 hosts in the supported window still
+ *    replace it — the queue stays, and it also keeps one confirmation visible
+ *    at a time instead of a pile of stacked dialogs on 1.4.0.
  *  - A gate that throws blocks the call (fail closed), matching pi's own
  *    `tool_call` handler contract.
  */

package/src/lib/model-config.ts

@@ -4,8 +4,8 @@
  * (review, compact-model — favorites keeps its own store-local key logic).
  *
  * Types are derived from pi-coding-agent's own exports (ModelRegistry)
- * rather than imported from @earendil-works/pi-ai: pi-ai's index.d.ts (1.0.0
- * through 1.3.0 alike) re-exports `Model`/`Api` via extensioned
+ * rather than imported from @earendil-works/pi-ai: pi-ai's index.d.ts (1.1.0
+ * through 1.4.0 alike) re-exports `Model`/`Api` via extensioned
  * `./types.ts` specifiers, which tsc 5.9 bundler resolution substitutes to
  * `.d.ts` but some tsserver builds do not. Deriving from ModelRegistry keeps
  * every resolver in agreement with the exact type

package/src/lib/model-picker.ts

@@ -9,7 +9,7 @@
  *
  * The component is driven through a small ModelRuntime facade backed by
  * ctx.modelRegistry (pi's extension-facing wrapper). SAFETY: verified
- * against pi 1.0.0–1.3.0 dist (modes/interactive/components/model-selector.js +
+ * against pi 1.1.0–1.4.0 dist (modes/interactive/components/model-selector.js +
  * model-catalog-refresh.js — byte-identical across that span) — the
  * component only calls getAvailableSnapshot, getModel, getError and refresh
  * on modelRuntime, and ModelRegistry provides exactly those