@msdavid/pi-distro 0.2.0 → 0.3.0

package/harnesses/pi-distro-one/harness.md

@@ -1,79 +0,0 @@
----
-name: pi-distro-one
-title: pi-distro-one
-description: "A Claude Code–style coding agent distribution built around autonomous sub-agent spawning and coordination, with web research, browser automation, live shell, model routing, and task management in support. Includes a Claude-style status line and an explore-before-acting approach."
-version: 0.3.0
-tags: [full-config, claude-code-style]
----
-
-# pi-distro-one
-
-A complete interactive coding agent configuration that attempts to mimic as closely as
-possible the functionality of today's Claude Code. The primary capability is spawning and
-coordinating autonomous sub-agents; the remaining functionality is integrated in support
-of that.
-
-## Bundled files
-The following bundled files are provided under `files/` and should be placed into the
-target project. For any path that already exists, do NOT overwrite — show the user a diff
-and ask whether to overwrite, keep theirs, or merge. Merge JSON settings field-by-field.
-Append AGENTS.md content under a delimited section if one exists.
-
-- `files/AGENTS.md` → `./AGENTS.md`
-- `files/settings.json` → `./.pi/settings.json` (merge with existing settings)
-- `files/.pi/extensions/claude-statusline.ts` → `./.pi/extensions/claude-statusline.ts`
-
-## pi packages to install
-Use `pi install -l` to install the following **project-locally** (writes to
-`./.pi/settings.json` on success, leaves settings untouched on failure). Confirm with the
-user before each install. Do NOT pre-add these to the bundled `settings.json` `packages`
-array — `pi install -l` is the single registration mechanism.
-
-- `npm:@tintinweb/pi-subagents` — Claude Code–style autonomous sub-agents: spawn
-  specialized agents in isolated sessions, each with its own tools, system prompt, model,
-  and thinking level; parallel execution, a live monitoring widget, mid-run steering, and
-  session resumption (the primary capability of this distribution)
-- `npm:pi-web-access` — web search, URL fetching, GitHub cloning, PDF/video extraction
-- `npm:pi-agent-browser-native` — real browser automation and web interaction
-- `npm:pi-bash-live-view` — live terminal rendering for shell commands
-- `npm:@yeliu84/pi-model-router` — model routing / fallback across providers
-- `npm:@robhowley/pi-openrouter` — OpenRouter provider integration
-- `npm:@juicesharp/rpiv-todo` — task list management
-- `npm:pi-goal` — persistent autonomous goals: `/goal` loops until complete, paused, or
-  budget-limited, so long-running objectives survive across turns without manual babysitting
-- `npm:@trevonistrevon/pi-loop` — cron/event-based agent re-wake loops and background
-  process monitoring: schedule agents to re-wake on time or events and keep long-running
-  or background work alive without manual babysitting
-- `npm:@juicesharp/rpiv-ask-user-question` — structured questionnaire the model can put to
-  the user when it would otherwise guess, with typed options instead of free-form replies
-  (reduces ambiguous decisions and keeps the user in the loop on judgment calls)
-
-**Tool-name conflict check:** before installing, cross-check each package's purpose
-against the already-active tools in the target project (run `pi list`). If a package
-overlaps an existing tool — either an exact name collision or semantic redundancy
-(different names, similar function) — offer **skip / replace / keep both / cancel** instead
-of installing blindly. (Exact name collisions are non-fatal in pi — project-local tools
-shadow global ones — but redundancy leaves a confusing duplicate tool set.)
-
-## Custom extension (bundled)
-`files/.pi/extensions/claude-statusline.ts` is a Claude-style status-line footer
-(model | dir | thinking level | context-window bar gauge + cache % | git branch status).
-It auto-enables on session start and is toggleable via the `/claude-statusline` command.
-It also **auto-expands tool outputs** on session start (the Ctrl+O effect) so full output
-is visible by default, while keeping thinking blocks hidden for a clean working view.
-Deploy it to `./.pi/extensions/claude-statusline.ts`; pi loads it via jiti on next start
-(no build step). It depends only on pi core (`@earendil-works/pi-coding-agent`,
-`@earendil-works/pi-ai`, `@earendil-works/pi-tui`) — all provided as peer deps.
-
-## Settings (bundled)
-`files/settings.json` provides the agent's defaults: high thinking level, one-at-a-time
-steering, hidden thinking blocks, and hardware cursor. Tool outputs are auto-expanded on
-start (via the status-line extension). Merge with any existing `.pi/settings.json`
-field-by-field. Auth and model/provider configuration are not part of this distribution —
-configure those independently.
-
-## Context
-The bundled `AGENTS.md` is an explore-before-acting working methodology: investigate
-before implementing, surface interpretations and tradeoffs, make surgical changes, keep
-solutions simple, execute against verifiable goals, and treat documentation as part of the
-implementation. Deploy it to `./AGENTS.md` so the agent follows these conventions.

package/harnesses/web-fullstack/README.md

