@vitos-pizza/vitos-pizza 0.1.0 → 0.2.0

package/AGENTS.md

@@ -1,158 +1,158 @@
-# Vito's Pizzeria — Agent Instructions
-
-This repository is **vitos-pizza**, a [Pi](https://pi.dev/) **distribution** (like LazyVim for Neovim). Users install the repo root once via `pi install .` and get the full curated experience.
-
-Inspired by Vito's Pizzeria from Garfield — one brand, one install.
-
-## Structure
-
-- **Repo root** — The distribution. `package.json` is the pi-package manifest.
-- **`packages/<module>/`** — Built-in modules (e.g. `@vitos-pizza/agent-mode`, `@vitos-pizza/question`, `@vitos-pizza/session-title`, `@vitos-pizza/permission-system`, `@vitos-pizza/subagents`, `@vitos-pizza/keybindings`). Not installed separately by users.
-- **`scripts/sync-pi-manifest.mjs`** — Scans `packages/*`, merges `piBundled` npm packages, and updates root `dependencies` + `pi` manifest. Honors `pi.requires` for extension load order.
-
-## Bundled third-party Pi packages
-
-Declare npm pi packages in root `package.json`:
-
-- `dependencies` — version range
-- `bundledDependencies` — include in the distribution tarball
-- `piBundled` — list read by `sync-pi-manifest.mjs` to merge `node_modules/<pkg>/` paths into the root `pi` manifest
-
-Extension load order: topological sort of `pi.requires`, with `LOCAL_ORDER` tie-break. Default: `permission-system` → `question` → `ui-enhancements` → `agent-mode` → `subagents` → `session-title` → `keybindings`.
-
-## Agent mode
-
-Vito's Pizzeria uses three centralized modes via **`@vitos-pizza/agent-mode`**:
-
-| Mode | Permissions | Behavior |
-|------|-------------|----------|
-| `agent` | `default` preset | Balanced daily work |
-| `plan` | `plan` preset | Read-only; scout → planner via subagents + `question` |
-| `execute` | `yolo` preset | Minimal gates; full implementation |
-
-Switch with `/mode [agent|plan|execute]` or **`F6`** (`agent-mode.cycle`). Current mode appears in the ui-enhancements border bar (`· plan` / `· execute`).
-
-## Keyboard shortcuts
-
-Pi already provides built-in keybindings (`~/.pi/agent/keybindings.json`, namespaced `app.*` / `tui.*`) and extension shortcuts via `pi.registerShortcut()`.
-
-**vitos-pizza convention:** only `@vitos-pizza/keybindings` may call `pi.registerShortcut`. Other modules register **actions** (not keys) during `session_start`:
-
-```typescript
-import { emitShortcutAction } from "@vitos-pizza/keybindings/types";
-
-// session_start — register handler only; keys come from vitos-shortcuts.json
-emitShortcutAction(pi.events, {
-  id: "agent-mode.cycle",
-  description: "Cycle agent mode (agent → plan → execute)",
-  handler: async (ctx) => { /* ... */ },
-});
-```
-
-Key config (project overrides global overrides preset defaults):
-
-- `packages/keybindings/presets/shortcuts.json` — distribution defaults
-- `~/.pi/agent/vitos-shortcuts.json` — user global overrides
-- `<cwd>/.pi/vitos-shortcuts.json` — project overrides
-
-Use `/vitos-shortcuts` to list registered actions and current bindings. Pi built-in shortcuts remain in `/hotkeys` and `keybindings.json`.
-
-Each module follows Pi conventions:
-
-```
-packages/<module>/
-├── extensions/     # TypeScript (*.ts)
-├── skills/         # */SKILL.md (optional)
-├── prompts/        # *.md slash templates (optional)
-└── themes/         # *.json (optional)
-```
-
-## Adding a module
-
-1. Create `packages/<name>/` with `package.json` (`"name": "@vitos-pizza/<name>"`).
-2. Optional: declare `"pi": { "requires": ["@vitos-pizza/other-module"] }` so sync orders extensions correctly.
-3. Add extensions, skills, prompts, or themes as needed.
-4. If you referenced external open source, add an **Acknowledgments** row in [README.md](README.md) (see **Open-source acknowledgments** below).
-5. Run `npm run sync && npm install` at repo root.
-6. Reload Pi with `/reload` or `pi install .`.
-
-## Dependency rules
-
-- **Pi core packages** (`@earendil-works/pi-coding-agent`, `@earendil-works/pi-agent-core`, `@earendil-works/pi-ai`, `@earendil-works/pi-tui`, `typebox`) → `peerDependencies: "*"` only.
-- **Third-party runtime deps** → `dependencies` in the module that uses them.
-
-## Subagent delegation
-
-All child-agent work in vitos-pizza modules must go through **`@vitos-pizza/subagents`** — use `requestSubagentRun` / `requestSubagentWait` from `@vitos-pizza/subagents/rpc/client` on `pi.events`. Do not call `completeSimple` or spawn `pi` directly for delegated agent runs.
-
-Declare `"pi": { "requires": ["@vitos-pizza/subagents"] }` in the consuming module's `package.json` so extension load order is correct.
-
-## Ask-user questions
-
-Structured clarification (multiple-choice UI) uses **`@vitos-pizza/question`** — the `question` tool. Main sessions show the TUI directly; subagent children forward prompts to the parent session (events RPC + file fallback). Planner and scout agents include `question` in their `tools:` list.
-
-## Open-source acknowledgments
-
-Whenever work **references, adapts, or depends on** external open source, add or update an entry in [README.md](README.md) → **Acknowledgments**. Do this in the **same PR** as the feature or dependency change — not as a follow-up.
-
-**Must acknowledge:**
-
-- Pi extensions / npm packages you read, port patterns from, or bundle (`piBundled`, `dependencies`)
-- GitHub repos or docs used as implementation reference (even if reimplemented in-tree)
-- New runtime `dependencies` in any `packages/*/package.json`
-- UX or architecture inspiration with a named upstream (e.g. Claude Code–style presets)
-
-**Do not** list every transitive npm package — only direct references and meaningful upstreams.
-
-**Where to put each entry** (keep existing subsection structure):
-
-| Kind | README subsection |
-|------|-------------------|
-| Platform / distribution model | `### Platform & distribution model` |
-| Feature reference, port, or bundled Pi package | `### Features referenced or adapted` |
-| Direct runtime or dev tooling dependency | `### Runtime & tooling libraries` |
-
-**Row format** (match existing tables):
-
-```markdown
-| [Project name](https://…/) | `@vitos-pizza/<module>` or area | One line: what we took or how we use it |
-```
-
-For libraries, the Link column can hold the homepage; for features, link the repo, npm page, or Pi package catalog URL.
-
-**Adding a module checklist** — in addition to sync/install, if the module references upstream work, extend README Acknowledgments before merging.
-
-## Development
-
-- No build step — Pi loads TypeScript via jiti.
-- After editing extensions: `/reload`.
-- Type-check: `npm run typecheck`
-- Test: `npm run test`
-- Lint: `npm run lint`
-
-## Plan documents
-
-Feature plans should include a short **`## 功能验收`** section (3–6 checkboxes) between the implementation approach and risks/constraints. Each item states an observable outcome, e.g. `xxx 功能已实现：<what the user can verify>`. Implementation is not done until every item can be answered yes/no.
-
-If the plan references external open source, include a checkbox: `README Acknowledgments 已更新（如有上游参考）`.
-
-## Install
-
-```bash
-pi install .           # global settings
-pi install -l .        # project .pi/settings.json
-pi -e .                # try without installing
-```
-
-## Extension API
-
-```typescript
-import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
-
-export default function (pi: ExtensionAPI) {
-  pi.registerCommand("hello", { /* ... */ });
-  pi.on("session_start", async (_event, ctx) => { /* ... */ });
-}
-```
-
-See [Pi Extensions docs](https://pi.dev/docs/latest/extensions).
+# Vito's Pizzeria — Agent Instructions
+
+This repository is **vitos-pizza**, a [Pi](https://pi.dev/) **distribution** (like LazyVim for Neovim). Users install the repo root once via `pi install .` and get the full curated experience.
+
+Inspired by Vito's Pizzeria from Garfield — one brand, one install.
+
+## Structure
+
+- **Repo root** — The distribution. `package.json` is the pi-package manifest.
+- **`packages/<module>/`** — Built-in modules (e.g. `@vitos-pizza/agent-mode`, `@vitos-pizza/question`, `@vitos-pizza/session-title`, `@vitos-pizza/permission-system`, `@vitos-pizza/subagents`, `@vitos-pizza/keybindings`). Not installed separately by users.
+- **`scripts/sync-pi-manifest.mjs`** — Scans `packages/*`, merges `piBundled` npm packages, and updates root `dependencies` + `pi` manifest. Honors `pi.requires` for extension load order.
+
+## Bundled third-party Pi packages
+
+Declare npm pi packages in root `package.json`:
+
+- `dependencies` — version range
+- `bundledDependencies` — include in the distribution tarball
+- `piBundled` — list read by `sync-pi-manifest.mjs` to merge `node_modules/<pkg>/` paths into the root `pi` manifest
+
+Extension load order: topological sort of `pi.requires`, with `LOCAL_ORDER` tie-break. Default: `permission-system` → `question` → `ui-enhancements` → `agent-mode` → `subagents` → `session-title` → `keybindings`.
+
+## Agent mode
+
+Vito's Pizzeria uses three centralized modes via **`@vitos-pizza/agent-mode`**:
+
+| Mode | Permissions | Behavior |
+|------|-------------|----------|
+| `agent` | `default` preset | Balanced daily work |
+| `plan` | `plan` preset | Read-only; scout → planner via subagents + `question` |
+| `execute` | `yolo` preset | Minimal gates; full implementation |
+
+Switch with `/mode [agent|plan|execute]` or **`F6`** (`agent-mode.cycle`). Current mode appears in the ui-enhancements border bar (`· plan` / `· execute`).
+
+## Keyboard shortcuts
+
+Pi already provides built-in keybindings (`~/.pi/agent/keybindings.json`, namespaced `app.*` / `tui.*`) and extension shortcuts via `pi.registerShortcut()`.
+
+**vitos-pizza convention:** only `@vitos-pizza/keybindings` may call `pi.registerShortcut`. Other modules register **actions** (not keys) during `session_start`:
+
+```typescript
+import { emitShortcutAction } from "@vitos-pizza/keybindings/types";
+
+// session_start — register handler only; keys come from vitos-shortcuts.json
+emitShortcutAction(pi.events, {
+  id: "agent-mode.cycle",
+  description: "Cycle agent mode (agent → plan → execute)",
+  handler: async (ctx) => { /* ... */ },
+});
+```
+
+Key config (project overrides global overrides preset defaults):
+
+- `packages/keybindings/presets/shortcuts.json` — distribution defaults
+- `~/.pi/agent/vitos-shortcuts.json` — user global overrides
+- `<cwd>/.pi/vitos-shortcuts.json` — project overrides
+
+Use `/vitos-shortcuts` to list registered actions and current bindings. Pi built-in shortcuts remain in `/hotkeys` and `keybindings.json`.
+
+Each module follows Pi conventions:
+
+```
+packages/<module>/
+├── extensions/     # TypeScript (*.ts)
+├── skills/         # */SKILL.md (optional)
+├── prompts/        # *.md slash templates (optional)
+└── themes/         # *.json (optional)
+```
+
+## Adding a module
+
+1. Create `packages/<name>/` with `package.json` (`"name": "@vitos-pizza/<name>"`).
+2. Optional: declare `"pi": { "requires": ["@vitos-pizza/other-module"] }` so sync orders extensions correctly.
+3. Add extensions, skills, prompts, or themes as needed.
+4. If you referenced external open source, add an **Acknowledgments** row in [README.md](README.md) (see **Open-source acknowledgments** below).
+5. Run `npm run sync && npm install` at repo root.
+6. Reload Pi with `/reload` or `pi install .`.
+
+## Dependency rules
+
+- **Pi core packages** (`@earendil-works/pi-coding-agent`, `@earendil-works/pi-agent-core`, `@earendil-works/pi-ai`, `@earendil-works/pi-tui`, `typebox`) → `peerDependencies: "*"` only.
+- **Third-party runtime deps** → `dependencies` in the module that uses them.
+
+## Subagent delegation
+
+All child-agent work in vitos-pizza modules must go through **`@vitos-pizza/subagents`** — use `requestSubagentRun` / `requestSubagentWait` from `@vitos-pizza/subagents/rpc/client` on `pi.events`. Do not call `completeSimple` or spawn `pi` directly for delegated agent runs.
+
+Declare `"pi": { "requires": ["@vitos-pizza/subagents"] }` in the consuming module's `package.json` so extension load order is correct.
+
+## Ask-user questions
+
+Structured clarification (multiple-choice UI) uses **`@vitos-pizza/question`** — the `question` tool. Main sessions show the TUI directly; subagent children forward prompts to the parent session (events RPC + file fallback). Planner and scout agents include `question` in their `tools:` list.
+
+## Open-source acknowledgments
+
+Whenever work **references, adapts, or depends on** external open source, add or update an entry in [README.md](README.md) → **Acknowledgments**. Do this in the **same PR** as the feature or dependency change — not as a follow-up.
+
+**Must acknowledge:**
+
+- Pi extensions / npm packages you read, port patterns from, or bundle (`piBundled`, `dependencies`)
+- GitHub repos or docs used as implementation reference (even if reimplemented in-tree)
+- New runtime `dependencies` in any `packages/*/package.json`
+- UX or architecture inspiration with a named upstream (e.g. Claude Code–style presets)
+
+**Do not** list every transitive npm package — only direct references and meaningful upstreams.
+
+**Where to put each entry** (keep existing subsection structure):
+
+| Kind | README subsection |
+|------|-------------------|
+| Platform / distribution model | `### Platform & distribution model` |
+| Feature reference, port, or bundled Pi package | `### Features referenced or adapted` |
+| Direct runtime or dev tooling dependency | `### Runtime & tooling libraries` |
+
+**Row format** (match existing tables):
+
+```markdown
+| [Project name](https://…/) | `@vitos-pizza/<module>` or area | One line: what we took or how we use it |
+```
+
+For libraries, the Link column can hold the homepage; for features, link the repo, npm page, or Pi package catalog URL.
+
+**Adding a module checklist** — in addition to sync/install, if the module references upstream work, extend README Acknowledgments before merging.
+
+## Development
+
+- No build step — Pi loads TypeScript via jiti.
+- After editing extensions: `/reload`.
+- Type-check: `npm run typecheck`
+- Test: `npm run test`
+- Lint: `npm run lint`
+
+## Plan documents
+
+Feature plans should include a short **`## 功能验收`** section (3–6 checkboxes) between the implementation approach and risks/constraints. Each item states an observable outcome, e.g. `xxx 功能已实现：<what the user can verify>`. Implementation is not done until every item can be answered yes/no.
+
+If the plan references external open source, include a checkbox: `README Acknowledgments 已更新（如有上游参考）`.
+
+## Install
+
+```bash
+pi install .           # global settings
+pi install -l .        # project .pi/settings.json
+pi -e .                # try without installing
+```
+
+## Extension API
+
+```typescript
+import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
+
+export default function (pi: ExtensionAPI) {
+  pi.registerCommand("hello", { /* ... */ });
+  pi.on("session_start", async (_event, ctx) => { /* ... */ });
+}
+```
+
+See [Pi Extensions docs](https://pi.dev/docs/latest/extensions).

package/CHANGELOG.md

@@ -1,24 +1,42 @@
-# Changelog
-
-All notable changes to vitos-pizza are documented here.
-
-## [0.1.0] - 2026-07-10
-
-### Added
-
-- Rebrand from xin-pi to **vitos-pizza** (维多披萨 / Vito's Pizzeria)
-- Pi distribution layout: repo root as single install entry
-- `scripts/sync-pi-manifest.mjs` module assembler
-- Original logo at `assets/logo.svg`
-
-### Removed
-
-- Nested `packages/xin-pi` aggregator
-- `@xin-pi/core`, template scaffold, postinstall symlink hack
-
-### Publishing
-
-- GitHub Actions publishes `@vitos-pizza/vitos-pizza` via **npm Trusted Publishing (OIDC)** — no long-lived `NPM_TOKEN`
-- Workflow: `.github/workflows/publish.yml` (triggers on `v*` tags / `workflow_dispatch`)
-- `scripts/prepare-publish.mjs` rewrites `file:` workspace deps for the npm tarball
-- First package version must be published once manually (or as a stub) before Trusted Publisher can be configured on npmjs.com
+# Changelog
+
+All notable changes to vitos-pizza are documented here.
+
+## [0.2.0] - 2026-07-11
+
+### Added
+
+- **`@vitos-pizza/todoist`** — in-memory task list with TUI widget, `/todo` command, and LLM tools (`todo_add` / `todo_update` / `todo_complete` / `todo_delete`)
+- Terminal **resize recovery** in ui-enhancements — debounce + full redraw after resize (fixes blank/corrupt TUI on Windows)
+- Plan-mode **Next** footer guidance and optional scout (skip recon when context is enough; parallel scouts for independent areas)
+
+### Changed
+
+- Permission system: tool activation starts from **all registered tools** (`getAllTools`) so leaving plan mode restores write/edit/bash
+- Plan instructions: require `question` for mutually exclusive choices; clarify scout → planner delegation paths
+- Question UI: width cache / render fixes for more stable TUI layout
+
+### Fixed
+
+- Permission gate / evaluator edge cases covered by new tests (`before-agent-start`, gates, evaluator)
+
+## [0.1.0] - 2026-07-10
+
+### Added
+
+- Rebrand from xin-pi to **vitos-pizza** (维多披萨 / Vito's Pizzeria)
+- Pi distribution layout: repo root as single install entry
+- `scripts/sync-pi-manifest.mjs` module assembler
+- Original logo at `assets/logo.svg`
+
+### Removed
+
+- Nested `packages/xin-pi` aggregator
+- `@xin-pi/core`, template scaffold, postinstall symlink hack
+
+### Publishing
+
+- GitHub Actions publishes `@vitos-pizza/vitos-pizza` via **npm Trusted Publishing (OIDC)** — no long-lived `NPM_TOKEN`
+- Workflow: `.github/workflows/publish.yml` (triggers on `v*` tags / `workflow_dispatch`)
+- `scripts/prepare-publish.mjs` rewrites `file:` workspace deps for the npm tarball
+- First package version must be published once manually (or as a stub) before Trusted Publisher can be configured on npmjs.com

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 vitos-pizza contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 vitos-pizza contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.