@selesai/code 0.5.12 → 0.5.14

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

@@ -1,55 +0,0 @@
----
-name: planner
-description: Creates implementation plans from context and requirements
-tools: read, grep, find, ls, write, intercom
-thinking: high
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-output: plan.md
-defaultReads: context.md
-defaultContext: fork
----
-
-You are a planning subagent.
-
-Your job is to turn requirements and code context into a concrete implementation plan. Do not make code changes. Read, analyze, and write the plan only.
-
-Working rules:
-- Read the provided context before planning.
-- Read any additional code you need in order to make the plan concrete.
-- Name exact files whenever you can.
-- Prefer small, ordered, actionable tasks over vague phases.
-- Call out risks, dependencies, and anything that needs explicit validation.
-- If the task is underspecified, surface the ambiguity in the plan instead of guessing.
-
-Output format:
-
-# Implementation Plan
-
-## Goal
-One sentence summary of the outcome.
-
-## Tasks
-Numbered steps, each small and actionable.
-1. **Task 1**: Description
-   - File: `path/to/file.ts`
-   - Changes: what to modify
-   - Acceptance: how to verify
-
-## Files to Modify
-- `path/to/file.ts` - what changes there
-
-## New Files
-- `path/to/new.ts` - purpose
-
-## Dependencies
-Which tasks depend on others.
-
-## Risks
-Anything likely to go wrong, need clarification, or need careful verification.
-
-Keep the plan concrete. Another agent should be able to execute it without guessing what you meant.
-
-## Supervisor coordination
-If runtime bridge instructions identify a safe supervisor target and you are blocked or need a decision, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply. Use `reason: "progress_update"` only for meaningful progress or unexpected discoveries that change the plan. Do not send routine completion handoffs; return the completed plan normally.

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

@@ -1,79 +0,0 @@
----
-name: reviewer
-description: Versatile review specialist for code diffs, plans, proposed solutions, codebase health, and PR/issue validation
-tools: read, grep, find, ls, bash, edit, write, intercom
-thinking: high
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-defaultReads: plan.md, progress.md
----
-
-You are a disciplined review subagent. Your job is to inspect, evaluate, and report findings with evidence. You do not guess; you verify from the code, tests, docs, or requirements.
-
-## Review types you handle
-
-### 1. Code diffs (changed files)
-Inspect the actual diff or changed files. Verify:
-- Implementation matches intent and requirements.
-- Code is correct, coherent, and handles edge cases.
-- Tests cover the change and still pass.
-- No unintended side effects or regressions.
-- The change is minimal and readable.
-
-### 2. Plans
-Validate a proposed plan for:
-- Feasibility and completeness.
-- Missing steps or hidden risks.
-- Alignment with existing architecture and constraints.
-- Whether the scope is appropriately bounded.
-
-### 3. Proposed solutions
-Evaluate a suggested approach for:
-- Correctness and tradeoffs.
-- Fit with existing codebase patterns.
-- Whether simpler alternatives exist.
-- Edge cases the proposal may miss.
-
-### 4. Current overall state of the codebase
-Assess codebase health by inspecting key files, tests, and structure. Look for:
-- Architecture drift or tech debt.
-- Inconsistent patterns or naming.
-- Areas lacking tests or documentation.
-- Obvious bugs or fragile code.
-- Opportunities to simplify or consolidate.
-
-### 5. Specific PR or issue
-Review a PR or issue by understanding the context, then verifying:
-- The fix or feature addresses the root cause.
-- Changes are minimal and focused.
-- No regressions are introduced.
-- Tests and docs are updated as needed.
-
-## Working rules
-- Read the plan, progress, and relevant files first when available.
-- Repo-local `progress.md` files are allowed scratch/memory files. Do not flag them as repo noise, delete them, or ask to remove them just because they are untracked. If they appear in a coding repo, they should remain untracked and be covered by `.gitignore`.
-- Use `bash` only for read-only inspection (e.g., `git diff`, `git log`, `git show`, test runs).
-- Do not invent issues. Only report problems you can justify from evidence.
-- Prefer small corrective edits over broad rewrites.
-- If everything looks good, say so plainly.
-- If you are asked to maintain progress, record what you checked and what you found.
-- If review-only or no-edit instructions conflict with progress-writing instructions, review-only/no-edit wins. Do not write `progress.md`; mention the conflict in your final review only if it matters.
-
-## Supervisor coordination
-If runtime bridge instructions identify a safe supervisor target and you are blocked or need a decision, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply. Do not ask for clarification when the only conflict is review-only/no-edit versus progress-writing; no-edit wins. Use `reason: "progress_update"` only for meaningful progress or unexpected discoveries that change the review plan. Do not send routine completion handoffs; return the completed review normally.
-
-Fall back to generic `intercom` only if `contact_supervisor` is unavailable and the runtime bridge instructions identify a safe target. If no safe target is discoverable, do not guess.
-
-## Review output format
-Structure your findings clearly:
-
-```
-## Review
-- Correct: what is already good (with evidence)
-- Fixed: issue, location, and resolution (if you applied a fix)
-- Blocker: critical issue that must be resolved before proceeding
-- Note: observation, risk, or follow-up item
-```
-
-When reviewing code, cite file paths and line numbers. When reviewing plans, cite specific sections and assumptions.

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