@@ -1,25 +0,0 @@
-# web-fullstack
-
-A full-stack React/Node project configuration with web research, code review, and a
-restricted tool set.
-
-## What it sets up
-
-- **`AGENTS.md`** — frontend and backend conventions, testing guidance, and a code
-  review process tailored to React/Node projects.
-- **`.pi/settings.json`** — sensible defaults with a restricted tools allowlist (only
-  the essential tools, keeping the agent focused).
-- **`.pi/prompts/review.md`** — a review prompt template for on-demand structured code
-  reviews.
-
-## Packages installed
-
-- **`npm:pi-browse`** — web search (Brave / DuckDuckGo / Exa / Gemini) and content
-  extraction. Used for documentation lookup, API verification, and research.
-
-## When to use
-
-- You're building a React/Node full-stack application.
-- You want web research built in for looking up docs and APIs.
-- You want a structured code review workflow.
-- You prefer a restricted tool set over the full default set.

package/harnesses/web-fullstack/files/.pi/prompts/review.md

@@ -1,12 +0,0 @@
-# Code Review
-
-Review the changes for: correctness, security, performance, accessibility, and test coverage.
-Provide specific, actionable feedback referencing line numbers or code blocks.
-
-## Checklist
-
-- **Correctness**: Does the code do what it claims? Are edge cases handled?
-- **Security**: Are inputs validated? Are secrets handled safely? Any injection risks?
-- **Performance**: Are there unnecessary re-renders, N+1 queries, or blocking operations?
-- **Accessibility**: Are semantic HTML elements used? Are interactive elements keyboard-accessible?
-- **Test coverage**: Are the new behaviors tested? Do existing tests still pass?

package/harnesses/web-fullstack/files/AGENTS.md

@@ -1,37 +0,0 @@
-# Project Instructions — Full-Stack Web
-
-Guidance for working in this React/Node full-stack project.
-
-## Frontend Conventions (React/Next.js)
-
-- Use TypeScript for all frontend code.
-- Prefer function components with hooks over class components.
-- Use named exports for components; default export only for page components.
-- Co-locate component styles using CSS Modules or Tailwind utility classes.
-- Keep components small and composable — extract reusable logic into custom hooks.
-- Use `next/navigation` (App Router) for routing in Next.js projects.
-
-## Backend Conventions (Node/Express)
-
-- Use TypeScript for all backend code.
-- Structure API routes with clear separation: controller → service → data layer.
-- Validate all request inputs with a schema validation library (e.g. zod, typebox).
-- Return consistent error response shapes: `{ error: { code, message, details? } }`.
-- Use environment variables for configuration; never hardcode secrets.
-- Prefer async/await over callback chains.
-
-## Testing
-
-- Write tests alongside the code they verify (co-located `*.test.ts` or `__tests__/`).
-- Use Vitest or Jest for unit/integration tests.
-- Use Playwright or Cypress for end-to-end tests.
-- Aim for meaningful coverage of business logic, not 100% line coverage.
-- Run tests in CI on every pull request.
-
-## Code Review Process
-
-- All changes require at least one approving review before merge.
-- Use the review prompt template at `.pi/prompts/review.md` for structured reviews.
-- Focus reviews on: correctness, security, performance, accessibility, and test coverage.
-- Provide specific, actionable feedback. Reference line numbers or code blocks.
-- Approve only when all blocking comments are resolved.

package/harnesses/web-fullstack/files/settings.json

@@ -1,11 +0,0 @@
-{
-  "tools": [
-    "read",
-    "bash",
-    "edit",
-    "write",
-    "grep",
-    "find",
-    "ls"
-  ]
-}

package/harnesses/web-fullstack/harness.md

@@ -1,40 +0,0 @@
----
-name: web-fullstack
-title: Full-Stack Web
-description: "React/Node project with web-research + review skills, review-oriented context, and a sensible tools allowlist."
-version: 0.1.0
-tags: [web, react, node]
----
-
-# Full-Stack Web
-
-## Bundled files
-The following bundled files are provided under `files/` and should be placed into the
-target project. For any path that already exists, do NOT overwrite — show the user a diff
-and ask whether to overwrite, keep theirs, or merge. Merge JSON settings objects field by
-field. Append (not replace) `AGENTS.md` content under a clearly-delimited section.
-
-- `files/AGENTS.md` → `./AGENTS.md`
-- `files/settings.json` → `./.pi/settings.json` (merge with existing settings)
-- `files/.pi/prompts/review.md` → `./.pi/prompts/review.md`
-
-## pi packages to install
-Use `pi install -l` to install the following **project-locally** (writes to `./.pi/settings.json`
-on success, and does nothing on failure). Confirm with the user before each install. Do NOT
-pre-add these packages to the bundled `settings.json` — `pi install -l` is the single source
-of truth that registers a package, so that a failed install never leaves a dangling entry
-in settings.
-
-- `npm:pi-browse` — web search (Brave/DuckDuckGo/Exa/Gemini) and content extraction for
-  documentation lookup and API verification
-
-## Context
-This harness sets up a full-stack web project with React/Node conventions. The bundled
-`AGENTS.md` contains frontend and backend conventions, testing guidance, and a code review
-process. The `settings.json` restricts the tools allowlist to the essential set. A review
-prompt template is included under `.pi/prompts/` for on-demand code reviews.
-
-## Skills / prompts
-- The `pi-browse` package (installed above) provides web research capabilities.
-- A review prompt template is bundled at `files/.pi/prompts/review.md` and deployed to
-  `./.pi/prompts/review.md`. Use it to run structured code reviews on changes.