@emiliosp/pi-maestro 0.16.0 → 0.18.0

package/node_modules/pi-subagents/node_modules/yaml/dist/visit.js

@@ -1,236 +0,0 @@
-'use strict';
-
-var identity = require('./nodes/identity.js');
-
-const BREAK = Symbol('break visit');
-const SKIP = Symbol('skip children');
-const REMOVE = Symbol('remove node');
-/**
- * Apply a visitor to an AST node or document.
- *
- * Walks through the tree (depth-first) starting from `node`, calling a
- * `visitor` function with three arguments:
- *   - `key`: For sequence values and map `Pair`, the node's index in the
- *     collection. Within a `Pair`, `'key'` or `'value'`, correspondingly.
- *     `null` for the root node.
- *   - `node`: The current node.
- *   - `path`: The ancestry of the current node.
- *
- * The return value of the visitor may be used to control the traversal:
- *   - `undefined` (default): Do nothing and continue
- *   - `visit.SKIP`: Do not visit the children of this node, continue with next
- *     sibling
- *   - `visit.BREAK`: Terminate traversal completely
- *   - `visit.REMOVE`: Remove the current node, then continue with the next one
- *   - `Node`: Replace the current node, then continue by visiting it
- *   - `number`: While iterating the items of a sequence or map, set the index
- *     of the next step. This is useful especially if the index of the current
- *     node has changed.
- *
- * If `visitor` is a single function, it will be called with all values
- * encountered in the tree, including e.g. `null` values. Alternatively,
- * separate visitor functions may be defined for each `Map`, `Pair`, `Seq`,
- * `Alias` and `Scalar` node. To define the same visitor function for more than
- * one node type, use the `Collection` (map and seq), `Value` (map, seq & scalar)
- * and `Node` (alias, map, seq & scalar) targets. Of all these, only the most
- * specific defined one will be used for each node.
- */
-function visit(node, visitor) {
-    const visitor_ = initVisitor(visitor);
-    if (identity.isDocument(node)) {
-        const cd = visit_(null, node.contents, visitor_, Object.freeze([node]));
-        if (cd === REMOVE)
-            node.contents = null;
-    }
-    else
-        visit_(null, node, visitor_, Object.freeze([]));
-}
-// Without the `as symbol` casts, TS declares these in the `visit`
-// namespace using `var`, but then complains about that because
-// `unique symbol` must be `const`.
-/** Terminate visit traversal completely */
-visit.BREAK = BREAK;
-/** Do not visit the children of the current node */
-visit.SKIP = SKIP;
-/** Remove the current node */
-visit.REMOVE = REMOVE;
-function visit_(key, node, visitor, path) {
-    const ctrl = callVisitor(key, node, visitor, path);
-    if (identity.isNode(ctrl) || identity.isPair(ctrl)) {
-        replaceNode(key, path, ctrl);
-        return visit_(key, ctrl, visitor, path);
-    }
-    if (typeof ctrl !== 'symbol') {
-        if (identity.isCollection(node)) {
-            path = Object.freeze(path.concat(node));
-            for (let i = 0; i < node.items.length; ++i) {
-                const ci = visit_(i, node.items[i], visitor, path);
-                if (typeof ci === 'number')
-                    i = ci - 1;
-                else if (ci === BREAK)
-                    return BREAK;
-                else if (ci === REMOVE) {
-                    node.items.splice(i, 1);
-                    i -= 1;
-                }
-            }
-        }
-        else if (identity.isPair(node)) {
-            path = Object.freeze(path.concat(node));
-            const ck = visit_('key', node.key, visitor, path);
-            if (ck === BREAK)
-                return BREAK;
-            else if (ck === REMOVE)
-                node.key = null;
-            const cv = visit_('value', node.value, visitor, path);
-            if (cv === BREAK)
-                return BREAK;
-            else if (cv === REMOVE)
-                node.value = null;
-        }
-    }
-    return ctrl;
-}
-/**
- * Apply an async visitor to an AST node or document.
- *
- * Walks through the tree (depth-first) starting from `node`, calling a
- * `visitor` function with three arguments:
- *   - `key`: For sequence values and map `Pair`, the node's index in the
- *     collection. Within a `Pair`, `'key'` or `'value'`, correspondingly.
- *     `null` for the root node.
- *   - `node`: The current node.
- *   - `path`: The ancestry of the current node.
- *
- * The return value of the visitor may be used to control the traversal:
- *   - `Promise`: Must resolve to one of the following values
- *   - `undefined` (default): Do nothing and continue
- *   - `visit.SKIP`: Do not visit the children of this node, continue with next
- *     sibling
- *   - `visit.BREAK`: Terminate traversal completely
- *   - `visit.REMOVE`: Remove the current node, then continue with the next one
- *   - `Node`: Replace the current node, then continue by visiting it
- *   - `number`: While iterating the items of a sequence or map, set the index
- *     of the next step. This is useful especially if the index of the current
- *     node has changed.
- *
- * If `visitor` is a single function, it will be called with all values
- * encountered in the tree, including e.g. `null` values. Alternatively,
- * separate visitor functions may be defined for each `Map`, `Pair`, `Seq`,
- * `Alias` and `Scalar` node. To define the same visitor function for more than
- * one node type, use the `Collection` (map and seq), `Value` (map, seq & scalar)
- * and `Node` (alias, map, seq & scalar) targets. Of all these, only the most
- * specific defined one will be used for each node.
- */
-async function visitAsync(node, visitor) {
-    const visitor_ = initVisitor(visitor);
-    if (identity.isDocument(node)) {
-        const cd = await visitAsync_(null, node.contents, visitor_, Object.freeze([node]));
-        if (cd === REMOVE)
-            node.contents = null;
-    }
-    else
-        await visitAsync_(null, node, visitor_, Object.freeze([]));
-}
-// Without the `as symbol` casts, TS declares these in the `visit`
-// namespace using `var`, but then complains about that because
-// `unique symbol` must be `const`.
-/** Terminate visit traversal completely */
-visitAsync.BREAK = BREAK;
-/** Do not visit the children of the current node */
-visitAsync.SKIP = SKIP;
-/** Remove the current node */
-visitAsync.REMOVE = REMOVE;
-async function visitAsync_(key, node, visitor, path) {
-    const ctrl = await callVisitor(key, node, visitor, path);
-    if (identity.isNode(ctrl) || identity.isPair(ctrl)) {
-        replaceNode(key, path, ctrl);
-        return visitAsync_(key, ctrl, visitor, path);
-    }
-    if (typeof ctrl !== 'symbol') {
-        if (identity.isCollection(node)) {
-            path = Object.freeze(path.concat(node));
-            for (let i = 0; i < node.items.length; ++i) {
-                const ci = await visitAsync_(i, node.items[i], visitor, path);
-                if (typeof ci === 'number')
-                    i = ci - 1;
-                else if (ci === BREAK)
-                    return BREAK;
-                else if (ci === REMOVE) {
-                    node.items.splice(i, 1);
-                    i -= 1;
-                }
-            }
-        }
-        else if (identity.isPair(node)) {
-            path = Object.freeze(path.concat(node));
-            const ck = await visitAsync_('key', node.key, visitor, path);
-            if (ck === BREAK)
-                return BREAK;
-            else if (ck === REMOVE)
-                node.key = null;
-            const cv = await visitAsync_('value', node.value, visitor, path);
-            if (cv === BREAK)
-                return BREAK;
-            else if (cv === REMOVE)
-                node.value = null;
-        }
-    }
-    return ctrl;
-}
-function initVisitor(visitor) {
-    if (typeof visitor === 'object' &&
-        (visitor.Collection || visitor.Node || visitor.Value)) {
-        return Object.assign({
-            Alias: visitor.Node,
-            Map: visitor.Node,
-            Scalar: visitor.Node,
-            Seq: visitor.Node
-        }, visitor.Value && {
-            Map: visitor.Value,
-            Scalar: visitor.Value,
-            Seq: visitor.Value
-        }, visitor.Collection && {
-            Map: visitor.Collection,
-            Seq: visitor.Collection
-        }, visitor);
-    }
-    return visitor;
-}
-function callVisitor(key, node, visitor, path) {
-    if (typeof visitor === 'function')
-        return visitor(key, node, path);
-    if (identity.isMap(node))
-        return visitor.Map?.(key, node, path);
-    if (identity.isSeq(node))
-        return visitor.Seq?.(key, node, path);
-    if (identity.isPair(node))
-        return visitor.Pair?.(key, node, path);
-    if (identity.isScalar(node))
-        return visitor.Scalar?.(key, node, path);
-    if (identity.isAlias(node))
-        return visitor.Alias?.(key, node, path);
-    return undefined;
-}
-function replaceNode(key, path, node) {
-    const parent = path[path.length - 1];
-    if (identity.isCollection(parent)) {
-        parent.items[key] = node;
-    }
-    else if (identity.isPair(parent)) {
-        if (key === 'key')
-            parent.key = node;
-        else
-            parent.value = node;
-    }
-    else if (identity.isDocument(parent)) {
-        parent.contents = node;
-    }
-    else {
-        const pt = identity.isAlias(parent) ? 'alias' : 'scalar';
-        throw new Error(`Cannot replace node with ${pt} parent`);
-    }
-}
-
-exports.visit = visit;
-exports.visitAsync = visitAsync;

