ultimate-pi 0.12.0 → 0.13.0

package/.pi/scripts/harness-cli-verify.sh

@@ -231,22 +231,32 @@ verify_ctx7() {
 	fi
 }
 
-verify_ck() {
-	log "[ck-search]"
-	npm_global_install "@beaconbay/ck-search" "ck" || { fail "ck-search npm install"; return; }
-	if ! ck --version &>/dev/null; then
-		fail "ck --version failed"
+verify_cocoindex() {
+	log "[cocoindex-code]"
+	local _bootstrap
+	_bootstrap="$(cd "$(dirname "${BASH_SOURCE[0]:-$0}")" && pwd)/harness-cocoindex-bootstrap.sh"
+	if [ ! -f "$_bootstrap" ]; then
+		fail "harness-cocoindex-bootstrap.sh missing"
 		return
 	fi
-	# Fast grep-mode smoke (no embedding model download)
-	local ck_target="."
-	[ -d .pi ] && ck_target=".pi"
-	if ck -l 1 "export" "$ck_target" 2>/dev/null | head -1 | grep -q .; then
-		pass "ck $(ck --version 2>/dev/null | head -1)"
-	elif ck --status "$ck_target" 2>/dev/null | head -1 | grep -q .; then
-		pass "ck $(ck --version 2>/dev/null | head -1) (index status ok)"
+	if [ "$FORCE" = true ]; then
+		bash "$_bootstrap" --force || { fail "cocoindex bootstrap --force"; return; }
+	else
+		bash "$_bootstrap" || { fail "cocoindex bootstrap"; return; }
+	fi
+	if ! command -v ccc &>/dev/null; then
+		fail "ccc not on PATH after bootstrap"
+		return
+	fi
+	if ! ccc doctor &>/dev/null; then
+		warn "ccc doctor reported issues (daemon/model/SQLite)"
+	fi
+	if ccc search --limit 3 "export function" 2>/dev/null | head -1 | grep -qE '\.(ts|js|py|md)|\[|score|path'; then
+		pass "cocoindex-code (ccc search smoke)"
+	elif ccc status 2>/dev/null | head -1 | grep -q .; then
+		pass "cocoindex-code (index present; search empty on tiny corpus)"
 	else
-		warn "ck installed but smoke search empty"
+		warn "cocoindex installed but smoke search empty — first [full] install downloads local embedding model"
 	fi
 }
 
@@ -335,7 +345,7 @@ log ""
 verify_scrapling
 verify_ctx7
 verify_agent_browser
-verify_ck
+verify_cocoindex
 verify_biome
 verify_sg
 verify_gh

package/.pi/scripts/harness-cocoindex-bootstrap.sh

@@ -0,0 +1,182 @@
+#!/usr/bin/env bash
+# harness-cocoindex-bootstrap — install CocoIndex Code (ccc), seed settings, build index.
+# Non-interactive (no `ccc init` prompts). Used by harness-cli-verify and /harness-setup.
+
+set -euo pipefail
+
+FORCE=false
+for arg in "$@"; do
+	case "$arg" in
+	--force) FORCE=true ;;
+	-h | --help)
+		echo "Usage: $0 [--force]"
+		echo "  --force   rebuild index even when cocoindex.db exists"
+		exit 0
+		;;
+	*)
+		echo "Unknown argument: $arg" >&2
+		exit 2
+		;;
+	esac
+done
+
+export PATH="${HOME}/.local/bin:${PATH}"
+
+log() { printf '%s\n' "$*"; }
+die() { printf 'error: %s\n' "$*" >&2; exit 1; }
+
+ROOT="$(pwd)"
+
+if ! python3 --version 2>/dev/null | grep -qE 'Python 3\.(1[0-9]|[2-9][0-9])'; then
+	die "Python 3.10+ required (got: $(python3 --version 2>/dev/null || echo missing))"
+fi
+log "✓ Python 3.10+"
+
+cocoindex_installed() {
+	command -v ccc &>/dev/null && return 0
+	command -v uv &>/dev/null && uv tool list 2>/dev/null | grep -qE '(^|[[:space:]])cocoindex-code([[:space:]]|$)' && return 0
+	return 1
+}
+
+install_cocoindex() {
+	if command -v uv &>/dev/null; then
+		log "Installing cocoindex-code[full] via uv tool..."
+		uv tool install 'cocoindex-code[full]'
+	elif command -v pipx &>/dev/null; then
+		log "Installing cocoindex-code[full] via pipx..."
+		pipx install 'cocoindex-code[full]'
+	else
+		die "Need uv or pipx to install cocoindex-code[full]"
+	fi
+	export PATH="${HOME}/.local/bin:${PATH}"
+	command -v ccc &>/dev/null || die "ccc not on PATH after install"
+}
+
+if ! cocoindex_installed; then
+	install_cocoindex
+fi
+command -v ccc &>/dev/null || die "ccc CLI not found"
+log "✓ ccc ($(command -v ccc))"
+
+CCC_BIN="$(command -v ccc)"
+CCC_PYTHON=""
+if [ -f "$CCC_BIN" ]; then
+	CCC_PYTHON="$(sed -n '1s/^#!//p' "$CCC_BIN" | tr -d '\r')"
+fi
+if [ -z "$CCC_PYTHON" ] || [ ! -x "$CCC_PYTHON" ]; then
+	CCC_VENV="$(cd "$(dirname "$CCC_BIN")/.." && pwd)"
+	CCC_PYTHON="$CCC_VENV/bin/python"
+fi
+if [ ! -x "$CCC_PYTHON" ]; then
+	CCC_PYTHON="$(command -v python3)"
+fi
+
+# Seed global + project settings and merge harness exclude_patterns (non-interactive).
+"$CCC_PYTHON" - <<'PY'
+from __future__ import annotations
+
+import os
+import sys
+from pathlib import Path
+
+try:
+    import yaml
+except ImportError:
+    print("error: PyYAML required for harness cocoindex bootstrap", file=sys.stderr)
+    sys.exit(1)
+
+ROOT = Path(os.environ.get("HARNESS_COCOINDEX_ROOT", ".")).resolve()
+SETTINGS_DIR = ROOT / ".cocoindex_code"
+PROJECT_SETTINGS = SETTINGS_DIR / "settings.yml"
+USER_DIR = Path.home() / ".cocoindex_code"
+USER_SETTINGS = USER_DIR / "global_settings.yml"
+
+HARNESS_EXCLUDES = [
+    "graphify-out/**",
+    "raw/**",
+    ".raw/**",
+    ".pi/wiki-search/**",
+    "vendor/**",
+    "node_modules/**",
+    "**/graph.html",
+    "**/*.jsonl",
+    ".cursor/**",
+]
+
+DEFAULT_GLOBAL = {
+    "embedding": {
+        "provider": "sentence-transformers",
+        "model": "Snowflake/snowflake-arctic-embed-xs",
+    }
+}
+
+
+def load_yaml(path: Path) -> dict:
+    if not path.is_file():
+        return {}
+    data = yaml.safe_load(path.read_text(encoding="utf-8"))
+    return data if isinstance(data, dict) else {}
+
+
+def save_yaml(path: Path, data: dict) -> None:
+    path.parent.mkdir(parents=True, exist_ok=True)
+    path.write_text(yaml.safe_dump(data, default_flow_style=False), encoding="utf-8")
+
+
+# Global settings (offline embeddings — no LiteLLM prompt).
+if not USER_SETTINGS.is_file():
+    save_yaml(USER_SETTINGS, DEFAULT_GLOBAL)
+    print(f"Created {USER_SETTINGS}")
+
+# Project settings — minimal file with merged excludes only.
+project = load_yaml(PROJECT_SETTINGS)
+excludes = list(project.get("exclude_patterns") or [])
+seen = set(excludes)
+for pat in HARNESS_EXCLUDES:
+    if pat not in seen:
+        excludes.append(pat)
+        seen.add(pat)
+project["exclude_patterns"] = excludes
+save_yaml(PROJECT_SETTINGS, project)
+print(f"Ensured project settings: {PROJECT_SETTINGS}")
+
+# .gitignore entry (mirror ccc init behavior).
+gitignore = ROOT / ".gitignore"
+entry = "/.cocoindex_code/"
+comment = "# CocoIndex Code (ccc)"
+if (ROOT / ".git").is_dir() and gitignore.is_file():
+    lines = gitignore.read_text(encoding="utf-8").splitlines()
+    if entry not in lines:
+        content = gitignore.read_text(encoding="utf-8")
+        if content and not content.endswith("\n"):
+            content += "\n"
+        content += f"{comment}\n{entry}\n"
+        gitignore.write_text(content, encoding="utf-8")
+elif (ROOT / ".git").is_dir():
+    gitignore.write_text(f"{comment}\n{entry}\n", encoding="utf-8")
+PY
+
+NEED_INDEX=true
+if [ "$FORCE" = false ] && [ -f ".cocoindex_code/cocoindex.db" ]; then
+	NEED_INDEX=false
+	log "✓ Existing cocoindex.db (use --force to rebuild)"
+fi
+
+if [ "$NEED_INDEX" = true ] || [ "$FORCE" = true ]; then
+	log "Building semantic code index (ccc index)..."
+	ccc index
+fi
+
+if ccc doctor 2>/dev/null; then
+	log "✓ ccc doctor"
+else
+	log "! ccc doctor reported issues (see output above)"
+fi
+
+if ccc status 2>/dev/null | head -5; then
+	log "✓ ccc status"
+else
+	log "! ccc status unavailable"
+fi
+
+log "CocoIndex output: .cocoindex_code/"

