@gavin-hu/my-pi-agent 0.11.3 → 0.12.0

package/README.md

@@ -60,11 +60,13 @@ pi -e .                                                    # try it for one run
 Then, from inside Pi:
 
 - `/bytefly [extension] [refresh]` opens the control center on Extensions, lists
-  every loaded extension with its runtime health, and enables or disables one.
+  every loaded extension with its runtime health, enables or disables one, and
+  clears a project override with `x`.
 - `/bytefly settings` opens the control center's Settings section: bytefly
-  startup TUI, desktop notifications, the transcript rail glyph, output padding,
-  and the hardware cursor, with `Space`/`Enter` to change a value and `Tab` for
-  Global/Project scope.
+  startup TUI, desktop notifications and their delivery method, the proactive
+  health check, the currency and cost precision, the transcript
+  rail glyph, output padding, and the hardware cursor, with `Space`/`Enter` to
+  change a value and `Tab` for Global/Project scope.
 - `/bytefly doctor [extension] [refresh]` prints the doctor report —
   `run_doctor`'s text — and checks that each enabled extension has what it needs
   at runtime.
@@ -110,7 +112,7 @@ extension's own `README.md` has the full tool and command surface.
 
 | Extension | Tools and commands | What it does |
 |---|---|---|
-| [`bytefly`](./extensions/bytefly/) | `/bytefly` (with the `doctor` and `settings` subcommands), `run_doctor` | A themed header and width-adaptive footer, a two-row `You` nameplate on each user message, a rule between completed turns, a shared transcript notice, a tool block that leads with its call line and rails its result body two columns under it (the rail glyph is the `chrome.rail` setting), a live elapsed counter on Pi's working row, the `/bytefly` control center — an Extensions section that lists every extension with its health and enables or disables one, plus a Settings section with five curated preferences (`/bytefly settings`) — `/bytefly doctor` prints the doctor report, and an opt-in `notify` capability that raises OS notifications when a run or a background job finishes or the agent asks for input. DeepSeek is priced out of the box, and `bytefly.json` is the shared config document every extension reads. |
+| [`bytefly`](./extensions/bytefly/) | `/bytefly` (with the `doctor` and `settings` subcommands), `run_doctor` | A themed header and width-adaptive footer, a two-row `You` nameplate on each user message, a rule between completed turns, a shared transcript notice, a tool block that leads with its call line and rails its result body two columns under it (the rail glyph is the `chrome.rail` setting), a live elapsed counter on Pi's working row, the `/bytefly` control center — an Extensions section that lists every extension with its health and enables or disables one, plus a Settings section with ten curated preferences across six groups, including inline text editing for the notification title (`/bytefly settings`) — `/bytefly doctor` prints the doctor report, and an opt-in `notify` capability that raises OS notifications when a run or a background job finishes or the agent asks for input, and one startup check of the published npm version, marked `↑0.12.0` in the header and announced in a transcript notice. DeepSeek is priced out of the box, and `bytefly.json` is the shared config document every extension reads. |
 | [`bytefly-dark`](./themes/bytefly-dark.json) / [`bytefly-light`](./themes/bytefly-light.json) | `/settings` → **Theme** | A GitHub-inspired dark palette and its light companion, with optional automatic light/dark switching. |
 
 ### Screens
@@ -144,9 +146,10 @@ one image per tool under [`assets/tools/`](./assets/tools).
 Most extensions need no configuration. Every setting lives in one shared
 document, `bytefly.json`, read from `<agent-dir>/bytefly.json` and merged with
 `<cwd>/.pi/bytefly.json` (project wins), under a top-level section named for the
-extension. Each extension's `README.md` lists its keys,
-[`docs/configuration.md`](./docs/configuration.md) indexes them, and
-[`assets/bytefly.schema.json`](./assets/bytefly.schema.json) validates the file.
+extension. Each extension's `README.md` covers the behaviour around its keys,
+[`docs/configuration.md`](./docs/configuration.md) indexes the sections, and
+[`docs/references/configuration-reference.md`](./docs/references/configuration-reference.md) lists
+every key with its type, default, and bounds.
 
 Every extension is on by default. To load the pack without some of them, set
 `PI_DISABLED_EXTENSIONS` to a comma- or whitespace-separated list of extension
@@ -167,9 +170,11 @@ stops the factories from registering; to drop the whole package, use Pi's
 | [Getting started](./docs/getting-started.md) | Requirements, install options, verifying the load, themes. |
 | [Extensions](./docs/extensions.md) | The full catalog of every extension and theme. |
 | [Configuration](./docs/configuration.md) | Config-file resolution, the per-extension index, environment variables. |