package/node_modules/pi-subagents/node_modules/yaml/package.json

@@ -1,97 +0,0 @@
-{
-  "name": "yaml",
-  "version": "2.8.3",
-  "license": "ISC",
-  "author": "Eemeli Aro <eemeli@gmail.com>",
-  "funding": "https://github.com/sponsors/eemeli",
-  "repository": "github:eemeli/yaml",
-  "description": "JavaScript parser and stringifier for YAML",
-  "keywords": [
-    "YAML",
-    "parser",
-    "stringifier"
-  ],
-  "homepage": "https://eemeli.org/yaml/",
-  "files": [
-    "browser/",
-    "dist/",
-    "util.js"
-  ],
-  "type": "commonjs",
-  "main": "./dist/index.js",
-  "bin": "./bin.mjs",
-  "browser": {
-    "./dist/index.js": "./browser/index.js",
-    "./dist/util.js": "./browser/dist/util.js",
-    "./util.js": "./browser/dist/util.js"
-  },
-  "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "node": "./dist/index.js",
-      "default": "./browser/index.js"
-    },
-    "./package.json": "./package.json",
-    "./util": {
-      "types": "./dist/util.d.ts",
-      "node": "./dist/util.js",
-      "default": "./browser/dist/util.js"
-    }
-  },
-  "scripts": {
-    "build": "npm run build:node && npm run build:browser",
-    "build:browser": "rollup -c config/rollup.browser-config.mjs",
-    "build:node": "rollup -c config/rollup.node-config.mjs",
-    "clean": "git clean -fdxe node_modules",
-    "lint": "eslint config/ src/",
-    "prettier": "prettier --write .",
-    "prestart": "rollup --sourcemap -c config/rollup.node-config.mjs",
-    "start": "node --enable-source-maps -i -e 'YAML=require(\"./dist/index.js\");const{parse,parseDocument,parseAllDocuments}=YAML'",
-    "test": "jest --config config/jest.config.js",
-    "test:all": "npm test && npm run test:types && npm run test:dist && npm run test:dist:types",
-    "test:browsers": "cd playground && npm test",
-    "test:dist": "npm run build:node && jest --config config/jest.config.js",
-    "test:dist:types": "tsc --allowJs --moduleResolution node --noEmit --target es5 dist/index.js",
-    "test:types": "tsc --noEmit && tsc --noEmit -p tests/tsconfig.json",
-    "docs:install": "cd docs-slate && bundle install",
-    "predocs:deploy": "node docs/prepare-docs.mjs",
-    "docs:deploy": "cd docs-slate && ./deploy.sh",
-    "predocs": "node docs/prepare-docs.mjs",
-    "docs": "cd docs-slate && bundle exec middleman server",
-    "preversion": "npm test && npm run build",
-    "prepublishOnly": "npm run clean && npm test && npm run build"
-  },
-  "browserslist": "defaults, not ie 11",
-  "prettier": {
-    "arrowParens": "avoid",
-    "semi": false,
-    "singleQuote": true,
-    "trailingComma": "none"
-  },
-  "devDependencies": {
-    "@babel/core": "^7.12.10",
-    "@babel/plugin-transform-typescript": "^7.12.17",
-    "@babel/preset-env": "^7.12.11",
-    "@eslint/js": "^9.9.1",
-    "@rollup/plugin-babel": "^6.0.3",
-    "@rollup/plugin-replace": "^6.0.3",
-    "@rollup/plugin-typescript": "^12.1.1",
-    "@types/jest": "^29.2.4",
-    "@types/node": "^20.11.20",
-    "babel-jest": "^29.0.1",
-    "eslint": "^9.9.1",
-    "eslint-config-prettier": "^10.1.8",
-    "fast-check": "^2.12.0",
-    "jest": "^29.0.1",
-    "jest-resolve": "^29.7.0",
-    "jest-ts-webcompat-resolver": "^1.0.0",
-    "prettier": "^3.0.2",
-    "rollup": "^4.12.0",
-    "tslib": "^2.8.1",
-    "typescript": "^5.7.2",
-    "typescript-eslint": "^8.4.0"
-  },
-  "engines": {
-    "node": ">= 14.6"
-  }
-}