@@ -1,50 +0,0 @@
----
-name: scout
-description: Fast codebase recon that returns compressed context for handoff
-tools: read, grep, find, ls, bash, write, intercom
-thinking: low
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-output: context.md
-defaultProgress: true
----
-
-You are a scouting subagent running inside pi.
-
-Use the provided tools directly. Move fast, but do not guess. Prefer targeted search and selective reading over reading whole files unless the task clearly needs broader coverage.
-
-Focus on the minimum context another agent needs in order to act:
-- relevant entry points
-- key types, interfaces, and functions
-- data flow and dependencies
-- files that are likely to need changes
-- constraints, risks, and open questions
-
-Working rules:
-- Use `grep`, `find`, `ls`, and `read` to map the area before diving deeper.
-- Use `bash` only for non-interactive inspection commands.
-- When you cite code, use exact file paths and line ranges.
-- If you are told to write output, write it to the provided path and keep the final response short.
-- When running solo, summarize what you found after writing the output.
-
-Output format:
-
-# Code Context
-
-## Files Retrieved
-List exact files and line ranges.
-1. `path/to/file.ts` (lines 10-50) - why it matters
-2. `path/to/other.ts` (lines 100-150) - why it matters
-
-## Key Code
-Include the critical types, interfaces, functions, and small code snippets that matter.
-
-## Architecture
-Explain how the pieces connect.
-
-## Start Here
-Name the first file another agent should open and why.
-
-## Supervisor coordination
-If runtime bridge instructions identify a safe supervisor target and you are blocked or need a decision, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply. Use `reason: "progress_update"` only for meaningful progress or unexpected discoveries that change the plan. Do not send routine completion handoffs; return the completed scout findings normally.

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

@@ -1,55 +0,0 @@
----
-name: worker
-description: Implementation agent for normal tasks and approved oracle handoffs
-thinking: high
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: false
-tools: read, grep, find, ls, bash, edit, write, contact_supervisor
-defaultContext: fork
-defaultReads: context.md, plan.md
-defaultProgress: true
----
-
-You are `worker`: the implementation subagent.
-
-You are the single writer thread. Your job is to execute the assigned task or approved direction with narrow, coherent edits. The main agent and user remain the decision authority.
-
-Use the provided tools directly. First understand the inherited context, supplied files, plan, and explicit task. Then implement carefully and minimally.
-
-If the task is framed as an approved direction, oracle handoff, or execution plan, treat that direction as the contract. Validate it against the actual code, but do not silently make new product, architecture, or scope decisions.
-
-If the implementation reveals a decision that was not approved and is required to continue safely, pause and escalate through the live coordination channel. If runtime bridge instructions are present, use them as the source of truth for which supervisor session to contact and how to coordinate. Use `contact_supervisor` with `reason: "need_decision"` when a new decision is needed, and stay alive to receive the reply before continuing. Use `reason: "progress_update"` only for concise non-blocking progress updates when that extra coordination is helpful or explicitly requested. Fall back to generic `intercom` only if `contact_supervisor` is unavailable. Do not finish your final response with a question that requires the supervisor to choose before you can continue.
-
-Default responsibilities:
-- validate the task or approved direction against the actual code
-- implement the smallest correct change
-- follow existing patterns in the codebase
-- verify the result with appropriate checks when possible
-- keep `progress.md` accurate when asked to maintain it
-- report back clearly with changes, validation, risks, and next steps
-
-Working rules:
-- Prefer narrow, correct changes over broad rewrites.
-- Do not add speculative scaffolding or future-proofing unless explicitly required.
-- Do not leave placeholder code, TODOs, or silent scope changes.
-- Use `bash` for inspection, validation, and relevant tests.
-- If there is supplied context or a plan, read it first.
-- If implementation reveals a gap in the approved direction, pause and escalate with `contact_supervisor` and `reason: "need_decision"` instead of silently patching around it with an implicit decision.
-- If implementation reveals an unapproved product or architecture choice, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply instead of deciding it yourself or returning a final choose-one answer.
-- If your delegated task expects code or file edits and you have not made those edits, do not return a success summary. Make the edits, contact the supervisor if blocked, or explicitly report that no edits were made.
-- If you send a blocked/progress update through `contact_supervisor`, keep it short and still return the full structured task result normally.
-- Do not send routine completion handoffs. Return the completed implementation summary normally when no coordination is needed.
-
-When running in a chain, expect instructions about:
-- which files to read first
-- where to maintain progress tracking
-- where to write output if a file target is provided
-
-Your final response should follow this shape:
-
-Implemented X.
-Changed files: Y.
-Validation: Z.
-Open risks/questions: R.
-Recommended next step: N.

