@gavin-hu/my-pi-agent 0.19.0 → 0.21.0

package/README.md

@@ -15,7 +15,7 @@ This page is the catalog and the setup instructions. For how to use a feature
 the keys, the commands, and what you should see — start with the
 [user guide](./docs/user-guide/).
 
-![A terminal window running the Pi TUI: the bytefly header naming Pi and bytefly's versions, three key-hint rows, a nameplated message with its answer and an edit diff behind the rail, a finished-jobs notice, the turn rule, the goal and todo rails, and the two-line footer](assets/screens/chrome.png)
+![A terminal window running the Pi TUI: the bytefly header naming Pi and bytefly's versions, three key-hint rows, a nameplated message with its answer and an edit diff behind the rail, a notice that two background jobs finished, naming the test run that passed and the build that failed, the turn rule, the goal and todo rails, the input editor with a half-typed request between its two rules, and the two-line footer — the plan chip and the branch above, the context gauge, the priced cost against its $5 budget, and the model below](assets/screens/chrome.png)
 
 ## Contents
 
@@ -71,16 +71,22 @@ Windows, macOS, and Linux all work, and the full check suite runs on each in CI.
 
 Then, from inside Pi:
 
-- `/bytefly [extension] [refresh]` opens the control center on Extensions, lists
-  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: one flat list
-  of the twelve preferences a session changes, each with its value beside the
-  label, `Space`/`Enter` to change one and `Tab` for Global/Project scope. Every
-  other key is a `bytefly.json` edit, listed in the configuration reference.
+- `/bytefly [extension] [refresh]` opens the control center on Extensions: one
+  frame for all three sections, its header rule carrying the attention at the
+  right (or `all clear`), a tab row with each section's count and the write scope.
+  It lists every loaded extension by name, with a checkbox and at most one
+  verdict word, enables or disables one, and clears a project override with `x`;
+  `/` filters the rows, `!` keeps only what needs attention, and `?` shows every
+  key.
+- `/bytefly settings` opens the control center's Settings section: the twelve
+  preferences a session changes, grouped under Startup, Notifications, Session,
+  and Price with each value in an aligned column, `Space`/`Enter` to change one
+  and `s` for Global/Project scope. Every other key is a `bytefly.json` edit,
+  listed in the configuration reference.
 - `/bytefly skills` opens the control center's Skills section: one row per Pi
-  skill with its enable checkbox, its declared description underneath, and
-  `Space` to switch it on or off for the active scope.
+  skill with its enable checkbox and at most one verdict word, what its `SKILL.md`
+  declares in the block beside it, and `Space` to switch it on or off for the
+  active 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.
@@ -102,7 +108,7 @@ document. `PI_OFFLINE` skips the check;
 
 ## What you get
 
-21 extensions, 4 packaged skills, and 2 themes, grouped by the promises the
+22 extensions, 4 packaged skills, and 2 themes, grouped by the promises the
 [roadmap](./ROADMAP.md) tracks; the [guide](./docs/user-guide/) covers the same
 ground chapter by chapter. Each extension's own page in `docs/extensions/` has
 the full tool and command surface, opening with its capabilities.
@@ -120,7 +126,8 @@ the full tool and command surface, opening with its capabilities.
 | [`job`](./docs/extensions/job.md) | `job`, `/jobs` | Run long-lived shell commands in the background; inspect logs, wait, or kill them. |
 | [`watch`](./docs/extensions/watch.md) | `watch`, `/watch` | Tail a file or command output, match lines against patterns, and alert you or hand matching lines to the agent. |
 | [`session-bus`](./docs/extensions/session-bus.md) | `session`, `/sessions` (screen) | Coordinate parallel Pi sessions on one repository: discover peers, exchange short messages/events, consume an inbox, or claim paths before editing, with `/sessions` as a live board of peers, unread mail, and claims. Local, pull-based by default, with an opt-in inbox watch that raises this session's turn once it is idle; it never spawns an agent. |
-| [`board`](./docs/extensions/board.md) | `board`, `/board` | One shared feature board per repository: a card per feature, which any session claims, moves, edits, notes, and finishes, and one loopback page that shows the same cards live in a **Board** and a **Team** tab. The page serves as the seat `team-lead`, so a second session opens it read-only instead of starting a rival one. A card can carry a priority, name the cards it waits on, and be handed to a teammate from the dashboard. Steps stay in the owner's plan and `todo`; a card is the feature, its owner, and the history that explains it. `board.port` in `bytefly.json` pins the page's port, so a bookmarked URL survives a restart. |
+| [`serve`](./docs/extensions/serve.md) | — | The session's one loopback server. `/board`, `/browse`, and a browser plan review mount path prefixes on it instead of binding their own listeners, so a session has one port, one chip, and one close path — and a second session (a peer conversation, another worktree, another Pi) still gets its own. `serve.port` in `bytefly.json` pins that port, so a bookmarked URL survives a restart, and a shared review borrows exactly one LAN address for the one page that asked. |
+| [`board`](./docs/extensions/board.md) | `board`, `/board` | One shared feature board per repository: a card per feature, which any session claims, moves, edits, notes, finishes, and archives — a finished card leaves the board for an `archive/` pile with its notes and landed commit still readable, so a long history stops costing every read — and one loopback page that shows the same cards live in a **Board** and a **Team** tab. The page is a read view — the tools are the only writers — served as the seat `team-lead`, so a second session opens the same page instead of starting a rival one, and handing a card to a teammate is `team`'s job because only it can message them. A card can carry a priority and name the cards it waits on. Steps stay in the owner's plan and `todo`; a card is the feature, its owner, and the history that explains it. The page answers at `/board` on the session's one port, so `serve.port` is the address to bookmark. |
 | [`team`](./docs/extensions/team.md) | `team`, `/team` | The lead's round over the same board. `/team join <label>` puts a session on the team, and `/board` does it for the lead as `team-lead`; then `assign` hands a feature to a running session, `offer` hands one to whoever is free — a broadcast that writes nothing, claimed by the first taker — and `reclaim` takes a card back to To do. A result says who will be woken for it and who will read it at their next turn, `/team` prints the round in the terminal without a browser, and nothing is spawned. |
 | [`context`](./docs/extensions/context.md) | `/context` | Show where the context window goes — system prompt, tool definitions, conversation by role, injected notes — and compact from the report with the before and after numbers. |
 

package/README.zh-CN.md

@@ -13,7 +13,7 @@
 本页是目录与安装说明。要了解某个功能怎么用 —— 按键、命令以及应有的效果 ——
 请先看[用户指南](./docs/user-guide/)。
 
-![一个运行 Pi TUI 的终端窗口：bytefly 头部标出 Pi 与 bytefly 的版本、三行按键提示、带名板的消息及其回答与编辑差异（位于竖线内）、后台任务完成通知、回合分隔线、目标与待办栏，以及两行页脚](assets/screens/chrome.png)
+![一个运行 Pi TUI 的终端窗口：bytefly 头部标出 Pi 与 bytefly 的版本、三行按键提示、带名板的消息及其回答与编辑差异（位于竖线内）、两个后台任务完成的通知（一个通过的测试任务与一个失败的构建任务）、回合分隔线、目标与待办栏、夹在两条横线之间且已输入半句的输入框，以及两行页脚（上下文指示、按价目计算的费用、模型名）](assets/screens/chrome.png)
 
 ## 目录
 
@@ -63,13 +63,18 @@ Windows、macOS 和 Linux 均可运行，完整检查套件在每个平台上都
 
 然后在 Pi 中：
 
-- `/bytefly [extension] [refresh]` 打开控制中心的 Extensions 区，列出每个已加载扩展
-  及其运行时健康状况，启用或禁用一个扩展，并用 `x` 清除项目级覆盖。
-- `/bytefly settings` 打开控制中心的 Settings 区：一次会话会改动的十二项设置排成
-  一列，值紧跟在名称之后；用 `Space`/`Enter` 修改，用 `Tab` 切换 Global/Project
-  作用域。其余键都是 `bytefly.json` 编辑，见配置参考。
+- `/bytefly [extension] [refresh]` 打开控制中心的 Extensions 区：三个区共用一个
+  框架，头部横线的右端写着需要注意的事项（没有问题时为 `all clear`），一行 tab
+  标出各区的数量与写入作用域。它按名称列出每个已加载扩展及其复选框与至多一个
+  结论词，启用或禁用一个扩展，并用 `x` 清除项目级覆盖；`/` 过滤行，`!` 只保留
+  需要注意的行，`?` 显示全部按键。
+- `/bytefly settings` 打开控制中心的 Settings 区：一次会话会改动的十二项设置按
+  Startup、Notifications、Session、Price 四组排列，值对齐在同一列；用
+  `Space`/`Enter` 修改一项，用 `s` 切换 Global/Project 作用域。其余键都是
+  `bytefly.json` 编辑，见配置参考。
 - `/bytefly skills` 打开控制中心的 Skills 区：每个 Pi 技能一行，带启用复选框与
-  `SKILL.md` 声明的描述，用 `Space` 在当前作用域开关它。
+  至多一个结论词，`SKILL.md` 声明的描述显示在旁边的区块中，用 `Space` 在当前
+  作用域开关它。
 - `/bytefly doctor [extension] [refresh]` 打印 doctor 报告（`run_doctor` 的文本），
   检查每个已启用扩展在运行时是否具备所需条件。
 - `/bytefly update` 立即重跑包更新检查，报告可更新的包、本包版本与 release URL，
@@ -87,7 +92,7 @@ Pi 自己的版本请求只是被重新绘制，本包的最新版本则来自
 
 ## 包含内容
 
-21 个扩展、4 个随包技能，以及 2 个主题，按 [路线图](./ROADMAP.md) 追踪的承诺分组；
+22 个扩展、4 个随包技能，以及 2 个主题，按 [路线图](./ROADMAP.md) 追踪的承诺分组；
 [用户指南](./docs/user-guide/) 按章节讲述同样的内容。每个扩展在 `docs/extensions/`
 下的页面提供完整的工具与命令说明，并以能力表开头。
 
@@ -104,7 +109,8 @@ Pi 自己的版本请求只是被重新绘制，本包的最新版本则来自
 | [`job`](./docs/extensions/job.md) | `job`, `/jobs` | 在后台运行长时 shell 命令；查看日志、等待或结束它们。 |
 | [`watch`](./docs/extensions/watch.md) | `watch`, `/watch` | 跟踪文件或命令输出，按模式匹配行，并提醒你或把匹配的行交给智能体。 |
 | [`session-bus`](./docs/extensions/session-bus.md) | `session`, `/sessions`（屏幕） | 在同一仓库的多个 Pi 会话之间协调：发现彼此、交换简短消息/事件、读取收件箱、编辑前声明路径；`/sessions` 是显示对等会话、未读邮件和路径声明的实时面板。本地、默认拉取式；收件箱监视需会话自行开启，空闲时会唤起本会话的一轮，从不创建智能体。 |
-| [`board`](./docs/extensions/board.md) | `board`、`/board` | 每个仓库一块共享看板：一张卡片代表一个 feature，任何 session 都可以认领、移动、编辑、加注、完成它；同一个看板在浏览器里以 **Board** 和 **Team** 两个 tab 实时显示。看板以固定席位 `team-lead` 对外服务，因此第二个 session 打开的是同一块看板（只读），而不是另起一个。卡片可以带上优先级、声明自己在等待哪几张卡片，也可以在看板里交给某个队友。步骤留在 owner 的 plan 和 `todo` 里，卡片就是 feature、它的 owner，以及解释它的历史。在 `bytefly.json` 里设置 `board.port` 可以固定看板端口，收藏的地址在重启后依然有效。 |
+| [`serve`](./docs/extensions/serve.md) | — | 每个 session 一个 loopback 服务。`/board`、`/browse` 和浏览器里的 plan review 都在它上面挂载路径前缀，而不是各自监听端口，因此一个 session 只有一个端口、一个 chip、一条关闭路径——而第二个 session（peer 会话、另一个 worktree、另一个 Pi）依然有自己的端口。`bytefly.json` 里的 `serve.port` 可以固定该端口，收藏的地址在重启后依然有效；共享 review 只为发起共享的那一个页面借用同一个网段上的一个地址。 |
+| [`board`](./docs/extensions/board.md) | `board`、`/board` | 每个仓库一块共享看板：一张卡片代表一个 feature，任何 session 都可以认领、移动、编辑、加注、完成、归档——已完成的卡片会离开看板进入 `archive/`，其注记与落地 commit 仍可读，长历史不再拖累每次读取——同一个看板在浏览器里以 **Board** 和 **Team** 两个 tab 实时显示。页面只读——写入只走工具——并以固定席位 `team-lead` 对外服务，因此第二个 session 打开的是同一张页面，而不是另起一个；把卡片交给队友由 `team` 负责，因为只有它能给对端发消息。卡片可以带上优先级、声明自己在等待哪几张卡片。步骤留在 owner 的 plan 和 `todo` 里，卡片就是 feature、它的 owner，以及解释它的历史。页面以 `/board` 挂在该 session 唯一的端口上，所以收藏时用 `serve.port`。 |
 | [`team`](./docs/extensions/team.md) | `team`、`/team` | 同一块看板上的 lead 轮次。`/team join <label>` 让一个 session 加入团队，lead 打开 `/board` 时则以 `team-lead` 自动加入；随后 `assign` 把一个 feature 交给运行中的 session，`offer` 交给谁有空谁接——广播而不写卡片，由第一个认领的人拿走——`reclaim` 把卡片收回 To do。结果会说明谁会因此被叫醒、谁会在下一轮才读到；`/team` 在终端里打印同一份轮次，不用开浏览器，也不启动任何进程。 |
 | [`context`](./docs/extensions/context.md) | `/context` | 显示上下文窗口的去向 —— 系统提示、工具定义、按角色拆分的对话、注入的笔记 —— 并从报告中触发压缩，给出压缩前后的数字。 |
 

package/docs/extensions/README.md

@@ -17,7 +17,8 @@ sections behind them.
 | `job` | Long-lived shell commands in the background, with logs and a wait | [`job.md`](./job.md) |
 | `watch` | Tailing a file or command and matching new lines | [`watch.md`](./watch.md) |
 | `session-bus` | Coordination between parallel Pi sessions on one repository | [`session-bus.md`](./session-bus.md) |
-| `board` | One shared feature board per repository, read and written by every session, and one page a lead serves for the team to watch | [`board.md`](./board.md) |
+| `serve` | The session's one loopback server: every page mounts a path prefix on it | [`serve.md`](./serve.md) |
+| `board` | One shared feature board per repository, written by the tools and shown by one page a lead serves | [`board.md`](./board.md) |
 | `team` | The lead's round: hand a card to a running session, take one back, or print it with `/team` | [`team.md`](./team.md) |
 | `context` | Where the context window went, and compacting from the report | [`context.md`](./context.md) |
 | `worktree` | An isolated `git worktree` per task, and the built-in tools following it | [`worktree.md`](./worktree.md) |