package/node_modules/pi-subagents/node_modules/yaml/util.js

@@ -1,2 +0,0 @@
-// Re-exporter for Node.js < 12.16.0
-module.exports = require('./dist/util.js')

package/node_modules/pi-subagents/package.json

@@ -1,138 +0,0 @@
-{
-  "type": "module",
-  "name": "pi-subagents",
-  "version": "0.78.0",
-  "description": "Pi extension for single-agent delegation and scripted multi-agent workflows",
-  "author": "Nico Bailon",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/nicobailon/pi-subagents.git"
-  },
-  "homepage": "https://github.com/nicobailon/pi-subagents#readme",
-  "bugs": {
-    "url": "https://github.com/nicobailon/pi-subagents/issues"
-  },
-  "bin": {
-    "pi-subagents": "install.mjs"
-  },
-  "dependencies": {
-    "@js-temporal/polyfill": "0.5.1",
-    "acorn": "8.18.0",
-    "jiti": "2.7.0",
-    "undici": "8.10.2",
-    "yaml": "2.8.3"
-  },
-  "peerDependencies": {
-    "@earendil-works/pi-agent-core": "*",
-    "@earendil-works/pi-ai": ">=0.86.1",
-    "@earendil-works/pi-coding-agent": "*",
-    "@earendil-works/pi-tui": "*",
-    "typebox": "*"
-  },
-  "peerDependenciesMeta": {
-    "@earendil-works/pi-agent-core": {
-      "optional": true
-    },
-    "@earendil-works/pi-ai": {
-      "optional": true
-    },
-    "@earendil-works/pi-coding-agent": {
-      "optional": true
-    },
-    "@earendil-works/pi-tui": {
-      "optional": true
-    },
-    "typebox": {
-      "optional": true
-    }
-  },
-  "keywords": [
-    "pi-package",
-    "pi",
-    "pi-coding-agent",
-    "extension",
-    "subagents",
-    "ai",
-    "agents",
-    "cli"
-  ],
-  "types": "./index.d.ts",
-  "exports": {
-    ".": {
-      "types": "./index.d.ts",
-      "default": "./index.js"
-    },
-    "./background-work": {
-      "types": "./src/api/background-work.d.ts",
-      "default": "./src/api/background-work.js"
-    },
-    "./external-job-provider": {
-      "types": "./src/api/external-job-provider.d.ts",
-      "default": "./src/api/external-job-provider.js"
-    },
-    "./external-runs": {
-      "types": "./src/api/external-runs.d.ts",
-      "default": "./src/api/external-runs.js"
-    },
-    "./agents": {
-      "types": "./src/api/agents.d.ts",
-      "default": "./src/api/agents.js"
-    },
-    "./inspectors": {
-      "types": "./src/api/inspectors.d.ts",
-      "default": "./src/api/inspectors.js"
-    },
-    "./delegation": {
-      "types": "./src/api/delegation.d.ts",
-      "default": "./src/api/delegation.js"
-    },
-    "./capability-ceiling": {
-      "types": "./src/api/capability-ceiling.d.ts",
-      "default": "./src/api/capability-ceiling.js"
-    },
-    "./workflow-resources": {
-      "types": "./src/api/workflow-resources.d.ts",
-      "default": "./src/api/workflow-resources.js"
-    },
-    "./required-child-extensions": {
-      "types": "./src/api/required-child-extensions.d.ts",
-      "default": "./src/api/required-child-extensions.js"
-    },
-    "./preflight": {
-      "types": "./src/api/preflight.d.ts",
-      "default": "./src/api/preflight.js"
-    },
-    "./control-channel": {
-      "types": "./src/api/control-channel.d.ts",
-      "default": "./src/api/control-channel.js"
-    },
-    "./intercom-bridge": {
-      "types": "./src/api/intercom-bridge.d.ts",
-      "default": "./src/api/intercom-bridge.js"
-    },
-    "./child-tool-plan": {
-      "types": "./src/api/child-tool-plan.d.ts",
-      "default": "./src/api/child-tool-plan.js"
-    },
-    "./shared-types": {
-      "types": "./src/api/shared-types.d.ts",
-      "default": "./src/api/shared-types.js"
-    },
-    "./project-panes": {
-      "types": "./src/api/project-panes.d.ts",
-      "default": "./src/api/project-panes.js"
-    }
-  },
-  "pi": {
-    "extensions": [
-      "./index.js"
-    ],
-    "skills": [
-      "./skills"
-    ],
-    "prompts": [
-      "./prompts"
-    ]
-  }
-}