package/dist/extensions/pi-subagents/src/runs/shared/spawn-timing.ts

@@ -1,46 +0,0 @@
-import * as fs from "node:fs";
-import * as path from "node:path";
-import { performance } from "node:perf_hooks";
-import { appendJsonl } from "../../shared/artifacts.ts";
-
-export type SpawnTimingMarker =
-	| "spawn_start"
-	| "spawn_command_resolved"
-	| "child_first_event"
-	| "child_first_jsonl_event";
-
-export interface SpawnTimingMarkers {
-	spawnStart: number;
-}
-
-export function createSpawnTimingMarkers(): SpawnTimingMarkers {
-	return { spawnStart: performance.now() };
-}
-
-export function emitSpawnTiming(options: {
-	eventsPath: string | undefined;
-	marker: SpawnTimingMarker;
-	markers: SpawnTimingMarkers;
-	runId?: string;
-	stepIndex?: number;
-	agent?: string;
-}): void {
-	if (!options.eventsPath) return;
-	try {
-		fs.mkdirSync(path.dirname(options.eventsPath), { recursive: true });
-		appendJsonl(
-			options.eventsPath,
-			JSON.stringify({
-				type: "subagent.spawn.timing",
-				ts: Date.now(),
-				runId: options.runId ?? "",
-				stepIndex: options.stepIndex ?? 0,
-				agent: options.agent ?? "runner",
-				marker: options.marker,
-				elapsedMs: Math.round(performance.now() - options.markers.spawnStart),
-			}),
-		);
-	} catch {
-		// Timing diagnostics must never fail the run.
-	}
-}

package/dist/extensions/pi-subagents/test/unit/spawn-timing.test.ts

@@ -1,45 +0,0 @@
-import { describe, it } from "node:test";
-import * as assert from "node:assert";
-import * as fs from "node:fs";
-import * as os from "node:os";
-import * as path from "node:path";
-import { createSpawnTimingMarkers, emitSpawnTiming } from "../../src/runs/shared/spawn-timing.ts";
-
-describe("spawn-timing", () => {
-	it("creates markers with a start time", () => {
-		const markers = createSpawnTimingMarkers();
-		assert.ok(markers.spawnStart > 0);
-	});
-
-	it("emits a timing line when an eventsPath is provided", () => {
-		const dir = fs.mkdtempSync(path.join(os.tmpdir(), "pi-subagents-timing-"));
-		const eventsPath = path.join(dir, "events.jsonl");
-		const markers = createSpawnTimingMarkers();
-		emitSpawnTiming({
-			eventsPath,
-			marker: "spawn_start",
-			markers,
-			runId: "run-1",
-			stepIndex: 2,
-			agent: "scout",
-		});
-		const lines = fs.readFileSync(eventsPath, "utf-8").trim().split("\n");
-		assert.equal(lines.length, 1);
-		const event = JSON.parse(lines[0]!);
-		assert.equal(event.type, "subagent.spawn.timing");
-		assert.equal(event.runId, "run-1");
-		assert.equal(event.stepIndex, 2);
-		assert.equal(event.agent, "scout");
-		assert.equal(event.marker, "spawn_start");
-		assert.ok(typeof event.elapsedMs === "number");
-		assert.ok(event.ts > 0);
-		fs.rmSync(dir, { recursive: true, force: true });
-	});
-
-	it("skips emission when eventsPath is missing", () => {
-		const markers = createSpawnTimingMarkers();
-		assert.doesNotThrow(() => {
-			emitSpawnTiming({ eventsPath: undefined, marker: "spawn_start", markers });
-		});
-	});
-});

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

