acstack 0.52.2 → 0.52.4

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acstack-cli",
-  "version": "0.52.2",
+  "version": "0.52.4",
   "description": "CLI for the ACStack agentic coding stack",
   "type": "module",
   "license": "MIT",

package/docs/terminal-workspace.md

@@ -353,14 +353,14 @@ What `apply` does:
 - It installs pi with `npm install -g @earendil-works/pi-coding-agent` when pi is missing
 - It installs ACStack into pi, pinned to the version of this plugin
     - Re-running `apply` after a plugin update moves the pin forward, and never back
-- It installs `pi-subagents`, which ACStack on pi needs to launch a subagent
+- It installs `ac-teams` for agent delegation, shared tasks, and messaging
+    - Reapplying removes replaced delegation and todo packages only if this setup installed them; user-installed packages stay
 - It installs `billion-context` by default for context compression in pi
     - When the `bili` command is available, setup runs native plugin setup for pi
     - Setup leaves Claude Code and Codex alone, and removes bili from them if an older setup added it
     - Set `pi.billion_context: false` to leave it out, or to remove it later if this setup installed it
-- It installs `@juicesharp/rpiv-todo` and `pi-plugin-manager` by default
-    - When todo is on, `apply` suggests a todo-discipline line for the user's global Pi context file if it is missing
-    - Set `pi.todo: false` or `pi.plugin_manager: false` to leave either package out
+- It installs `pi-plugin-manager` by default
+    - Set `pi.plugin_manager: false` to leave it out
 - It installs `@juicesharp/rpiv-ask-user-question` as pi's question tool by default
     - ACStack uses it because decisions can include markdown, code and artifact previews
     - It accepts freeform answers and notes, and needs no full-event telemetry environment variable
@@ -390,16 +390,15 @@ What `apply` does:
     - The agentic-retro step needs the agentic-retro plugin installed first, and `apply` says so when it is not
 - It writes the delegation line into pi's context file in `~/.pi/agent`, between HTML comment markers
     - That is `AGENTS.md` by default, or the first of `AGENTS.override.md`, `AGENTS.md`, `AGENTS.MD`, `CLAUDE.md` and `CLAUDE.MD` that exists, which is the one pi reads
-    - `pi-subagents` delegates only when your request or your instructions allow it
-- It sets `"toolActivation": "eager"` in `~/.pi/agent/extensions/subagent/config.json`
+    - Delegate only when your request or your instructions allow it
 - It binds `"app.message.dequeue"` to `"ctrl+enter"` in `~/.pi/agent/keybindings.json`
 - It writes the four keys under `pi.settings` into `~/.pi/agent/settings.json`
 - It patches pi's bundled TUI so Windows Terminal Win32 input records paste as text
     - `pi update` can replace the bundle, so `setup.sh upgrade pi` reapplies the patch
 - It patches an existing herdr Pi reporter to keep the parent working while background subagents run
     - Questions still show blocked, even when children are active
-    - The patch handles `pi-subagents` busy events and `@tintinweb/pi-subagents` Agent lifecycle events
-    - Tintin workflows and children already running during an extension reload lack lifecycle replay and remain outside this tracking
+    - The patch retains legacy delegation-event support; it does not track ac-teams sessions
+    - Children already running during an extension reload lack lifecycle replay and remain outside this tracking
     - `apply`, herdr integration installation, and `setup.sh upgrade herdr` reapply the patch
     - Direct `herdr integration install pi` overwrites the patch; run `apply` afterward, then restart Pi or use `/reload`
     - Setup leaves unknown reporter layouts unchanged and reports the skipped patch
@@ -419,10 +418,10 @@ How it treats pi's files:
     - A value you changed after `apply` stays as you set it
 - `apply` never touches `auth.json`
     - Run `pi`, then `/login`, yourself
-- `setup.sh status` reports pi's version, its packages, the delegation line, `toolActivation`, and whether `auth.json` exists
+- `setup.sh status` reports pi's version, its packages, the delegation line, and whether `auth.json` exists
     - The question bridge line reports a managed asset, a user-owned path, or an absent asset
     - Start a new pi session or run `/reload` after setup changes extensions
-- `setup.sh outdated` and `setup.sh upgrade` include `billion-context`, `@juicesharp/rpiv-todo`, `pi-plugin-manager`, `@juicesharp/rpiv-ask-user-question`, `pi-web-access`, `pi-lens`, and `pi-slash-anywhere` like pi's other npm packages
+- `setup.sh outdated` and `setup.sh upgrade` include `ac-teams`, `billion-context`, `pi-plugin-manager`, `@juicesharp/rpiv-ask-user-question`, `pi-web-access`, `pi-lens`, and `pi-slash-anywhere` like pi's other npm packages
 
 ## 4. How you attach
 