package/node_modules/pi-subagents/prompts/council.md

@@ -1,63 +0,0 @@
----
-description: Run a bounded supervisor-mediated council of advisors and write a decision memo
-argument-hint: "<question> [--advisors name,name] [--max-passes 2|3] [--scope ...] [--non-goals ...]"
----
-
-Run a bounded, supervisor-mediated council on this question. You, the parent
-session, are the supervisor. You select the roster, curate cross-advisor packets,
-decide which feedback is valid, and write the final memo. Advisors do not talk
-directly or see peer transcripts by default. This is not free-form agent chat.
-
-Before you orchestrate, load the council protocol with
-`subagent({ action: "guide", options: { topic: "council" } })`. If only `subagents_enable`
-is available, call it first; `subagent` is available on the next request. The
-guide returns the packaged council-mode skill and the references it asks you to
-read, so it also works when Pi runs with `--no-skills`.
-
-Parse the invocation yourself. The flags below are conventions, not runtime
-options. Record a brief with the question, scope, non-goals, evidence targets,
-roster, known advisor context modes, and pass cap. Default `--max-passes` to 2.
-Clamp it to 2 or 3. If the question is trivial or settled, answer directly instead
-of convening a council.
-
-## Roster
-
-- If `--advisors` is given, use exactly those agent names. Fail clearly on an
-  unknown agent. Do not require or invent per-advisor role labels.
-- Otherwise list agents with `subagent({ action: "list" })`, then prefer 2–3
-  executable names that start with `council-`.
-- If fewer than two profiles are available, fill the roster with `oracle`, then
-  `reviewer`, until it has two advisors. Launch fallback `oracle` with
-  `context: "fork"` so global defaults cannot remove its parent-chat context.
-  Let `reviewer` use its normal profile context. Note the fallback and known
-  context modes in the memo.
-- Use the normal single-oracle loop only when a requested roster or unavailable
-  builtins leaves fewer than two advisors. Label the memo as degraded mode.
-
-Profiles provide the model, tools, context, and advisor stance. The council
-question and scope provide the decision frame. If the user wants a specific lens,
-they should put it in the question, scope, or profile definition. Keep the roster
-at 2–3 and never exceed 4.
-
-Package advisors such as Surf's `gpt-pro` are valid only when the package Pi
-extension is installed and its external-job provider is registered. For Surf,
-that means the `surf-cli` Pi extension has loaded and `surf-oracle` appears in
-`subagent({ action: "list" })` or the advisor is explicitly requested in
-`--advisors` after that install. Treat them as external-runner advisors: omit
-child `async` for normal attached council results, do not pass `outputSchema`,
-include any needed evidence in the prompt, and use the fresh fallback cross-exam
-path if the run is not resumable.
-
-## Run the protocol
-
-Use the canonical workflow, structured advisor contracts, aggregate pass receipts,
-and memo requirements from the council guide. Keep the parent as the
-only synthesizer and decision maker. Do not introduce a chair advisor, peer chat,
-or transcript sharing.
-
-Use its required boundary checkpoints, yield for each async workflow without
-polling, and write its required final memo.
-
-Question and options from the slash command invocation:
-
-$@

