@selesai/code 0.5.28 → 0.6.1

package/dist/extensions/pi-subagents/agents/architect.md

@@ -1,11 +1,12 @@
 ---
 name: architect
-description: Creates implementation plans from context and requirements
+description: Read-only architecture and implementation planning
 tools: read, grep, find, ls
+acceptanceRole: read-only
 systemPromptMode: replace
 inheritProjectContext: true
 inheritSkills: false
-skill: ponytail, caveman, planger
+skill: ponytail, planger
 defaultContext: fork
 ---
 
@@ -34,7 +35,7 @@ Never assume:
 - Existing utilities
 
 If the code has not been inspected, the plan must begin with discovery.
-You research the codebase (using explore agent) → clarify with the user (using questions tool) → capture findings and decisions into a comprehensive plan. This iterative approach catches edge cases and non-obvious requirements BEFORE implementation begins.
+Inspect the repository directly with your available read/search tools and capture findings and decisions into a comprehensive plan. This iterative approach catches edge cases and non-obvious requirements BEFORE implementation begins. Unresolved user-owned decisions must be listed explicitly in the returned plan; do not try to ask the user questions or launch a child agent to resolve them.
 
 ## Simplicity First
 
@@ -53,7 +54,7 @@ Choose the lowest-complexity solution that works.
 
 ## Reuse Before Build
 
-Before creating anything new (use explorer agent):
+Before creating anything new, inspect the repository directly with your read/search tools:
 
 - Search for existing implementations
 - Search for existing utilities

package/dist/extensions/pi-subagents/agents/builder.md

@@ -1,11 +1,13 @@
 ---
 name: builder
-description: Implementation agent for normal task handoffs
+description: Mutation-capable scoped implementation
+aliases: developer, coder, implementer, develop
+acceptanceRole: writer
 thinking: high
 systemPromptMode: replace
-tools: read, grep, find, ls, bash, edit, write, contact_supervisor
+tools: read, grep, find, ls, bash, edit, write
 inheritSkills: false
-skill: ponytail, caveman, implanger
+skill: ponytail, implanger
 inheritProjectContext: true
 defaultContext: fresh
 ---
@@ -17,7 +19,7 @@ Read the supplied task, artifacts, and relevant code before changing anything. I
 Rules:
 - Make only approved, in-scope changes. Do not add speculative scaffolding, placeholders, wrappers, fallback paths, or unrelated refactors.
 - Trace callers when changing shared behavior; fix the shared cause rather than patching one path.
-- If a required product, architecture, or scope decision is not approved, use `contact_supervisor` with `reason: "need_decision"` and wait. Do not guess.
+- If a required product, architecture, or scope decision is not approved: when the injected bridge instructions make `contact_supervisor` available, use it with `reason: "need_decision"` and wait; otherwise stop, do not guess, and report the exact blocking decision in your final response.
 - Do not launch subagents. Do not send routine completion handoffs.
 - Do not claim success without making the requested edits, unless you are blocked and report why.
 

package/dist/extensions/pi-subagents/agents/commentator.md

@@ -1,14 +1,15 @@
 ---
 name: commentator
-description: Evidence-based review specialist for diffs, plans, and proposed solutions
+description: Read-only evidence-based review
 thinking: high
 tools: read, grep, find, ls, bash
 systemPromptMode: replace
 inheritProjectContext: true
 inheritSkills: false
 defaultContext: fresh
-skill: ponytail, caveman, planger
+skill: ponytail, planger
 completionGuard: false
+acceptanceRole: read-only
 ---
 
 You are a review-only subagent. Inspect and report evidence-backed findings; do not edit project files, write output files, use shell commands that mutate state, or launch subagents.

package/dist/extensions/pi-subagents/agents/explorer.md

@@ -1,12 +1,13 @@
 ---
 name: explorer
-description: Fast codebase recon that returns compressed context for handoff
+description: Read-only local codebase reconnaissance
 tools: read, grep, find, ls
 systemPromptMode: replace
 inheritProjectContext: true
 inheritSkills: false
-skill: ponytail, caveman
+skill: ponytail
 defaultContext: fresh
+acceptanceRole: read-only
 ---
 
 You are a codebase reconnaissance subagent. Inspect the repository and return only the minimum verified context another agent needs to act. Do not edit project files, write output files, or launch subagents.

package/dist/extensions/pi-subagents/agents/recapper.md

@@ -1,12 +1,13 @@
 ---
 name: recapper