package/orchestrator/AGENTS.md

@@ -240,7 +240,7 @@ flowchart TD
 
 - Run `commands.format` over touched files before final verification when configured
     - Report a non-zero exit as a formatting problem, not proof of incorrect behavior
-- Run the project's required build, lint, typecheck, and test checks (see Build verification)
+- Run checks covering the change and explicit project requirements (see Build verification)
 - Audit whether checks detect realistic mistakes, including circular mock assertions and missing integration
 - Respect separate test ownership when reviewing changes
 - For changed frontend files, the verification owner runs configured frontend build, lint, and tests
@@ -328,15 +328,18 @@ Read-only reviewers report discrepancies to the completion owner.
 
 ## Build verification (mandatory)
 
-The verification owner gathers passing completion evidence for the final revision before declaring the request or parent effort complete or creating a PR.
+The verification owner gathers evidence for the final revision. Opening a PR does not require running every test locally.
 
-Read `.acstack/project.yaml` for the specific commands:
+Read `.acstack/project.yaml` for the available commands and inspect the project's CI configuration before relying on it:
 
-1. Run the configured build, lint, and typecheck commands
-2. Run the configured full test suite; all tests must pass
-3. When `commands.test_collect` is configured, compare the count against `.acstack/.test-baseline` if present; investigate removed coverage and honor project baseline requirements
-4. Run configured frontend build, lint, and tests when frontend files changed
-5. Complete configured design and browser gates when applicable
+1. Use focused local checks by default: cover changed behavior, affected callers, and relevant integration paths
+2. Run applicable build, lint, and typecheck checks; scope them when the tooling supports it
+3. A configured command is not a requirement to run its entire suite. Run the full suite locally only when explicitly required by the user or project instructions, or when broad or uncertain impact cannot be covered adequately by narrower checks
+4. When `commands.test_collect` is configured, compare the count against `.acstack/.test-baseline` if present; investigate removed coverage and honor project baseline requirements
+5. Run configured frontend build, lint, and tests when frontend files changed, and complete applicable design and browser gates
+
+Required CI checks must pass before merge, not before opening a PR. Defer broader checks to CI only after confirming it runs them for this change; do not assume CI runs every test.
+Report which checks passed locally, which are deferred to CI, and which remain unverified. Do not describe pending CI checks as passing or the whole effort as verified.
 
 ### During implementation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "acstack",
-  "version": "0.52.2",
+  "version": "0.52.4",
   "private": false,
   "description": "Agentic coding stack with first-class Claude Code and pi support: skills, orchestrator instructions, and verification agents.",
   "license": "MIT",

package/pi/extension.ts

@@ -4,8 +4,8 @@
  * The pi port of the Claude Code hooks in hooks/. Claude Code and Codex never
  * load this file, and nothing in hooks/ depends on it.
  *
- *   session_start        symlink the CLI, warn once if pi-subagents is
- *                        missing, and print the setup reminder outside a
+ *   session_start        symlink the CLI, warn once if delegation is
+ *                        unavailable, and print the setup reminder outside a
  *                        acstack project            (hooks/session-start.sh)
  *   before_agent_start   list ACStack's skills in the system prompt in every
  *                        session, and add orchestrator/AGENTS.md in a
@@ -659,11 +659,11 @@ export default function acstack(pi: ExtensionAPI): void {
 			return;
 		}
 