package/node_modules/pi-subagents/prompts/gather-context-and-clarify.md

@@ -1,13 +0,0 @@
----
-description: Use subagents to gather context, then ask clarifying questions
----
-
-Based on our discussion and my intent, launch focused context-gathering subagents before planning or implementing.
-
-Use `scout` to inspect the relevant local files, existing patterns, constraints, tests, and likely integration points. Use `researcher` when external docs, recent sources, ecosystem context, or primary evidence would improve the answer.
-
-Give each subagent a specific meta prompt. Ask them to return concise findings plus the remaining clarification questions that matter for implementation confidence.
-
-After they return, synthesize what we know and use the `interview` tool to ask me the unresolved questions needed to reach a shared understanding.
-
-$@

package/node_modules/pi-subagents/prompts/parallel-cleanup.md

@@ -1,59 +0,0 @@
----
-description: Parallel cleanup review
----
-
-Run a fresh-context parallel cleanup review of the current work.
-
-Use the `subagent` tool. First inspect available agents/skills if needed, then launch two reviewer subagents in parallel with `context: "fresh"`. Do not use forked context unless I explicitly ask for it. Reviewers must inspect the repository, relevant instructions, and current diff directly from files and commands. They must not rely on the main conversation history.
-
-Do not write reviewer output files into the repository unless I explicitly ask for artifacts. Prefer `output: false` for each reviewer task.
-
-Reviewer 1: deslop pass.
-
-If the `deslop` skill is available, pass it to this reviewer. If not, inline the guidance below. Ask this reviewer to look for AI-slop patterns in the changed scope:
-- comments that restate code, placeholder text, stale rationale, or debug leftovers;
-- defensive checks that hide useful errors, return vague defaults, or validate trusted internal data after a real boundary was already crossed;
-- type escapes, broad casts, duplicated type definitions, or object-bag typing where a local source-of-truth type exists;
-- style drift from nearby non-slop code and project instructions;
-- generated-sounding docs, changelog text, UI copy, status text, or test names;
-- pass-through wrappers, dead helpers, duplicate helper signatures, duplicated test harness setup, or abstractions that do not enforce an invariant;
-- UI or CLI copy that is noisy, vague, brittle, or makes the user do extra interpretation.
-
-Tell this reviewer to treat tool output and slop-scan-style findings as leads, not verdicts. It should flag only concrete issues in the requested scope with evidence, severity, file/line references, and the smallest safe fix.
-
-Reviewer 2: verbosity pass.
-
-If the `verbosity-cleaner` skill is available, pass it to this reviewer. If not, inline the guidance below. Ask this reviewer to look for needless verbosity in code, tests, docs, status text, grouped messages, receipts, and changelog wording:
-- single-use helpers that merely paraphrase an expression;
-- temporary variables that only name obvious expressions;
-- nested returns or branches that can become direct returns without hiding intent;
-- multi-line cleanup scaffolding that can use a local direct pattern while preserving cleanup semantics;
-- repeated boilerplate that can use an existing local fixture or a small local helper;
-- tests that restate formatter details already covered at a cheaper layer;
-- regression tests where one focused assertion would cover the bug but wrapper/API-adjacent tests only repeat the same claim;
-- prose that says the same thing twice, sounds generic, or buries the important rule.
-
-Tell this reviewer that shorter is only better when it is clearer and preserves behavior, error signals, cleanup semantics, useful invariants, and local style.
-
-Both reviewers are review-only. They must not edit files unless I explicitly ask for a writer pass. Their response should be review feedback, not a context summary. Ask them to return concise, evidence-backed findings with file/line references and suggested fixes.
-
-While reviewers run, do your own narrow inspection if useful. After they return, synthesize the feedback into:
-- fixes worth doing now;
-- optional improvements;
-- feedback to ignore or defer, with a short reason.
-
-Do not blindly apply every reviewer suggestion.
-
-Autofix mode: if the invocation contains the exact word `autofix`, treat it as workflow control, not cleanup scope. Remove it before deciding the cleanup target. After synthesis, apply only fixes worth doing now, validate, and summarize. Do not apply optional improvements unless explicitly requested. If there are no fixes worth doing now, do not edit.
-
-Without autofix mode, ask before applying fixes unless I already told you to address review feedback. When you ask, end with a compact numbered menu so I can respond with a number. Use wording suited to the findings, but include these choices when applicable:
-
-```text
-Reply with [1], [2], or further instructions:
-[1] Apply only the fixes worth doing now.
-[2] Apply the fixes worth doing now plus optional improvements.
-```
-
-Additional scope or focus from the slash command invocation:
-
-$@