package/.pi/scripts/harness-verify.mjs

@@ -202,6 +202,16 @@ async function main() {
 	if (!(await fileExists(runCtxLib))) fail("missing lib/harness-run-context.ts");
 	ok("lib/harness-run-context.ts");
 
+	const pkgJson = JSON.parse(
+		await readFile(join(ROOT, "package.json"), "utf-8"),
+	);
+	if (!pkgJson.files?.includes("vendor/pi-subagents")) {
+		fail(
+			'package.json "files" must include vendor/pi-subagents (npm publish ships subagents vendor)',
+		);
+	}
+	ok('package.json files includes vendor/pi-subagents');
+
 	const subagentsVendor = join(
 		ROOT,
 		"vendor",

package/.pi/skills/ast-grep/SKILL.md

@@ -23,7 +23,7 @@ Verifies with `sg --version`.
 | Task | Tool | Why |
 |------|------|-----|
 | Find code by structure/pattern | **ast-grep** (`sg`) | AST-aware — knows what is a function call vs a string |
-| Find code by concept/meaning | graphify / ck | Semantic search, knowledge graph |
+| Find code by concept/meaning | graphify / `ccc search` | Architecture (graphify) vs implementation chunks (`ccc`) |
 | Find exact literal string | `grep` | Only tool for non-code files or exact byte match |
 | Explore architecture | graphify | Call graph, community detection |
 
@@ -319,7 +319,7 @@ Need to find code
   ├─ Structural pattern (function calls, imports, classes)? → sg -p 'pattern'
   ├─ Rewrite/codemod needed? → sg -p 'old' --rewrite 'new'
   ├─ Project-wide lint rule? → sg scan (with sgconfig.yml)
-  ├─ Conceptual/semantic search? → graphify query or ck --hybrid
+  ├─ Conceptual/semantic search? → graphify query (architecture) or ccc search (implementation)
   ├─ Explore architecture? → graphify
   └─ Exact literal string in non-code? → grep
 ```

package/.pi/skills/ccc/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: ccc
+description: "This skill should be used when code search, file/directory summary lookup, or concept-guide lookup is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'describe this file', 'read the concept guide', 'update the index', 'ccc', 'cocoindex-code'."
+---
+
+# ccc - Semantic Code Search & Indexing
+
+`ccc` is the CLI for CocoIndex Code, providing semantic search over the current codebase and index management.
+
+## Ownership
+
+The agent owns the `ccc` lifecycle for the current project — initialization, indexing, and searching. Do not ask the user to perform these steps; handle them automatically.
+
+- **Initialization**: If `ccc search` or `ccc index` fails with an initialization error (e.g., "Not in an initialized project directory"), run `bash "$UP_PKG/.pi/scripts/harness-cocoindex-bootstrap.sh"` from the project root (or `ccc init` + `ccc index` when not in ultimate-pi harness), then retry the original command.
+- **Index freshness**: Keep the index up to date by running `ccc index` (or `ccc search --refresh`) when the index may be stale — e.g., at the start of a session, or after making significant code changes (new files, refactors, renamed modules). There is no need to re-index between consecutive searches if no code was changed in between.
+- **Installation**: If `ccc` itself is not found (command not found), refer to [management.md](references/management.md) for installation instructions and inform the user.
+
+### ultimate-pi harness
+
+- **Parent / main agents:** follow ownership above (`ccc index` when stale after large edits).
+- **`harness/planning/scout-semantic`:** use **`ccc search` only** — the harness runs incremental `ccc index` before subagent spawns. Never run `ccc index`, `ccc init`, or `ccc search --refresh` in scouts.
+- **Lane contract:** graphify = callers/communities/architecture; `ccc` = implementation-by-meaning (chunks). Do not use `ccc` for “who calls X” — use `graphify explain` / `graphify path`.
+
+## Searching the Codebase
+
+To perform a semantic search:
+
+```bash
+ccc search <query terms>
+```
+
+The query should describe the concept, functionality, or behavior to find, not exact code syntax. For example:
+
+```bash
+ccc search database connection pooling
+ccc search user authentication flow
+ccc search error handling retry logic
+```
+
+### Filtering Results
+
+- **By language** (`--lang`, repeatable): restrict results to specific languages.
+
+  ```bash
+  ccc search --lang python --lang markdown database schema
+  ```
+
+- **By path** (`--path`): restrict results to a glob pattern relative to project root. If omitted, defaults to the current working directory (only results under that subdirectory are returned).
+
+  ```bash
+  ccc search --path 'src/api/*' request validation
+  ```
+
+### Pagination
+
+Results default to the first page. To retrieve additional results:
+
+```bash
+ccc search --offset 5 --limit 5 database schema
+```
+
+If all returned results look relevant, use `--offset` to fetch the next page — there are likely more useful matches beyond the first page.
+
+### Working with Search Results
+
+Search results include file paths and line ranges. To explore a result in more detail:
+
+- Use the editor's built-in file reading capabilities (e.g., the `Read` tool) to load the matched file and read lines around the returned range for full context.
+- When working in a terminal without a file-reading tool, use `sed -n '<start>,<end>p' <file>` to extract a specific line range.
+
+### Following Hints in Search Output
+
+Search results are a mixed ranking of code chunks, per-file/dir summaries, and (when configured) curated concept guides — all scored against the same query. Two kinds of hit come with a follow-up command embedded in the output:
+
+- `[summary]` — a file or directory summary. Read with `ccc describe <path>`.
+- `[guide]` — a curated concept guide. Read with `ccc guide <slug>`.
+
+When a hit carries one of these tags, follow the hint: the synthesised text is usually a faster read than chasing through individual files. Conversely, do **not** run `ccc describe .` or `ccc guide` proactively as a triage step — let search rank what's relevant and act on what it returns.
+
+## Describing Files and Directories
+
+Per-file and per-directory summaries (when configured for the project) condense each file's public API, contracts, and role into a short markdown block. They are typically faster to consult than reading the source.
+
+```bash
+ccc describe src/auth/session.py        # one file
+ccc describe src/auth/                  # directory: summary + children tree
+ccc describe .                          # project root overview
+```
+
+Use `describe` when you already know the path you want; let `ccc search` find paths for you when you don't.
+
+## Concept Guides
+
+Some projects configure cross-cutting concept guides in `.cocoindex_code/guides.yml` — synthesised markdown documents for architectural topics that span many files (e.g. memoization, plugin-SDK boundary, channel routing). Each guide names canonical files, end-to-end flow, and contracts/invariants.
+
+```bash
+ccc guide                               # list available guides + descriptions
+ccc guide <slug>                        # print one guide
+```
+
+Discovery is search-driven: a relevant guide will surface in `ccc search` results tagged `[guide]` with a `ccc guide <slug>` hint. Run `ccc guide` (no args) only when first orienting in an unfamiliar codebase or when the user explicitly asks for the guide list — not as a routine first step.
+
+### Authoring `guides.yml` Interactively
+
+When the user wants to add or improve concept guides, collaborate on the slug list rather than dumping a finished YAML. Good guide candidates are **named subsystems the codebase obviously has** — cross-cutting lifecycles, registration/dispatch protocols, end-to-end data paths. Single-file or symbol-specific topics do not warrant a guide; per-file summaries already cover those.
+
+Recommended flow:
+
+1. **Survey the codebase.** Use `ccc describe .` and a few likely subdirectory summaries to enumerate the project's subsystems and inter-edge boundaries.
+2. **Propose candidates.** Suggest 5–10 slugs with one-line descriptions, framed to name the canonical starting file or directory for each topic. Show them to the user as a list.
+3. **Iterate.** Ask which to keep, drop, rename, or merge. Surface non-obvious dependencies (`deps:`) so a higher-level guide can cite a lower-level one rather than restate it. Cycles are rejected at load time.
+4. **Write the YAML.** Add the agreed entries to `.cocoindex_code/guides.yml` (creating the file if absent). Confirm `defaults.enabled: true` and that the project's summary feature is enabled — guides require summaries.
+5. **Generate.** Run `ccc index` to drive the per-guide agent loop and produce `<slug>.md` files under `.cocoindex_code/guides/`. Re-run after editing descriptions to refresh.
+
+Schema:
+
+```yaml
+defaults:
+  enabled: true                     # disables all guides when false
+  model: openai/gpt-5.4-nano        # falls back to summary.model when omitted
+  session_budget: 200
+  max_logical_depth: 3
+  max_turns_per_session: 18
+
+guides:
+  - slug: memoization                          # [a-z0-9][a-z0-9-]*
+    description: |
+      What this guide covers, framed for the reader.
+      Name the canonical starting files (e.g. "start with src/cache.py").
+    deps: [other-slug]                         # optional; must not cycle
+    max_turns_per_session: 28                  # optional per-entry overrides
+```
+
+A multi-line description is fine and often clearer than one terse sentence — the description seeds the guide-generation agent's question, so concrete file/directory anchors pay off.
+
+## Settings
+
+To view or edit embedding model configuration, include/exclude patterns, or language overrides, see [settings.md](references/settings.md).
+
+## Management & Troubleshooting
+
+For installation, initialization, daemon management, troubleshooting, and cleanup commands, see [management.md](references/management.md).

package/.pi/skills/ccc/references/management.md

@@ -0,0 +1,110 @@
+# ccc Management
+
+## Installation
+
+Install CocoIndex Code via pipx. Two install styles:
+
+```bash
+pipx install 'cocoindex-code[full]'      # batteries included (local embeddings via sentence-transformers)
+pipx install cocoindex-code              # slim (LiteLLM-only; requires a cloud embedding provider + API key)
+```
+
+The `[full]` extra pulls in `sentence-transformers` so the first-run default (local embeddings, no API key) works out of the box. The slim install is for environments where you don't want the torch/transformers deps and plan to use a LiteLLM-supported cloud provider instead.
+
+To upgrade to the latest version:
+
+```bash
+pipx upgrade cocoindex-code
+```
+
+After installation, the `ccc` command is available globally.
+
+## Project Initialization
+
+Run from the root directory of the project to index:
+
+```bash
+ccc init
+```
+
+**First run (global settings don't exist yet)** — `ccc init` prompts interactively for the embedding provider (sentence-transformers / litellm) and model, then runs a one-off test embed via the daemon to confirm the model works. Accept the defaults for the sentence-transformers path, or pick litellm and enter a model identifier.
+
+**Subsequent runs** (global settings already exist) — prompts are skipped; only project settings and `.gitignore` are set up.
+
+To skip the interactive prompts on the first run (e.g. in a script or container), pass `--litellm-model MODEL`:
+
+```bash
+ccc init --litellm-model openai/text-embedding-3-small
+```
+
+This is also the only way to pick a LiteLLM model when stdin isn't a TTY and you've done a slim install.
+
+`ccc init` creates:
+- `~/.cocoindex_code/global_settings.yml` (user-level, embedding config + env vars).
+- `.cocoindex_code/settings.yml` (project-level, include/exclude patterns).
+
+If `.git` exists in the directory, `.cocoindex_code/` is automatically added to `.gitignore`.
+
+Use `-f` to skip the confirmation prompt if `ccc init` detects a potential parent project root.
+
+After initialization, edit the settings files if needed (see [settings.md](settings.md) for format details), then run `ccc index` to build the initial index. If the model test printed `[FAIL]` during `init`, edit `global_settings.yml` (and optionally add API keys under the commented `envs:` block) and verify with `ccc doctor` before indexing.
+
+## Troubleshooting
+
+### Diagnostics
+
+Run `ccc doctor` to check system health end-to-end:
+
+```bash
+ccc doctor
+```
+
+This checks global settings, daemon status, embedding model (runs a test embedding), and — if run from within a project — file matching (walks files using the same logic as the indexer) and index status. Results stream incrementally. Always points to `daemon.log` at the end for further investigation.
+
+### Checking Project Status
+
+To view the current project's index status:
+
+```bash
+ccc status
+```
+
+This shows whether indexing is ongoing and index statistics.
+
+### Daemon Management
+
+The daemon starts automatically on first use. To check its status:
+
+```bash
+ccc daemon status
+```
+
+This shows whether the daemon is running, its version, uptime, and loaded projects.
+
+To restart the daemon (useful if it gets into a bad state):
+
+```bash
+ccc daemon restart
+```
+
+To stop the daemon:
+
+```bash
+ccc daemon stop
+```
+
+## Cleanup
+
+To reset a project's index (removes databases, keeps settings):
+
+```bash
+ccc reset
+```
+
+To fully remove all CocoIndex Code data for a project (including settings):
+
+```bash
+ccc reset --all
+```
+
+Both commands prompt for confirmation. Use `-f` to skip.

package/CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to this project are documented in this file.
 
 ## [Unreleased]
 
+## [v0.13.0] — 2026-05-18
+
+### ✨ Features
+
+- **CocoIndex Code:** replace `@beaconbay/ck-search` with offline `ccc` semantic search; `harness-cocoindex-bootstrap.sh`, pre-scout incremental index in `harness-subagents-bridge`, vendored `/skill:ccc`, `cocoindex-search` skill, and `ck-search` deprecation stub.
+
+### 🔧 Chores
+
+- Harness excludes for `graphify-out/`, `vendor/`, `raw/`, etc. in `.cocoindex_code/settings.yml`; `.gitignore` tracks `.cocoindex_code/`.
+
 ## [v0.12.0] — 2026-05-18
 
 ### ✨ Features

package/THIRD_PARTY_NOTICES.md

@@ -22,3 +22,10 @@
 - **License:** MIT ([vendor/pi-subagents/LICENSE](vendor/pi-subagents/LICENSE))  
 - **Pinned revision:** See [vendor/pi-subagents/UPSTREAM_PIN.md](vendor/pi-subagents/UPSTREAM_PIN.md)  
 - ultimate-pi loads it from [`vendor/pi-subagents`](vendor/pi-subagents) via [`.pi/extensions/harness-subagents.ts`](.pi/extensions/harness-subagents.ts) with harness discovery, spawn gates, and subprocess env. Maintainer refresh: `npm run vendor:sync-subagents`.
+
+## CocoIndex Code (CLI + skill)
+
+- **Project:** https://github.com/cocoindex-io/cocoindex-code  
+- **License:** Apache-2.0  
+- **Install:** `uv tool install 'cocoindex-code[full]'` (see `/harness-setup` §2.4)  
+- ultimate-pi vendors the upstream agent skill at [`.pi/skills/ccc/`](.pi/skills/ccc/) and bootstraps indexes via [`.pi/scripts/harness-cocoindex-bootstrap.sh`](.pi/scripts/harness-cocoindex-bootstrap.sh). Replaces deprecated `@beaconbay/ck-search`.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "ultimate-pi",
-	"version": "0.12.0",
+	"version": "0.13.0",
 	"description": "Ultimate AI coding harness for pi.dev — extensible skills, Obsidian wiki knowledge layer, compressed context, deterministic output",
 	"keywords": [
 		"pi-package",
@@ -67,13 +67,14 @@
 		"README.md",
 		"THIRD_PARTY_NOTICES.md",
 		"vendor/pi-model-router",
+		"vendor/pi-subagents",
 		"vendor/pi-vcc"
 	],
 	"peerDependencies": {
 		"@earendil-works/pi-coding-agent": "*"
 	},
 	"scripts": {
-		"check:ts": "tsc --noEmit --target ES2023 --lib ES2023 --moduleResolution nodenext --module nodenext --skipLibCheck .pi/extensions/custom-system-prompt.ts .pi/lib/harness-run-context.ts .pi/lib/harness-ui-state.ts .pi/extensions/harness-run-context.ts .pi/extensions/lib/harness-vcc-settings.ts .pi/extensions/dotenv-loader.ts .pi/extensions/lib/posthog-node.d.ts .pi/extensions/lib/harness-posthog.ts .pi/extensions/lib/harness-paths.ts .pi/extensions/pi-model-router-harness.ts .pi/extensions/provider-payload-sanitize.ts .pi/extensions/harness-telemetry.ts .pi/extensions/harness-ask-user.ts .pi/extensions/harness-plan-approval.ts .pi/extensions/lib/ask-user/schema.ts .pi/extensions/lib/ask-user/types.ts .pi/extensions/lib/ask-user/validate.ts .pi/extensions/lib/ask-user/dialog.ts .pi/extensions/lib/ask-user/fallback.ts .pi/extensions/lib/ask-user/render.ts .pi/extensions/lib/plan-approval/types.ts .pi/extensions/lib/plan-approval/schema.ts .pi/extensions/lib/plan-approval/validate.ts .pi/extensions/lib/plan-approval/format-plan.ts .pi/extensions/lib/plan-approval/dialog.ts .pi/extensions/lib/plan-approval/fallback.ts .pi/extensions/lib/plan-approval/render.ts .pi/extensions/lib/plan-approval/create-plan.ts .pi/extensions/harness-subagents.ts .pi/extensions/lib/harness-subagents-bridge.ts .pi/extensions/lib/harness-subagent-auth.ts .pi/extensions/lib/harness-subagent-policy.ts .pi/extensions/lib/harness-subagent-precheck.ts .pi/extensions/lib/harness-spawn-budget.ts .pi/extensions/lib/spawn-policy.ts vendor/pi-subagents/src/agents.ts vendor/pi-subagents/src/subagents.ts .pi/extensions/trace-recorder.ts .pi/extensions/observation-bus.ts .pi/extensions/drift-monitor.ts .pi/extensions/policy-gate.ts .pi/extensions/budget-guard.ts .pi/extensions/debate-orchestrator.ts .pi/extensions/harness-live-widget.ts .pi/extensions/sentrux-rules-sync.ts .pi/extensions/custom-header.ts .pi/extensions/harness-web-tools.ts .pi/extensions/harness-web-guard.ts .pi/extensions/lib/harness-web/run-cli.ts",
+		"check:ts": "tsc --noEmit --target ES2023 --lib ES2023 --moduleResolution nodenext --module nodenext --skipLibCheck .pi/extensions/custom-system-prompt.ts .pi/lib/harness-run-context.ts .pi/lib/harness-ui-state.ts .pi/extensions/harness-run-context.ts .pi/extensions/lib/harness-vcc-settings.ts .pi/extensions/dotenv-loader.ts .pi/extensions/lib/posthog-node.d.ts .pi/extensions/lib/harness-posthog.ts .pi/extensions/lib/harness-paths.ts .pi/extensions/pi-model-router-harness.ts .pi/extensions/provider-payload-sanitize.ts .pi/extensions/harness-telemetry.ts .pi/extensions/harness-ask-user.ts .pi/extensions/harness-plan-approval.ts .pi/extensions/lib/ask-user/schema.ts .pi/extensions/lib/ask-user/types.ts .pi/extensions/lib/ask-user/validate.ts .pi/extensions/lib/ask-user/dialog.ts .pi/extensions/lib/ask-user/fallback.ts .pi/extensions/lib/ask-user/render.ts .pi/extensions/lib/plan-approval/types.ts .pi/extensions/lib/plan-approval/schema.ts .pi/extensions/lib/plan-approval/validate.ts .pi/extensions/lib/plan-approval/format-plan.ts .pi/extensions/lib/plan-approval/dialog.ts .pi/extensions/lib/plan-approval/fallback.ts .pi/extensions/lib/plan-approval/render.ts .pi/extensions/lib/plan-approval/create-plan.ts .pi/extensions/harness-subagents.ts .pi/extensions/lib/harness-subagents-bridge.ts .pi/extensions/lib/harness-cocoindex-refresh.ts .pi/extensions/lib/harness-subagent-auth.ts .pi/extensions/lib/harness-subagent-policy.ts .pi/extensions/lib/harness-subagent-precheck.ts .pi/extensions/lib/harness-spawn-budget.ts .pi/extensions/lib/spawn-policy.ts vendor/pi-subagents/src/agents.ts vendor/pi-subagents/src/subagents.ts .pi/extensions/trace-recorder.ts .pi/extensions/observation-bus.ts .pi/extensions/drift-monitor.ts .pi/extensions/policy-gate.ts .pi/extensions/budget-guard.ts .pi/extensions/debate-orchestrator.ts .pi/extensions/harness-live-widget.ts .pi/extensions/sentrux-rules-sync.ts .pi/extensions/custom-header.ts .pi/extensions/harness-web-tools.ts .pi/extensions/harness-web-guard.ts .pi/extensions/lib/harness-web/run-cli.ts",
 		"vendor:sync-router": "bash .pi/scripts/vendor-sync-pi-model-router.sh",
 		"vendor:sync-vcc": "bash .pi/scripts/vendor-sync-pi-vcc.sh",
 		"vendor:sync-subagents": "bash .pi/scripts/vendor-sync-pi-subagents.sh",

package/vendor/pi-subagents/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 narumiruna
+
+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/vendor/pi-subagents/UPSTREAM_PIN.md

@@ -0,0 +1,11 @@
+# Vendored `@narumitw/pi-subagents`
+
+- **Repository:** https://github.com/narumiruna/pi-extensions
+- **Directory:** `extensions/pi-subagents`
+- **Version:** 0.1.26
+- **Commit:** main @ 2026-05-18 (subagents.ts + agents.ts base)
+- **License:** MIT ([LICENSE](LICENSE))
+
+ultimate-pi extends upstream with recursive `$UP_PKG/.pi/agents/**` discovery, harness spawn gates, and subprocess env (`UP_PKG`, `PI_HARNESS_SUBPROCESS`).
+
+Refresh: `npm run vendor:sync-subagents`