@each1024/pi-mini-mode 2.0.9 → 2.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -12,7 +12,7 @@ An everyday refinement for [Pi](https://pi.dev), not just a footer. Preview imag
12
12
 
13
13
  https://github.com/user-attachments/assets/1ad90757-ecea-4901-afd8-f33a68176ae2
14
14
 
15
- https://github.com/user-attachments/assets/53c1bcd8-9f0b-42d7-a424-a407dcf666e8
15
+
16
16
 
17
17
  Numbers in the footer shots come from a scripted demo session; prices are estimates, not provider bills.
18
18
 
@@ -78,6 +78,7 @@ Enable **Minimal output** in `/pi-mini-mode-settings`.
78
78
  - **Subagents, in plain sight.** Click a subagent row to expand its available activity and message/final output. In minimal mode, this extension uses `Ctrl+S` to expand or collapse completed subagent summaries; Pi's focused selectors keep their own keys. A dispatch receipt or returned tool call is not a completed background task.
79
79
  - **A process tree, not a wall of output.** Thinking, tools and skill reads share one chronological tree. The latest summaries stay visible, including the latest thinking; `Ctrl+O` expands or collapses the full process. New questions start collapsed.
80
80
  - **Tool details on demand.** Expand a tool or thinking entry, including the latest thinking, using its fold control. Thinking starts collapsed and only expands or collapses manually, including while running. Tool details show saved text, not the original custom renderer or image output.
81
+ - **Readable summaries.** Long tool rows keep the command beginning and put the ellipsis at the end; expanding reveals the complete long or multiline input. Live thinking follows the latest returned summary, while completed thinking previews its beginning and expands to the full received text. Empty summaries show their actual state without repeating a tool command; failures and interruptions stop the thinking clock.
81
82
  - **Room for the answer.** Final Markdown streams without extra headings or backgrounds. Failures and interruptions stay explicit. Folding changes presentation, not stored session messages.
82
83
 
83
84
  Turn **Minimal output** off in settings to restore native Pi history.
@@ -203,21 +204,23 @@ Install only the local copy while developing; installing npm and local copies to
203
204
  ```bash
204
205
  pi remove npm:@each1024/pi-mini-mode && pi install /path/to/pi-mini-mode
205
206
  npm run check
206
- npm test
207
+ npm run check:syntax
207
208
  ```
208
209
 
209
- After source changes, run `/reload` in an already-open Pi session. `npm run check` runs TypeScript checking and `npm test` runs the project self-checks.
210
+ After source changes, run `/reload` in an already-open Pi session. `npm run check` checks all extension and library TypeScript, including unused declarations and parameters. `npm run check:syntax` parses the JavaScript checks, maintenance scripts, and settings page without executing them.
211
+
212
+ For a specific regression, list the existing checks with `npm run check:focused -- --list`, then select one, for example `npm run check:focused -- settings-web`. `npm test` uses the same selector and requires a name; it never defaults to the full suite. Terminal fixtures in `test/minimal-pty.py` remain available for explicitly requested terminal investigations.
210
213
 
211
- For a real terminal smoke test, run `python3 test/minimal-pty.py`. It needs Python 3, Node, and the installed dependency’s bundled Pi CLI. Temporary fixtures cover regular/fullscreen output, toggling, process expansion, restored results, and narrow terminals without model calls.
214
+ The direct development dependency on `@earendil-works/pi-server` is required by experimental modules imported by Pi 0.85.0; that Pi release omits it from its package dependencies. Keep it until a Pi upgrade fixes the upstream dependency declaration.
212
215
 
213
216
  </details>
214
217
 
215
218
  <details>
216
219
  <summary><strong>Publishing</strong></summary>
217
220
 
218
- Complete and commit the task, then run `npm run release` from a clean checkout. It selects one version above every historically published stable npm version, updates package.json and the lockfile, checks types, commits and pushes to main, publishes to npm, verifies the package and latest tag, and creates the matching Git tag. Versions start at `2.0.6`; the final number continues through 100 and beyond and does not reset when the feature version changes. Pi uses the same npm version. Ordinary pushes do not publish. The manual CI backup publishes the committed version exactly and never changes it. Failed publication stops without a second publish.
221
+ Every push to main (including merged PRs) that changes `extensions/`, `lib/`, `themes/`, package.json or the lockfile publishes automatically via `.github/workflows/publish.yml`: a package.json version above the highest published npm version is used as is; otherwise the patch number of the highest published version is incremented, the package is published to npm, the version is committed back to main with `[skip ci]`, and a matching tag and GitHub Release are created. Docs-only or CI-only changes do not publish, and a version is never published twice. The Pi package gallery discovers the package from npm.
219
222
 
220
- The backup workflow needs the package’s npm Trusted Publisher configured for this GitHub repository and `publish.yml`. It uses OIDC and provenance and does not use an npm token.
223
+ npm authentication prefers a Trusted Publisher (OIDC) bound to this repository and `publish.yml`; a repository secret `NPM_TOKEN` also works.
221
224
 
222
225
  </details>
223
226
 
package/README.zh-CN.md CHANGED
@@ -194,25 +194,23 @@ deepseek-v4-flash high Total 45K Cached 25K CH 40.0% $0.012 ◇ MCP 3 500
194
194
  ```bash
195
195
  pi remove npm:@each1024/pi-mini-mode && pi install /path/to/pi-mini-mode
196
196
  npm run check
197
- npm test
197
+ npm run check:syntax
198
198
  ```
199
199
 
200
- 修改源码后,在已打开的 Pi 会话中运行 `/reload`。`npm run check` 会执行 TypeScript 检查,`npm test` 会执行页脚、设置和发布自检。真实终端冒烟测试:
200
+ 修改源码后,在已打开的 Pi 会话中运行 `/reload`。`npm run check` 检查扩展与 lib 中的全部 TypeScript,包含未使用声明和参数;`npm run check:syntax` 只解析检查脚本、维护脚本及设置页的 JavaScript,不执行检查脚本。
201
201
 
202
- ```bash
203
- python3 test/minimal-pty.py
204
- ```
202
+ 需要定位具体回归时,先用 `npm run check:focused -- --list` 列出已有检查,再指定一个名称,例如 `npm run check:focused -- settings-web`。`npm test` 使用相同入口,必须指定名称,不再默认执行全量套件。`test/minimal-pty.py` 保留供明确要求的终端问题调查使用。
205
203
 
206
- 该测试需要 Python 3、Node 以及已安装依赖中自带的 Pi CLI;会使用临时 fixture,覆盖普通/全屏模式、切换、10 条过程记录、`Ctrl+O` 展开/收起、恢复结果和窄终端,不会调用模型。
204
+ 开发依赖 `@earendil-works/pi-server` 是 Pi 0.85.0 的实验性模块间接导入所需,上游该版本漏写了依赖声明;升级 Pi 并确认上游修复后才能移除。
207
205
 
208
206
  </details>
209
207
 
210
208
  <details>
211
209
  <summary><strong>发布</strong></summary>
212
210
 
213
- 每轮改动完成并提交后,在干净的工作区运行 `npm run release`。入口统一确定高于 npm 全部历史稳定版本的版本号,同步 package.json 与 lockfile,执行类型检查,提交并推送 main,发布 npm,核验包内容与 latest,最后创建同名 Git 标签。新流程从 `2.0.6` 开始,末位持续累加,可超过 100,功能版本升级也不归零。Pi 使用同一 npm 版本。普通推送不触发发布;手动 CI 备用入口只发布已提交的版本,不自行升号。发布失败立即停止,不重复发布。
211
+ 推到 main(含 PR 合并)且 `extensions/`、`lib/`、`themes/`、package.json 或 lockfile 有变化时,`.github/workflows/publish.yml` 自动发布:package.json 版本高于 npm 已发布的最高版本就用它,否则在最高版本上末位 +1,发布 npm 后把版本号以 `[skip ci]` 提交回 main,并创建同名标签和 GitHub Release。只改文档或 CI 不发布;同一版本不会重复发布。Pi 插件目录从 npm 收录,无需另外上传。
214
212
 
215
- 备份流程需要为该包配置指向此 GitHub 仓库及 `publish.yml` 的 npm Trusted Publisher。它使用 OIDC 和 provenance,不使用 npm token。
213
+ npm 认证优先使用指向本仓库 `publish.yml` 的 Trusted Publisher(OIDC);也可配置仓库 Secret `NPM_TOKEN`。
216
214
 
217
215
  </details>
218
216