package/node_modules/pi-subagents/prompts/parallel-research.md

@@ -1,50 +0,0 @@
----
-description: Parallel subagents research
----
-
-Launch parallel research subagents to build a grounded answer to the current question or decision.
-
-Use fresh context, not forked context, unless I explicitly ask for forked context. Researchers and scouts should inspect sources directly instead of relying on the main conversation history.
-
-Use a combination of `researcher` and `scout` subagents:
-- Use `researcher` for web, docs, standards, ecosystem, recent changes, benchmarks, and primary-source evidence.
-- Use `scout` for local codebase context, existing implementation patterns, repo constraints, and files that would be affected.
-
-Give each subagent a distinct angle. Unless I specify angles, use these three:
-
-1. External evidence
-   Use `researcher` to find current, authoritative sources: official docs, specs, release notes, benchmarks, issue threads, or primary explanations.
-
-2. Local code context
-   Use `scout` to inspect the repository for relevant files, existing patterns, constraints, tests, and likely integration points.
-
-3. Practical tradeoffs
-   Use `researcher` or `scout`, whichever fits the question, to compare options, risks, edge cases, maintenance cost, and what would be easiest to validate.
-
-Adapt the angles when the question calls for it:
-- Library/API questions: include official docs and recent examples.
-- Architecture decisions: include local module boundaries, dependency direction, and migration cost.
-- Debugging questions: include likely failure modes, local call paths, and exact error evidence.
-- UI/product questions: include user flow, accessibility, design precedent, and implementation constraints.
-- Time-sensitive topics: include a recent-developments angle and prefer 2026/2025 sources.
-
-Prefer two or three strong subagents over many vague ones. The parent agent should frame the question and assign angles; the child agents should research or scout, not invent broad plans.
-
-Ask each subagent to return concise findings with evidence:
-- file paths and line ranges for local findings
-- source links for external findings
-- confidence level and gaps
-- recommended next step or decision implication
-
-Do not ask subagents to edit files. This is a research pass only unless I explicitly ask for implementation.
-
-After the subagents return, synthesize the answer into:
-- what we know
-- what the local codebase implies
-- tradeoffs and risks
-- gaps or assumptions
-- the recommended next move
-
-If findings disagree, call out the disagreement instead of smoothing it over.
-
-$@