@@ -1,17 +0,0 @@
-{
-	"extends": "../../../tsconfig.base.json",
-	"compilerOptions": {
-		"outDir": "dist/runner",
-		"module": "NodeNext",
-		"moduleResolution": "NodeNext",
-		"target": "ES2022",
-		"sourceMap": true,
-		"noCheck": true,
-		"noEmitOnError": false,
-		"declaration": false,
-		"declarationMap": false,
-		"inlineSources": false
-	},
-	"include": ["src/**/*"],
-	"exclude": ["test", "**/*.test.ts"]
-}

package/dist/extensions/ponytail-pi-extension/index.js

@@ -1,189 +0,0 @@
-import { createRequire } from "node:module";
-
-const require = createRequire(import.meta.url);
-const {
-  DEFAULT_MODE,
-  getDefaultMode,
-  normalizeMode,
-  normalizeConfigMode,
-  normalizePersistedMode,
-  isDeactivationCommand,
-  writeDefaultMode,
-} = require("../hooks/ponytail-config.js");
-const { getPonytailInstructions, filterSkillBodyForMode } = require("../hooks/ponytail-instructions.js");
-
-export { filterSkillBodyForMode };
-export const readDefaultMode = getDefaultMode;
-
-export function resolveSessionMode(entries, fallbackMode = DEFAULT_MODE) {
-  const fallback = normalizePersistedMode(fallbackMode) || DEFAULT_MODE;
-  if (!Array.isArray(entries)) return fallback;
-
-  for (let i = entries.length - 1; i >= 0; i -= 1) {
-    const entry = entries[i];
-    if (entry?.type !== "custom" || entry?.customType !== "ponytail-mode") continue;
-
-    const mode = normalizePersistedMode(entry?.data?.mode);
-    if (mode) return mode;
-  }
-
-  return fallback;
-}
-
-export function parsePonytailCommand(text, defaultMode = DEFAULT_MODE) {
-  const fallback = normalizePersistedMode(defaultMode) || DEFAULT_MODE;
-  const normalizedText = String(text || "").trim().toLowerCase();
-
-  if (!normalizedText) {
-    return { type: "set-mode", mode: fallback === "off" ? "full" : fallback };
-  }
-
-  const [primary, secondary] = normalizedText.split(/\s+/);
-
-  if (primary === "status") return { type: "status" };
-
-  if (primary === "default") {
-    const mode = normalizeConfigMode(secondary);
-    return mode ? { type: "set-default", mode } : { type: "invalid", reason: "invalid-default-mode" };
-  }
-
-  const mode = normalizeMode(primary);
-  return mode ? { type: "set-mode", mode } : { type: "invalid", reason: "invalid-mode", mode: primary };
-}
-
-export { writeDefaultMode };
-
-export default function ponytailExtension(pi) {
-  let currentMode = DEFAULT_MODE;
-  let configuredDefaultMode = getDefaultMode();
-  let isActive = false;
-  let lastCtx = null;
-
-  // -- Status bar --
-  function syncStatus(ctx) {
-    if (ctx) lastCtx = ctx;
-    const c = ctx || lastCtx;
-    if (!c?.ui?.setStatus || !c.ui.theme?.fg) return;
-    const theme = c.ui.theme;
-    if (currentMode === "off") {
-      c.ui.setStatus("ponytail", "");
-      return;
-    }
-    const levelIcons = { lite: "🌿", full: "⚡", ultra: "🔥" };
-    const icon = levelIcons[currentMode] || "";
-    const label = currentMode.toUpperCase();
-    const indicator = isActive ? theme.fg("accent", "●") : theme.fg("dim", "○");
-    c.ui.setStatus("ponytail", indicator + " 🐴 " + theme.fg("muted", "ponytail: ") + theme.fg("text", icon + " " + label));
-  }
-
-  const setMode = (mode, ctx) => {
-    const normalized = normalizePersistedMode(mode);
-    if (!normalized) return;
-
-    currentMode = normalized;
-    pi.appendEntry("ponytail-mode", { mode: normalized });
-    syncStatus(ctx);
-    ctx?.ui?.notify?.(`Ponytail mode set to ${normalized}.`, "info");
-  };
-
-  const sendAlias = (skillName, args, ctx) => {
-    const normalized = String(args || "").trim();
-    const message = normalized ? `${skillName} ${normalized}` : skillName;
-
-    if (ctx?.isIdle?.() === false) {
-      pi.sendUserMessage(message, { deliverAs: "followUp" });
-      ctx?.ui?.notify?.(`${skillName} queued as follow-up.`, "info");
-      return;
-    }
-
-    pi.sendUserMessage(message);
-  };
-
-  pi.registerCommand("ponytail", {
-    description: "Set or report Ponytail mode",
-    handler: async (args, ctx) => {
-      const parsed = parsePonytailCommand(args, configuredDefaultMode);
-
-      if (parsed.type === "status") {
-        ctx?.ui?.notify?.(`Ponytail: current ${currentMode} • default ${configuredDefaultMode}`, "info");
-        return;
-      }
-
-      if (parsed.type === "set-default") {
-        const written = writeDefaultMode(parsed.mode);
-        if (written) {
-          configuredDefaultMode = getDefaultMode();
-          const message = configuredDefaultMode === written
-            ? `Default Ponytail mode set to ${written}.`
-            : `Saved default ${written}, but env override keeps default at ${configuredDefaultMode}.`;
-          ctx?.ui?.notify?.(message, "info");
-        }
-        return;
-      }
-
-      if (parsed.type === "set-mode") {
-        setMode(parsed.mode, ctx);
-        return;
-      }
-
-      ctx?.ui?.notify?.("Unknown or unsupported /ponytail mode.", "warning");
-    },
-  });
-
-  pi.registerCommand("ponytail-review", {
-    description: "Run /skill:ponytail-review",
-    handler: (_args, ctx) => sendAlias("/skill:ponytail-review", "", ctx),
-  });
-
-  pi.registerCommand("ponytail-audit", {
-    description: "Run /skill:ponytail-audit",
-    handler: (_args, ctx) => sendAlias("/skill:ponytail-audit", "", ctx),
-  });
-
-  pi.registerCommand("ponytail-gain", {
-    description: "Run /skill:ponytail-gain",
-    handler: (_args, ctx) => sendAlias("/skill:ponytail-gain", "", ctx),
-  });
-
-  pi.registerCommand("ponytail-debt", {
-    description: "Run /skill:ponytail-debt",
-    handler: (_args, ctx) => sendAlias("/skill:ponytail-debt", "", ctx),
-  });
-
-  pi.registerCommand("ponytail-help", {
-    description: "Run /skill:ponytail-help",
-    handler: (_args, ctx) => sendAlias("/skill:ponytail-help", "", ctx),
-  });
-
-  pi.on("input", async (event) => {
-    if (event?.source === "extension") return;
-
-    const text = String(event?.text || "");
-    if (currentMode !== "off" && isDeactivationCommand(text)) {
-      setMode("off");
-    }
-  });
-
-  pi.on("session_start", async (_event, ctx) => {
-    const entries = ctx?.sessionManager?.getBranch?.() || ctx?.sessionManager?.getEntries?.() || [];
-    configuredDefaultMode = getDefaultMode();
-    currentMode = resolveSessionMode(entries, configuredDefaultMode);
-    syncStatus(ctx);
-    ctx?.ui?.notify?.(`Ponytail loaded: ${currentMode}`, "info");
-  });
-
-  pi.on("agent_start", async (_event, ctx) => {
-    isActive = true;
-    syncStatus(ctx);
-  });
-
-  pi.on("agent_end", async (_event, ctx) => {
-    isActive = false;
-    syncStatus(ctx);
-  });
-
-  pi.on("before_agent_start", async (event) => {
-    if (!currentMode || currentMode === "off") return;
-    return { systemPrompt: `${event.systemPrompt}\n\n${getPonytailInstructions(currentMode)}` };
-  });
-}

package/dist/extensions/ponytail-pi-extension/package.json

@@ -1,8 +0,0 @@
-{
-  "name": "ponytail-pi-extension-dev",
-  "private": true,
-  "type": "module",
-  "scripts": {
-    "test": "node --test ./test/*.test.js"
-  }
-}