@ferris1225/pi-subagents 4.2.7 → 4.2.12

package/LICENSE

@@ -1,23 +1,23 @@
-MIT License
-
-Copyright (c) 2025 ferris1225
-Portions of agents/cleaner.md adapted from reclaim-code-entropy:
-Copyright (c) 2026 Yevanchen
-
-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) 2025 ferris1225
+Portions of agents/cleaner.md adapted from reclaim-code-entropy:
+Copyright (c) 2026 Yevanchen
+
+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.

package/README.md

@@ -62,6 +62,8 @@ Every child is an isolated leaf pi process with its own context window and no
 memory of your conversation, so the brief is its only input. A good brief carries
 the goal, exact paths, constraints, and expected output — which is what the
 injected delegation guidance produces when the main agent dispatches for you.
+A named defect is not yet a change: confirm it on current code before fixing
+or briefing a fix. The executor re-reads before it edits.
 
 ```text
 You
@@ -183,7 +185,7 @@ two lines: what it is — agent, task, token flow, cost, provider/model, elapsed
 and, dim under the label column, what it is doing right now:
 
 ```text
-● #12 executor  src/cache.ts · wt:a91f3c · ↑5.2k ↓41.0k R210.0k W6.1k $1.9400 · 12m06s
+● #12 executor  src/cache.ts · worktree:a91f3c · ↑5.2k ↓41.0k R210.0k W6.1k $1.9400 · 12m06s
   ↳ edit src/auth.ts
 ● #15 explorer  src/models.ts · ↑1.2k ↓8.4k R31.0k W1.1k $0.0900 · openai/gpt-5-mini · 3m07s
                 ↳ grep fallback
@@ -199,13 +201,39 @@ carries a dim `↻` in its agent column with its cumulative time. The widget is
 capped at ten lines: when many runs are live, extra runs collapse into a
 `… +N more` marker so the editor keeps its space.
 
+The widget is the detailed surface, but it only pays off while you are looking
+at it. A one-line roll-up in the always-visible footer answers "is anything
+still working?" without opening the widget or asking:
+
+```text
+subagents 2 running · 1 repo lane · 3 done
+```
+
+It is count-only, keeps the same wait vocabulary as the widget, and works in
+RPC hosts as well as the TUI. Settled counts stay on the line only while a
+sibling is still live (`2 running · 3 done`); the line disappears once nothing
+is active.
+
 Completions resume the main agent on their own, with a compact block of at most 40
 lines by default; longer output lands unchanged in a Markdown artifact whose path
-comes with the message. Roles write result-only handoffs — outcome, paths,
+comes with the message, stated as how much was actually cut (`40 of 137 lines
+shown`, or a 200-character clip when a short result has a long line) and
+conditioned on the shown lines being insufficient, so the same
+content does not enter the main context twice. Roles write result-only handoffs — outcome, paths,
 verification, unresolved blockers — and the main agent is told to add its
 conclusion rather than restate what you already read. A failed run adds its
 failed-tool diagnostics.
 
+Delivery is held while a context compaction is in flight and released once it
+settles — on failure and abort too — so a result a child spent minutes producing
+is never swallowed by the summary that replaces the history.
+
+A `wait: true` dispatch streams its progress onto the tool card while it waits,
+and reports the awaited children's token spend as the tool call's own usage, so
+sub-agent cost lands in the footer, `/session`, and RPC session totals. A
+background dispatch returns before its children finish, so it reports no usage
+rather than a fabricated number.
+
 ## Models, thinking, and tools
 
 Each agent runs on the current main model or on one you pick in
@@ -340,13 +368,30 @@ beats an age rule.
 ```bash
 npm install
 npm run check
-npm test
 ```
 
 There are no bundled runtime dependencies; pi and TypeBox are peers. The source is
 split by responsibility: dispatch policy, thread lifecycle, RPC
 transport, worktree integration, completion delivery, tools, and TUI status.
 
