@agimon-ai/doompi 0.0.1-alpha.21 → 0.0.1-alpha.22

package/README.md

@@ -1,4 +1,4 @@
-# Doompi
+# DoomPi
 
 **A coding agent that loads only the skills and tools you name.**
 
@@ -6,14 +6,15 @@
 > wakes up with database tools, browser controls, and their small novel of schemas. This
 > is our config.
 
-Doompi is a configuration framework for [Pi](https://github.com/earendil-works/pi)
-tailored for people whose agent has one MCP server too many. It turns extensions, skills,
+DoomPi is an opinionated, composable distribution of [Pi](https://github.com/earendil-works/pi). It is closer
+in spirit to Spacemacs, Doom Emacs, or a curated Neovim setup than to a single plugin. It is tailored
+for people whose agent has one MCP server too many. It turns extensions, skills,
 MCP servers, and system prompts into config instead of background noise.
 
-![Doompi terminal interface showing tasks, Plan mode, and the Leader menu](https://cdn.jsdelivr.net/npm/@agimon-ai/doompi@latest/assets/doompi-tui.png)
+![DoomPi terminal interface showing tasks, Plan mode, and the Leader menu](https://cdn.jsdelivr.net/npm/@agimon-ai/doompi@latest/assets/doompi-tui.png)
 
 Plugin systems scope what an agent knows. Nothing scopes what it can reach. Claude Code's
-`enableAllProjectMcpServers` and static denylist are repository-wide. Doompi draws that
+`enableAllProjectMcpServers` and static denylist are repository-wide. DoomPi draws that
 boundary around the session. Pick a major mode and some domains; add a profile if you want
 one. Four YAML files decide what loads; `doompi --explain` tells you what got in, why, and
 what it costs before launch.
@@ -30,6 +31,14 @@ npm install -g @agimon-ai/doompi
 
 The package pins and installs the upstream Pi version used by `dpi`.
 
+## Status and requirements
+
+DoomPi is alpha software. Configuration and package boundaries may still change between alpha releases.
+
+- Node.js 22.19.0 or newer
+- macOS or Linux on arm64 or x64 for the bundled Runner backend
+- Pi 0.84.2 and Pi TUI 0.84.2 for packages that declare them as peer requirements
+
 ## Try DoomPi without replacing your Pi setup
 
 `dpi` is the comparison runner. Use it to try DoomPi beside your current `pi` customization
@@ -51,43 +60,14 @@ not register DoomPi in either normal Pi settings file.
 
 ### Sync storage and worktrees
 
-Generated sync artifacts are kept out of the repository at:
-
-```text
-~/.pi/.doom/sync/<repo-label>--<repo-id-32hex>/
-  shared-cache/objects/<full-build-sha256>/
-  worktrees/<worktree-label>--<worktree-id-32hex>/
-```
+DoomPi stores generated sync state under `~/.pi/.doom/sync`, outside the repository. Each
+Git worktree gets isolated runtime state while immutable build artifacts may be shared.
 
-The repository identity comes from Git's canonical common directory, while each
-worktree gets its own identity. Linked worktrees therefore share immutable,
-content-addressed build objects but never share state, `dist`, manifests, staged
-resources, or per-process `run` files. Runtime loading uses only verified artifacts
-materialized in the current worktree directory; it never loads directly from the
-shared cache. The global `~/.pi/.doom/*.yaml` configuration and persistent
-`~/.pi/.doom/plugin-cache` behavior are unchanged.
-
-Older releases may have written state under `<repository>/.pi/doom`. That location
-is a read-only fallback only when the corresponding home-scoped state is absent.
-`doompi sync --check` reports that migration is required, and `doompi sync` rebuilds
-into the home-scoped worktree namespace rather than copying the legacy files. DoomPi
-does not automatically delete legacy, orphaned, or unused generated directories.
-
-For a fair comparison, `dpi` lets Pi merge the same ordinary settings from
-`~/.pi/agent/settings.json` and `<repo>/.pi/settings.json`. It then overlays only these
-DoomPi-owned values in memory:
-
-```json
-{
-  "extensions": ["@agimon-ai/doompi", "!extensions/**"],
-  "themes": ["themes/doom-pi-dark.json"],
-  "theme": "doom-pi-dark",
-  "quietStartup": true
-}
-```
+`dpi` preserves Pi's normal global and repository settings, then applies DoomPi's extension
+and theme settings in memory. It never writes those values to `.pi/settings.json`.
 
-Those four values are never written by `dpi`, including when Pi saves an unrelated option.
-Every other value keeps Pi's normal global/project precedence and trust handling.
+Run `doompi sync --check` to detect stale or legacy state. Run `doompi sync` to rebuild it
+in the current home-scoped layout.
 
 When you are comfortable with DoomPi and no longer need the side-by-side experiment, register
 it for normal Pi:
@@ -108,7 +88,7 @@ doompi --domains analytics --explain
 
 ## Philosophy
 
-An agent does not need every tool for every job. Doompi separates the base session from
+An agent does not need every tool for every job. DoomPi separates the base session from
 the things you switch on for a while: modes choose behavior, domains choose subject
 matter, and profiles choose a point of view.
 
@@ -119,14 +99,14 @@ or whatever else you do. Define as many as you like; only one is active at a tim
 can switch it without leaving the session.
 
 Minor modes are battery-included switches inside that base. They start off, stack freely,
-and keep their model tools and skills out of context until turned on. Doompi ships six:
+and keep their model tools and skills out of context until turned on. DoomPi ships six:
 
-- **Help mode** — expose package-owned guidance only while you need it.
-- **Plan mode** — make the repository read-only while you agree on an approach.
-- **Loop mode** — run a prompt now, then run it again on a schedule.
-- **Goal mode** — keep one objective in view until it is done or dismissed.
-- **Workflow mode** — run jobs with dependencies, timeouts, and artifacts.
-- **Voice mode** — replace typing with local speech.
+- **Help mode:** expose package-owned guidance only while you need it.
+- **Plan mode:** remove Pi's file-editing tools while you agree on an approach.
+- **Loop mode:** run a prompt now, then run it again on a schedule.
+- **Goal mode:** keep one objective in view until it is done or dismissed.
+- **Workflow mode:** run jobs with dependencies, timeouts, and artifacts.
+- **Voice mode:** replace typing with local speech.
 
 ### Domains
 
@@ -143,7 +123,7 @@ plugins:
   entries:
     remote-review:
       source: url
-      url: https://github.com/acme/review-plugin.git
+      url: '<REVIEW_PLUGIN_GIT_URL>'
       ref: v1.2.0
 
 domains:
@@ -213,8 +193,8 @@ Together they can dispatch structured jobs from one live session.
 
 #### Workflows
 
-GitHub Actions already has a decent vocabulary for long jobs, so Doompi reuses it. Each job
-declares the Doompi session it wants. Here, implementation gets coding tools; the release
+GitHub Actions already has a decent vocabulary for long jobs, so DoomPi reuses it. Each job
+declares the DoomPi session it wants. Here, implementation gets coding tools; the release
 note waits for it and gets marketing context plus a brand voice:
 
 ```yaml
@@ -223,21 +203,21 @@ on:
 
 jobs:
   implement:
+    runs-on: ubuntu-latest
     steps:
       - name: Build the feature
         timeout-minutes: 180
-        artifacts: [implementation/report.md]
         interactiveRun:
           default: |
             doompi --major-mode dev --domains development --auto-stop \
               --cwd "$PWD" "$JOB_SYSTEM_PROMPT"
 
   release-note:
+    runs-on: ubuntu-latest
     needs: implement
     steps:
       - name: Write the release note
         timeout-minutes: 30
-        artifacts: [marketing/release-note.md]
         interactiveRun:
           default: |
             doompi --major-mode marketing --domains marketing \
@@ -253,51 +233,65 @@ it. One session becomes the dispatcher instead of the place every job has to fit
 
 ## Features
 
-Doompi is a distribution, not one giant extension. Each package owns one job; shared TUI
+DoomPi is a distribution, not one giant extension. Each package owns one job; shared TUI
 and session contracts make them behave like one. Use the defaults together or replace
 them one at a time.
 
-### Configuration and composition
+### Foundation and interface
+
+#### Configuration and composition
 
 [`@agimon-ai/doompi`][pkg-doompi] is both an extension and the command-line config compiler. `dpi init`
 creates repository config for an isolated experiment, while `doompi init` creates the personal
-config and registers the permanent Pi integration. The sync commands resolve every major mode
-and domain into a distribution Pi can load quickly. A large major mode with 15 extensions adds
-only 400 ms of code startup time.
+config and registers the permanent Pi integration. The sync commands resolve every major mode and domain into a distribution Pi can load quickly.
+
+#### Supporting packages
+
+[`@agimon-ai/doompi-config`][pkg-doompi-config] resolves the four YAML files and exposes the
+configuration API. [`@agimon-ai/doompi-extension-contracts`][pkg-doompi-extension-contracts]
+contains the shared protocol and Leader contracts used by extension authors.
+[`@agimon-ai/doompi-file-edit`][pkg-doompi-file-edit] opens files in the configured editor and
+keeps the edit timeline. [`@agimon-ai/doompi-log`][pkg-doompi-log] collects session events, while
+[`@agimon-ai/doompi-telemetry`][pkg-doompi-telemetry] is the library-level telemetry adapter.
+
+Runner selects one native artifact automatically; do not install these directly:
+[`darwin-arm64`][pkg-rmux-darwin-arm64], [`darwin-x64`][pkg-rmux-darwin-x64],
+[`linux-arm64`][pkg-rmux-linux-arm64], or [`linux-x64`][pkg-rmux-linux-x64].
 
-### Leader key
+#### Leader key
 
 [`@agimon-ai/doompi-ui`][pkg-doompi-ui] turns `SPC` into a map of the available commands. It stays out of
 the way when a draft is not empty, and other packages contribute bindings through one
 leader API instead of hardcoding their own menus.
 
-### Agent team
+### Coordinated work
 
-[`@agimon-ai/doompi-team`][pkg-doompi-team] runs named subagents asynchronously against a shared task board.
-They can work in parallel, message one another, and use the model policy attached to the
-selected Team package entry. `SPC a l` lists available agents; `SPC a r` opens current-session runs and
-their controls.
+#### Agent team
 
-### Tasks
+[`@agimon-ai/doompi-team`][pkg-doompi-team] runs named subagents asynchronously. It owns agents,
+runs, membership, intercom, and model policy; Task owns the persistent task graph used for
+delegation. Agents can work in parallel and message one another. `SPC a l` lists available agents;
+`SPC a r` opens current-session runs and their controls.
+
+#### Tasks
 
 [`@agimon-ai/doompi-task`][pkg-doompi-task] keeps a task graph on disk, not a disposable checklist in the
-transcript. Dependencies and delegation survive compaction, and work can be handed to a
-subagent—including a smaller model when the job does not need the expensive one. Seeded
+transcript. Dependencies persist independently of transcript compaction, and work can be handed to
+a subagent, including a smaller model when the job does not need the expensive one. Seeded
 `minimal` and `copilot` modes select its `task` layer; omit that layer when a major mode
 should not expose the task tool.
 
-### Runner
+#### Runner
 
 [`@agimon-ai/doompi-runner`][pkg-doompi-runner] replaces Pi's blocking `bash` tool with
 supervised command execution in the generated default Copilot mode. Short commands still return
-inline; commands that pass the configurable threshold—60 seconds by default—move into the
+inline; commands that pass the configurable threshold of 60 seconds by default move into the
 background with durable logs. Use `background: true` for an immediate detached run or
-`interactive: true` when the command needs terminal input. Runner IDs, controls, and logs survive
-compaction and context rewrites and remain available through Runner Space at `SPC r r` or the
-`doom-runner` CLI. Platform-specific RMUX binaries are selected automatically, with a fallback
+`interactive: true` when the command needs terminal input. Runner IDs and durable logs remain available to the current session through Runner Space at
+`SPC r r` or the `doom-runner` CLI. Platform-specific RMUX binaries are selected automatically, with a fallback
 when RMUX is unavailable. Custom modes must include the `runner` layer to replace `bash`.
 
-### Auto-compact
+#### Auto-compact
 
 Ordinary compaction waits for one summary to save an overgrown session.
 [`@agimon-ai/doompi-autocompact`][pkg-doompi-autocompact] leaves checkpoints instead:
@@ -307,71 +301,76 @@ Ordinary compaction waits for one summary to save an overgrown session.
    result is ready to use.
 3. On the third pass, it combines them again and forces compaction.
 
-The work runs off-thread. Each checkpoint carries the live plan, task graph, team state,
-and user request with it, so coordination does not have to be guessed back out of prose.
+The work runs off-thread and can make up to three additional summarization calls. The standard
+adapter preserves staged conversation checkpoints; Task and Team keep their own state rather than
+being embedded as special snapshots in the compact summary.
+
+### Context and access
 
-### Help mode
+#### Help mode
 
 [`@agimon-ai/doompi-help`][pkg-doompi-help] keeps package guidance out of the default prompt. A fresh parent
 session performs no Help retrieval and exposes no Help skills. Use `SPC h e`, or the existing
 `minor_mode` client in headless sessions, to activate the package indexes; use the same action
 to deactivate them before the next interaction. The initial contributors expose
-`doompi-help`, `workflow-help`, and `doompi-config-help`. Child sessions never assemble the
-Help runtime.
+`doompi-help`, `workflow-help`, and `doompi-config-help`. DoomPi's default child-session assembly does not include the Help runtime.
 
-### MCP
+#### MCP
 
 [`@agimon-ai/doompi-mcp`][pkg-doompi-mcp] is the gate between a session and its servers. It reads `.mcp.json`
 and other common formats, then exposes only the servers and proxy upstreams allowed by the
 selected domains. Switch domains and that boundary reloads with them.
 
-### Ask user question
+#### Ask user question
 
 [`@agimon-ai/doompi-user-feedback`][pkg-doompi-user-feedback] gives the agent a structured question that actually
 waits for an answer. In autonomous Voice mode it skips the modal, narrates the choices,
 and accepts the next spoken response as an ordinary user message.
 
-### Logging and telemetry
+#### Logging and telemetry
+
+DoomPi logging records operational metadata such as counters, spans, session IDs, tool names, and
+errors. Callers remain responsible for values they attach to telemetry. `SPC h l` opens current-session
+metrics, and [`@agimon-ai/log-sink-mcp`][pkg-log-sink-mcp] provides historical lookup when a sink is
+configured.
 
-Doompi telemetry records counters and spans, never prompt text or file content, in a local
-SQLite database by default. `SPC h l` opens the metrics, and
-[`@agimon-ai/log-sink-mcp`][pkg-log-sink-mcp] gives the agent CLI tools for inspecting its own
-runs.
+### Modes and automation
 
-### Plan mode
+#### Plan mode
 
-A promise to "only plan" is not a permission boundary. [`@agimon-ai/doompi-plan`][pkg-doompi-plan] makes the
-repository read-only while the agent explores, persists the plan, and hands it back for
-approval. Use `SPC p p` for normal planning, `SPC p d` for debug planning, `SPC p f` for
+A promise to "only plan" is not a permission boundary. [`@agimon-ai/doompi-plan`][pkg-doompi-plan]
+removes Pi's `edit` and `write` tools while the agent explores, persists the plan, and hands it back
+for approval. It does not sandbox Bash, external tools, or the operating system. Use `SPC p p` for normal planning, `SPC p d` for debug planning, `SPC p f` for
 the Fable flow, and `SPC p e` to exit. Turn it on when the approach should be settled
 before the files move.
 
-### Loop mode
+#### Loop mode
 
 [`@agimon-ai/doompi-loop`][pkg-doompi-loop] is an in-session scheduler. It runs a prompt immediately and then
 repeats it on an interval; several loops can coexist. Use `SPC l s` to start one and
 `SPC l l` to list or stop them. It is for recurring checks and prompts that belong to the
 current session.
 
-### Goal mode
+#### Goal mode
 
 [`@agimon-ai/doompi-goal`][pkg-doompi-goal] pins one objective to the session until it completes or you end
 it. Use `SPC g g` for status, `SPC g s` to start, `SPC g e` to end, and `SPC g p` for
 history. Finished goals leave the prompt and tools behind but remain in history when you
 want to restart one.
 
-### Workflow mode
+#### Workflow mode
 
 [`@agimon-ai/doompi-workflow`][pkg-doompi-workflow] runs GitHub Actions-style job graphs with dependencies,
-timeouts, artifacts, and a separate Doompi session for each step. Use `SPC w w` to launch,
+timeouts, artifacts, and a separate DoomPi session for each step. Use `SPC w w` to launch,
 `SPC w l` to manage, `SPC w r` to recover a failed run, and `SPC w e` to give the agent
 workflow tools or take them back. It is for work that needs hard job boundaries and
 explicit handoffs rather than one long conversation.
 
-### Voice mode
+#### Voice mode
 
-[`@agimon-ai/doompi-voice`][pkg-doompi-voice] records and transcribes speech locally; audio stays on the
-machine. `SPC v v` is one-shot manual dictation and never enables Voice tools. `SPC v a`
+[`@agimon-ai/doompi-voice`][pkg-doompi-voice] captures PCM audio through the local platform helper and
+can transcribe it locally. Transcript text, session state, and model requests may still cross process
+or provider boundaries according to the configured engines. `SPC v v` is one-shot manual dictation and never enables Voice tools. `SPC v a`
 toggles autonomous capture; only its exact-active TUI session receives the two Voice
 façades plus the standalone `narrate` tool.
 
@@ -392,7 +391,7 @@ available, and the same model continues to provide bounded command correction.
 
 ## Configuration
 
-Doompi reads four configuration files:
+DoomPi reads four configuration files:
 
 - `config.yaml` defines runtime settings such as trust, editor, planning, and voice behavior.
 - `modes.yaml` defines extension layers and major modes.
@@ -400,7 +399,7 @@ Doompi reads four configuration files:
 - `profiles.yaml` supplies persona files and environment defaults.
 
 Each matrix file has two optional layers: personal defaults in `~/.pi/.doom/` and repository
-overrides in `<repository>/.doom/`. Doompi loads both. Unique named entries from either layer
+overrides in `<repository>/.doom/`. DoomPi loads both. Unique named entries from either layer
 remain available; a same-named repository entry replaces the complete personal entry. Plugin
 and profile roots from both layers are retained. Relative paths in personal config resolve
 from `~/.pi/.doom/`; relative paths in repository config resolve from the repository root.
@@ -434,7 +433,7 @@ majorMode:
     layers: [team, review]
 ```
 
-Order matters: Doompi assembles layers and their packages from left to right. Put settings
+Order matters: DoomPi assembles layers and their packages from left to right. Put settings
 under the package that consumes them; a layer is composition, not a mystery bag of shared
 configuration. Home and repository `layers` and `majorMode` records merge by name, with the
 repository definition winning a collision.
@@ -456,7 +455,7 @@ plugins:
   entries:
     remote-review:
       source: url
-      url: https://github.com/acme/review-plugin.git
+      url: '<REVIEW_PLUGIN_GIT_URL>'
       ref: v1.2.0
     published-research:
       source: npm
@@ -499,7 +498,7 @@ amount of repository context is none.
 
 A profile directory becomes discoverable when it directly contains `profile.md`, `SOUL.md`,
 or `AGENTS.md`. A root may be one profile or a container of direct-child profiles. The folder
-name becomes the profile name; Doompi concatenates those three files in that order.
+name becomes the profile name; DoomPi concatenates those three files in that order.
 
 ```yaml
 profiles:
@@ -541,6 +540,56 @@ DPI without registering it in normal Pi settings. `doompi sync --check` turns dr
 non-zero exit code for CI. If the explanation is surprising, fix the YAML before paying a model
 to be surprised with you.
 
+## Trust and data boundaries
+
+DoomPi executes the extensions, remote Git/npm plugins, hooks, MCP stdio commands, workflows, and
+shell commands you configure. Treat them as trusted executable code. Runner commands inherit the
+process environment and operating-system privileges; their logs may contain command output and
+secrets. MCP credentials may live in the system keyring or private configuration files.
+
+Voice can keep PCM capture and transcription local when local engines are selected, but transcript
+text and model requests follow the configured providers. Loop, Workflow, Plan, Autocompact, Team,
+and autonomous Voice can make additional model calls. Telemetry is disabled or redirected through
+its owning package's controls; values supplied by callers are not automatically scrubbed.
+
+## CLI reference
+
+| Command or option                            | What it does                                                                     |
+| -------------------------------------------- | -------------------------------------------------------------------------------- |
+| `dpi init`, `dpi sync`, `dpi`                | Creates, synchronizes, and runs the repository-scoped comparison setup           |
+| `doompi init`, `doompi sync`                 | Seeds personal config, builds synchronized state, and registers DoomPi with Pi   |
+| `doompi sync --check`                        | Exits non-zero when synchronized state is stale or legacy state needs migration  |
+| `doompi compat <codex\|claude\|antigravity>` | Resolves the selected matrix and launches the compatibility adapter              |
+| `doom-runner`                                | Inspects and controls supervised Runner processes and logs                       |
+| `--explain`                                  | Prints the resolved matrix and estimated prompt cost without launching Pi        |
+| `--emit-mcp <dir>`, `--no-mcp`               | Writes the resolved MCP config or disables MCP for one run                       |
+| `--cwd <path>`, `--auto-stop`                | Chooses the working directory or exits after an interactive agent settles        |
+| `--` and remaining arguments                 | Forwards provider or Pi arguments unchanged where the selected command allows it |
+
+## Troubleshooting and direct use
+
+- Run `doompi sync --check` to detect drift and `doompi sync` to rebuild synchronized state.
+- If RMUX is unavailable on a supported target, Runner reports the fallback it uses. Linux native
+  artifacts require a compatible loader and libc environment.
+- Leader menus and overlays require Pi's interactive TUI. Commands and tools remain the interface
+  for JSON, RPC, and other headless sessions where the owning package supports them.
+- Install a directly loaded Pi subsystem with `pi install npm:@agimon-ai/<package>`. Library consumers
+  use `npm install`; native RMUX artifacts are selected by Runner and should not be installed directly.
+  The distribution remains the supported way to get the coordinated defaults.
+
+## Development
+
+```bash
+nx build @agimon-ai/doompi
+nx test @agimon-ai/doompi
+nx typecheck @agimon-ai/doompi
+nx lint @agimon-ai/doompi
+```
+
+## License
+
+MIT
+
 ## Package release order
 
 Publish [`@agimon-ai/doompi-extension-contracts`][pkg-doompi-extension-contracts] first, then
@@ -550,6 +599,14 @@ by the release tooling.
 
 [pkg-doompi]: https://www.npmjs.com/package/@agimon-ai/doompi
 [pkg-doompi-ui]: https://www.npmjs.com/package/@agimon-ai/doompi-ui
+[pkg-doompi-config]: https://www.npmjs.com/package/@agimon-ai/doompi-config
+[pkg-doompi-file-edit]: https://www.npmjs.com/package/@agimon-ai/doompi-file-edit
+[pkg-doompi-log]: https://www.npmjs.com/package/@agimon-ai/doompi-log
+[pkg-doompi-telemetry]: https://www.npmjs.com/package/@agimon-ai/doompi-telemetry
+[pkg-rmux-darwin-arm64]: https://www.npmjs.com/package/@agimon-ai/doompi-runner-rmux-darwin-arm64
+[pkg-rmux-darwin-x64]: https://www.npmjs.com/package/@agimon-ai/doompi-runner-rmux-darwin-x64
+[pkg-rmux-linux-arm64]: https://www.npmjs.com/package/@agimon-ai/doompi-runner-rmux-linux-arm64
+[pkg-rmux-linux-x64]: https://www.npmjs.com/package/@agimon-ai/doompi-runner-rmux-linux-x64
 [pkg-doompi-team]: https://www.npmjs.com/package/@agimon-ai/doompi-team
 [pkg-doompi-task]: https://www.npmjs.com/package/@agimon-ai/doompi-task
 [pkg-doompi-runner]: https://www.npmjs.com/package/@agimon-ai/doompi-runner

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agimon-ai/doompi",
-  "version": "0.0.1-alpha.21",
+  "version": "0.0.1-alpha.22",
   "description": "Pi-based agent harness for repository automations and developer workflows",
   "keywords": [
     "ai",
@@ -346,24 +346,24 @@
     "rolldown": "1.0.0-rc.17",
     "typebox": "1.1.38",
     "yaml": "2.9.0",
-    "@agimon-ai/doompi-autocompact": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-extension-contracts": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-config": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-help": "0.0.1-alpha.4",
-    "@agimon-ai/doompi-log": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-loop": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-file-edit": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-mcp": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-plan": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-goal": "0.0.1-alpha.11",
-    "@agimon-ai/doompi-runner": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-telemetry": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-user-feedback": "0.0.1-alpha.10",
-    "@agimon-ai/doompi-voice": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-workflow": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-team": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-ui": "0.0.1-alpha.21",
-    "@agimon-ai/doompi-task": "0.0.1-alpha.21"
+    "@agimon-ai/doompi-extension-contracts": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-autocompact": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-file-edit": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-goal": "0.0.1-alpha.12",
+    "@agimon-ai/doompi-config": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-log": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-loop": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-help": "0.0.1-alpha.5",
+    "@agimon-ai/doompi-task": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-mcp": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-team": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-user-feedback": "0.0.1-alpha.11",
+    "@agimon-ai/doompi-telemetry": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-plan": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-ui": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-runner": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-workflow": "0.0.1-alpha.22",
+    "@agimon-ai/doompi-voice": "0.0.1-alpha.22"
   },
   "devDependencies": {
     "@earendil-works/pi-ai": "0.84.2",