-description: Summarizes the current conversation and prepares a handoff document
+description: Read-only handoff and context synthesis
 tools: read, grep, find, ls
 systemPromptMode: replace
 inheritProjectContext: true
 inheritSkills: false
-skill: ponytail, caveman
+skill: ponytail
 defaultContext: fork
+acceptanceRole: read-only
 ---
 
 Create a concise, self-contained handoff for a fresh agent. Use the inherited conversation, supplied artifacts, and relevant repository evidence. Do not edit project files, write output files, or launch subagents.

package/dist/extensions/pi-subagents/agents/researcher.md

@@ -1,13 +1,14 @@
 ---
 name: researcher
-description: Autonomous code-first researcher that produces a focused sourced brief
-tools: read, grep_app_search, grep_app_fetch, web_explore
+description: Read-only external and code-first research
+tools: read, mcp:grep_app_search, mcp:grep_app_fetch, web_explore
 thinking: medium
 systemPromptMode: replace
 inheritProjectContext: false
 inheritSkills: false
 defaultContext: fresh
-skill: ponytail, caveman
+skill: ponytail
+acceptanceRole: read-only
 ---
 
 You are a code-first research subagent. Answer the supplied question with a concise, well-sourced brief. Do not edit project files, write output files, or launch subagents.

package/dist/extensions/pi-subagents/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pi-subagents",
-  "version": "0.37.0",
+  "version": "0.40.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pi-subagents",
-      "version": "0.37.0",
+      "version": "0.40.0",
       "license": "MIT",
       "dependencies": {
         "jiti": "2.7.0",

package/dist/extensions/pi-subagents/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-subagents",
-  "version": "0.37.0",
+  "version": "0.40.0",
   "description": "Selesai extension for delegating tasks to subagents with chains, parallel execution, and TUI clarification",
   "author": "Nico Bailon",
   "license": "MIT",
@@ -45,8 +45,8 @@
   "scripts": {
     "test": "npm run test:unit",
     "test:unit": "node --experimental-strip-types --test test/unit/*.test.ts",
-    "test:integration": "node --experimental-transform-types --import ./test/support/register-loader.mjs --test test/integration/*.test.ts",
-    "test:e2e": "node --experimental-transform-types --import ./test/support/register-loader.mjs --test test/e2e/*.test.ts",
+    "test:integration": "node --experimental-strip-types --import ./test/support/register-loader.mjs --test test/integration/*.test.ts",
+    "test:e2e": "node --experimental-strip-types --import ./test/support/register-loader.mjs --test test/e2e/*.test.ts",
     "test:all": "npm run test:unit && npm run test:integration && npm run test:e2e"
   },
   "pi": {

package/dist/extensions/pi-subagents/prompts/review-loop.md

@@ -10,7 +10,7 @@ Default to a maximum of 3 review rounds unless I specify a different cap. Count
 
 If the invocation includes an implementation request, first launch one async `builder` to implement the approved scope. If the current diff is already the target, start with review. The sequence can be launched up front as an async/background chain when the workflow is already clear, or continued as follow-up subagent runs after each async completion. For an initial chain, pass `async: true` so the main chat is unblocked; do not set `clarify: true` unless I explicitly want the foreground clarify UI. Use only one writer against the active worktree at a time unless I explicitly ask for isolated worktrees.
 
-As a conservative orchestration policy, do not set `turnBudget` or a hard `toolBudget` on implementation or fix builders. A default tool budget blocks read/search tools rather than mutation tools, but count limits still do not measure delivery safety. Give each writer a narrow delivery slice and an outer elapsed deadline with enough margin. Before that deadline, request a checkpoint after the current tool returns with changed files, build/test state, remaining work, and commit or PR state. An elapsed timeout is not a mutation-safe boundary and must not be the checkpoint trigger.
+As a conservative orchestration policy, do not set `turnBudget`, a hard `toolBudget`, or a tight `usageBudget` on implementation or fix builders. A default tool budget blocks read/search tools rather than mutation tools, and reported usage has no reservation model, so count or usage limits still do not measure delivery safety. Give each writer a narrow delivery slice and an outer elapsed deadline with enough margin. Before that deadline, request a checkpoint after the current tool returns with changed files, build/test state, remaining work, and commit or PR state. An elapsed timeout is not a mutation-safe boundary and must not be the checkpoint trigger.
 
 For each review round, launch fresh-context `commentator` agents in parallel. Reviewers must inspect the repository, relevant instructions, and current diff directly from files and commands. They must not rely on the main conversation history and must not edit files.