-		if (!warnedSubagents && !pi.getAllTools().some((tool) => tool.name === "subagent" || tool.name === "Agent")) {
+		if (!warnedSubagents && !pi.getAllTools().some((tool) => tool.name === "subagent" || tool.name === "Agent" || tool.name === "team_agent")) {
 			warnedSubagents = true;
 			report(
 				ctx,
-				"acstack: no supported subagent tool is loaded (Agent or subagent), so the test-writer, task-executor, task-checker, and frontend-verifier agents cannot run. Install `npm:@tintinweb/pi-subagents` or `npm:pi-subagents` with `pi install`.",
+				"acstack: no supported subagent tool is loaded (Agent, subagent, or team_agent), so the test-writer, task-executor, task-checker, and frontend-verifier agents cannot run. Install `npm:ac-teams` with `pi install`.",
 				"warning",
 			);
 		}

package/skills/terminal-workspace/SKILL.md

@@ -67,7 +67,7 @@ above them. Eleven of those sections install thirteen tools between them:
 - Five tools the user drives day to day: herdr, gh-dash, diffnav, lazygit and harlequin. tuicr joins them once a review starts
 - Five tools that support them: delta, tuicr, yazi, mermaid-ascii and glow
 - Two helpers of ACStack's own: acstack-md, and the acstack-clip and acstack-open pair
-- The pi coding agent, with ACStack and pi-subagents installed into it
+- The pi coding agent, with ACStack and ac-teams installed into it
 
 The twelfth, `neovim`, installs nothing. It writes one file into a neovim config
 the user already has. `neovim` and `pi` both start off, because each writes into a config the user built.

package/skills/terminal-workspace/components.md

@@ -13,7 +13,7 @@ Read this file when the user asks what a component does, which key turns it on,
 | tuicr | Reviews a pull request inside the terminal. | `tuicr.enabled` |
 | lazygit | Stages, commits, amends and pushes, on one key. | `lazygit.enabled` |
 | harlequin | A SQL editor in the terminal, on one key. Installed by uv, and launched by acstack-db. | `harlequin.enabled` |
-| pi | A coding agent in the terminal, with ACStack, pi-subagents and the user's own pi settings installed into it. Installed by npm, and starts off. | `pi.enabled` |
+| pi | A coding agent in the terminal, with ACStack, ac-teams and the user's own pi settings installed into it. Installed by npm, and starts off. | `pi.enabled` |
 | neovim | A dot in the LazyVim statusline for a buffer with unsaved changes, and copy over SSH through OSC 52. Installs nothing, writes one file, and starts off. | `neovim.enabled` |
 | yazi | A file manager, with markdown drawn live by acstack-md. One key sends the hovered file to the machine the user sits at. | `yazi.enabled` |
 | markdown | Markdown with its mermaid diagrams drawn as text, or served to a browser. Installs acstack-md, mermaid-ascii and glow. | `markdown.enabled` |

package/skills/terminal-workspace/config-choices.md

@@ -54,7 +54,7 @@ Then ask about these settings, in this order:
     - Tell such a user to delete their own file to hand the dot to this component
 - **`pi.enabled`**: off by default. Turn it on for a user who runs pi, the coding agent, or wants ACStack inside it
     - `apply` installs pi with npm when it is missing, then installs ACStack into it, pinned to this plugin's version
-    - `apply` always installs `pi-subagents` too, because ACStack on pi cannot launch a subagent without it
+    - `apply` always installs `ac-teams` too, for agent delegation, shared tasks, and messaging
     - `apply` adds one line to pi's context file in `~/.pi/agent` (`AGENTS.md` by default) that lets pi delegate when an ACStack skill says to
     - `pi.compact_tools` and `pi.agentic_retro` add pi-compact-tools and agentic-retro's pi extension, both on by default
         - agentic-retro's extension needs the agentic-retro plugin first, and `apply` says so when it is missing

package/skills/terminal-workspace/turn-off-and-update.md

@@ -25,7 +25,7 @@ and leaves the rest of the user's neovim config alone. Neither `disable` nor
 `pi` undoes only what `apply` added, because pi's config is the user's:
 
 - It removes the pi packages `apply` installed, and keeps any the user installed first
-- It releases the four settings and `toolActivation`, unless the user has changed one since
+- It releases the settings and keybinding it wrote, unless the user has changed one since
     - A value `apply` replaced goes back to what the user had, and a key `apply` added goes
 - It puts back an ACStack pin `apply` moved forward, unless the user has moved it since
 - It removes the delegation block from pi's context file, and the user's text stays byte for byte
@@ -84,8 +84,8 @@ bash "$SETUP" upgrade yazi delta   # only these
 
 pi adds four rows of its own:
 
-- `pi`, `pi-subagents` and `pi-compact-tools` compare against npm, and `upgrade` runs `pi update` for each
-    - A package the user pinned, such as `npm:pi-subagents@1.0.0`, reports `unknown`, because `pi update` never moves it
+- `pi`, `ac-teams` and `pi-compact-tools` compare against npm, and `upgrade` runs `pi update` for each
+    - A package the user pinned, such as `npm:ac-teams@1.0.0`, reports `unknown`, because `pi update` never moves it
 - `pi-acstack` compares ACStack's pin in pi against this plugin's version, with no network at all
     - `upgrade pi-acstack` moves the pin forward, and so does `apply`
     - Neither moves a pin newer than this plugin, because the user chose it