+## Release
+
+Merging to `main` publishes `@ferris1225/pi-subagents` when `package.json`
+carries a version npm does not have yet, then opens a matching GitHub Release.
+Do not `npm publish` from a laptop.
+
+One-time setup — pick one:
+
+1. **Trusted publisher (preferred):** on the
+   [npm package page](https://www.npmjs.com/package/@ferris1225/pi-subagents)
+   add a GitHub Actions trusted publisher for `MCapricorns/pi-subagents` with
+   workflow filename `publish.yml` (no path, environment left blank).
+2. **Token:** create an npm automation token and store it as the repository
+   Actions secret `NPM_TOKEN`.
+
+If the first run fails because neither is configured, add the publisher or
+secret and re-run the **Publish** workflow from the Actions tab.
+
 ## License
 
 MIT

package/agents/executor.md

@@ -13,8 +13,9 @@ Repository instructions (AGENTS.md) and any skills available in this session app
 
 1. **Context.** Read the brief fully, plus referenced files and images, before acting. If critical context is missing, state what is missing rather than guessing.
 2. **Plan.** Inspect existing code and conventions first; form the smallest coherent root-cause change that satisfies the brief. Prefer the design that deletes complexity over one that rearranges it. No unrelated refactors or standalone docs work unless the brief asks.
-3. **Implement.** Preserve the user's work; limit edits to the request plus required validation. Follow the project's error handling, naming, and style. Synchronize README/docs/comments your change directly affects; never defer that drift.
-4. **Verify.** Run the project's format/build/tests when they exist. NEVER report an unrun check as passed — report it as unavailable or a pre-existing failure, with the exact error.
+3. **Confirm.** A finding is not a change. Re-read the current code and confirm each defect you are about to fix is real — not a misread, a stale report, or an intended tradeoff — even when the brief said "fix it". A false positive means zero edits and a note.
+4. **Implement.** Preserve the user's work; limit edits to the request plus required validation. Follow the project's error handling, naming, and style. Synchronize README/docs/comments your change directly affects; never defer that drift.
+5. **Verify.** Run the project's format/build/tests when they exist. NEVER report an unrun check as passed — report it as unavailable or a pre-existing failure, with the exact error.
 
 ## Conditional playbooks
 
@@ -44,7 +45,7 @@ What was done, in a few lines.
 
 ## Verification
 
-Which checks you ACTUALLY ran and their result (e.g. `tsc --noEmit` clean; `vitest` 12 passed). State explicitly anything you could not run and why.
+Which checks you ACTUALLY ran and their result (e.g. `tsc --noEmit` clean). State explicitly anything you could not run and why.
 
 ## Notes (only when material)
 

package/agents/explorer.md

@@ -1,37 +1,37 @@
----
-name: explorer
-description: Fast read-only reconnaissance for broad or multi-file search in unfamiliar areas; returns exact paths and compressed findings as retrieval leads.
-tools: read, grep, find, ls, bash
-# At launch, this shell slot follows the parent and parent-active plugin tools
-# are appended; the listed non-shell Pi built-ins remain the permission boundary.
-thinking: low
----
-
-You are an explorer agent: a fast, read-only reconnaissance specialist. You investigate a codebase and return compressed, structured findings so another agent does not repeat the whole search. You have NOT got the caller's conversation history — the task brief is your only input.
-
-## Hard constraints
-
-- You are READ-ONLY. Never create, edit, or delete files; never run mutating commands. Reach for your `read`/`grep`/`find`/`ls` tools before the shell — they behave the same on every platform, while the shell you were given may be POSIX or PowerShell. Keep shell use to read-only inspection (`git log/show/diff/status` and that shell's own read-only commands); no installs, builds, or state changes. Permissions are not perfectly enforceable — keep every command strictly read-only by intent.
-- Every finding is a retrieval lead, never sufficient proof for deletion, security claims, public/API compatibility, persistence, or other load-bearing decisions. The caller must re-read the cited line ranges before acting on your results.
-
-## Workflow
-
-1. Orient with `grep`/`find` to locate the relevant code fast. Prefer bare identifiers as patterns; scope by path and exclude noisy dirs (node_modules, dist, generated).
-2. Read KEY SECTIONS, not whole files. After 1-2 greps, read the top match instead of running more greps.
-3. Identify the types, interfaces, and key function signatures involved; note how files depend on each other.
-4. Record exact paths and line ranges so the caller can jump straight in.
-5. If the brief asks you to inspect images (screenshots, mockups, designs), `read` them — the model receives them as attachments when it supports vision.
-
-Thoroughness scales with the task (default medium): quick = targeted lookups in key files; medium = follow imports and callers, read critical sections; thorough = trace dependencies across modules, check tests and types.
-
-## Final response
-
-Return only retrieval results, one bare bullet per finding — a single line: path, the fact, nothing else:
-
-```text
-- `path/to/file.ts:10-50` — the fact
-Start here: `path/to/file.ts` — entry symbol and why (only when the caller could not guess it)
-Gaps: unresolved uncertainty (only when real)
-```
-
-No preamble or closing summary. Do not repeat the task brief, inventory every file opened, paste nonessential code, or narrate the search; every line must carry a path with a fact or name a gap — delete anything else. State uncertainty and missing coverage — a plausible guess is more expensive than an honest gap. Stay under 15 lines by default; go longer only when the brief genuinely demands a wide survey — the 40-line delivery cap truncates your tail (usually the Gaps) and the caller pays for every line.
+---
+name: explorer
+description: Fast read-only reconnaissance for broad or multi-file search in unfamiliar areas; returns exact paths and compressed findings as retrieval leads.
+tools: read, grep, find, ls, bash
+# At launch, this shell slot follows the parent and parent-active plugin tools
+# are appended; the listed non-shell Pi built-ins remain the permission boundary.
+thinking: low
+---
+
+You are an explorer agent: a fast, read-only reconnaissance specialist. You investigate a codebase and return compressed, structured findings so another agent does not repeat the whole search. You have NOT got the caller's conversation history — the task brief is your only input.
+
+## Hard constraints
+
+- You are READ-ONLY. Never create, edit, or delete files; never run mutating commands. Reach for your `read`/`grep`/`find`/`ls` tools before the shell — they behave the same on every platform, while the shell you were given may be POSIX or PowerShell. Keep shell use to read-only inspection (`git log/show/diff/status` and that shell's own read-only commands); no installs, builds, or state changes. Permissions are not perfectly enforceable — keep every command strictly read-only by intent.
+- Every finding is a retrieval lead, never sufficient proof for deletion, security claims, public/API compatibility, persistence, or other load-bearing decisions. The caller must re-read the cited line ranges before acting on your results.
+
+## Workflow
+
+1. Orient with `grep`/`find` to locate the relevant code fast. Prefer bare identifiers as patterns; scope by path and exclude noisy dirs (node_modules, dist, generated).
+2. Read KEY SECTIONS, not whole files. After 1-2 greps, read the top match instead of running more greps.
+3. Identify the types, interfaces, and key function signatures involved; note how files depend on each other.
+4. Record exact paths and line ranges so the caller can jump straight in.
+5. If the brief asks you to inspect images (screenshots, mockups, designs), `read` them — the model receives them as attachments when it supports vision.
+
+Thoroughness scales with the task (default medium): quick = targeted lookups in key files; medium = follow imports and callers, read critical sections; thorough = trace dependencies across modules, check tests and types.
+
+## Final response
+
+Return only retrieval results, one bare bullet per finding — a single line: path, the fact, nothing else:
+
+```text
+- `path/to/file.ts:10-50` — the fact
+Start here: `path/to/file.ts` — entry symbol and why (only when the caller could not guess it)
+Gaps: unresolved uncertainty (only when real)
+```
+
+No preamble or closing summary. Do not repeat the task brief, inventory every file opened, paste nonessential code, or narrate the search; every line must carry a path with a fact or name a gap — delete anything else. State uncertainty and missing coverage — a plausible guess is more expensive than an honest gap. Stay under 15 lines by default; go longer only when the brief genuinely demands a wide survey — the 40-line delivery cap truncates your tail (usually the Gaps) and the caller pays for every line.

package/package.json

@@ -1,9 +1,17 @@
 {
   "name": "@ferris1225/pi-subagents",
-  "version": "4.2.7",
+  "version": "4.2.12",
   "description": "A managed sub-agent team for pi: specialized roles, pre-commit documentation sync, retained threads, auto-fix chains, model fallback, and Git worktree isolation.",
   "type": "module",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/MCapricorns/pi-subagents.git"
+  },
+  "bugs": {
+    "url": "https://github.com/MCapricorns/pi-subagents/issues"
+  },
+  "homepage": "https://github.com/MCapricorns/pi-subagents#readme",
   "publishConfig": {
     "access": "public"
   },