+| [Configuration reference](./docs/references/configuration-reference.md) | Every `bytefly.json` section and key, with its type, default, and bounds. |
 | [Architecture](./docs/architecture.md) | How the package, its extensions, and `lib/` fit together. |
 | [Development](./docs/development.md) | Local setup, checks, tests, cross-platform notes, and the release process. |
 | [Security](./docs/security.md) | Trust boundaries for the loopback and remote surfaces. |
+| [Roadmap](./ROADMAP.md) | Where the pack is going, grouped by the README's promises, with the evidence behind each item. |
 
 ## Requirements
 

package/README.zh-CN.md

@@ -104,7 +104,7 @@ pi -e .                                                    # 试运行一次
 
 | 扩展 | 工具与命令 | 说明 |
 |---|---|---|
-| [`bytefly`](./extensions/bytefly/) | `/bytefly`（`doctor`、`settings` 子命令）、`run_doctor` | 主题化头部与宽度自适应页脚、每条用户消息上方的两行 `You` 铭牌、已完成回合之间的分隔线、共享的转录通知、以调用行为标题并将结果正文挂在轨道下两列的工具块（轨道字形由 `chrome.rail` 设置）、Pi 工作行上的实时用时计数、`/bytefly` 控制中心——Extensions 区列出每个扩展及其健康状况并启用或禁用一个扩展，另有一个 Settings 区，提供五项常用偏好（`/bytefly settings`）；`/bytefly doctor` 打印 doctor 报告；以及可选的 `notify` 能力：当一次运行或后台任务结束、或智能体请求输入时发出系统通知。DeepSeek 开箱即定价，`bytefly.json` 是每个扩展都会读取的共享配置文档。 |
+| [`bytefly`](./extensions/bytefly/) | `/bytefly`（`doctor`、`settings` 子命令）、`run_doctor` | 主题化头部与宽度自适应页脚、每条用户消息上方的两行 `You` 铭牌、已完成回合之间的分隔线、共享的转录通知、以调用行为标题并将结果正文挂在轨道下两列的工具块（轨道字形由 `chrome.rail` 设置）、Pi 工作行上的实时用时计数、`/bytefly` 控制中心——Extensions 区列出每个扩展及其健康状况并启用或禁用一个扩展，另有一个 Settings 区，按六个分组提供十项常用偏好（`/bytefly settings`）；`/bytefly doctor` 打印 doctor 报告；以及可选的 `notify` 能力：当一次运行或后台任务结束、或智能体请求输入时发出系统通知；另外每次交互式会话启动时会检查 npm 上已发布的版本，落后时在头部标出 `↑0.12.0` 并发出一次转录通知。DeepSeek 开箱即定价，`bytefly.json` 是每个扩展都会读取的共享配置文档。 |
 | [`bytefly-dark`](./themes/bytefly-dark.json) / [`bytefly-light`](./themes/bytefly-light.json) | `/settings` → **Theme** | GitHub 风格的深色调色板及其浅色搭档，并支持可选的自动浅色/深色切换。 |
 
 ### 截图
@@ -136,9 +136,10 @@ pi -e .                                                    # 试运行一次
 
 大多数扩展无需配置。所有设置都在一个共享文档 `bytefly.json` 中，从
 `<agent-dir>/bytefly.json` 读取，并与 `<cwd>/.pi/bytefly.json` 合并（项目优先），
-位于一个以扩展名命名的顶层 section 下。每个扩展的 `README.md` 列出它的键，
+位于一个以扩展名命名的顶层 section 下。每个扩展的 `README.md` 说明其键位的行为，
 [`docs/configuration.md`](./docs/configuration.md) 为其建立索引，
-[`assets/bytefly.schema.json`](./assets/bytefly.schema.json) 校验该文件。
+[`docs/references/configuration-reference.md`](./docs/references/configuration-reference.md) 逐个列出每个键的
+类型、默认值和取值范围。
 
 每个扩展默认都开启。若要在加载整包时排除其中一些，把 `PI_DISABLED_EXTENSIONS`
 设为一个以逗号或空白分隔的扩展名列表（即 [`extensions/`](./extensions/) 下的目录
@@ -161,6 +162,7 @@ Pi 的 `--no-extensions`，或从你的设置中删除该包。
 | [架构](./docs/architecture.md) | 包、各扩展与 `lib/` 如何协同。 |
 | [开发](./docs/development.md) | 本地设置、检查、测试、跨平台注意事项与发布流程。 |
 | [安全](./docs/security.md) | 回环与远程界面的信任边界。 |
+| [路线图](./ROADMAP.md) | 包的下一步方向，按 README 的承诺分组，并列出每条事项的依据。 |
 
 ## 环境要求