ultimate-pi 0.18.0 → 0.18.1

package/.pi/scripts/harness-sentrux-cli.mjs

@@ -0,0 +1,142 @@
+#!/usr/bin/env node
+/**
+ * Run the Sentrux CLI against the harness project root.
+ *
+ * Sentrux resolves `.sentrux/rules.toml` relative to the PATH argument, so
+ * harness commands must not rely on the current working directory. This helper
+ * finds the nearest ancestor with harness Sentrux config and passes that root
+ * explicitly to `sentrux check` / `sentrux gate`.
+ *
+ * Usage:
+ *   node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check [--root <PROJECT_ROOT>]
+ *   node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate [--save] [--root <PROJECT_ROOT>]
+ *   node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" --print-root
+ */
+
+import { access } from "node:fs/promises";
+import { constants } from "node:fs";
+import { dirname, isAbsolute, join, resolve } from "node:path";
+import { spawn } from "node:child_process";
+
+const ROOT_MARKERS = [
+	join(".sentrux", "rules.toml"),
+	join(".pi", "harness", "sentrux", "architecture.manifest.json"),
+];
+
+async function fileExists(path) {
+	try {
+		await access(path, constants.R_OK);
+		return true;
+	} catch {
+		return false;
+	}
+}
+
+async function hasRootMarker(dir) {
+	for (const marker of ROOT_MARKERS) {
+		if (await fileExists(join(dir, marker))) return true;
+	}
+	return false;
+}
+
+async function findProjectRoot(startDir) {
+	let dir = resolve(startDir || process.cwd());
+	while (true) {
+		if (await hasRootMarker(dir)) return dir;
+		const parent = dirname(dir);
+		if (parent === dir) return null;
+		dir = parent;
+	}
+}
+
+function takeRootArg(args) {
+	const next = [];
+	let explicitRoot = process.env.HARNESS_PROJECT_ROOT || "";
+	for (let i = 0; i < args.length; i++) {
+		const arg = args[i];
+		if (arg === "--root") {
+			explicitRoot = args[i + 1] || "";
+			i++;
+			continue;
+		}
+		if (arg.startsWith("--root=")) {
+			explicitRoot = arg.slice("--root=".length);
+			continue;
+		}
+		next.push(arg);
+	}
+	return { args: next, explicitRoot };
+}
+
+async function resolveProjectRoot(explicitRoot) {
+	if (explicitRoot) {
+		const root = isAbsolute(explicitRoot)
+			? resolve(explicitRoot)
+			: resolve(process.cwd(), explicitRoot);
+		if (!(await hasRootMarker(root))) {
+			console.error(
+				`harness-sentrux-cli: ${root} has no .sentrux/rules.toml or .pi/harness/sentrux/architecture.manifest.json`,
+			);
+			process.exit(1);
+		}
+		return root;
+	}
+
+	const root = await findProjectRoot(process.cwd());
+	if (!root) {
+		console.error(
+			"harness-sentrux-cli: could not find a harness project root above the current directory",
+		);
+		process.exit(1);
+	}
+	return root;
+}
+
+function normalizeSentruxArgs(args, projectRoot) {
+	const command = args[0];
+	if (!command || command === "--help" || command === "-h") {
+		console.log(`Usage: node harness-sentrux-cli.mjs <check|gate> [sentrux flags] [--root PROJECT_ROOT]
+
+Runs Sentrux with PROJECT_ROOT passed explicitly so .sentrux/rules.toml is found even when invoked from .pi/harness/runs/*.`);
+		process.exit(0);
+	}
+	if (command !== "check" && command !== "gate") {
+		console.error(
+			`harness-sentrux-cli: unsupported command "${command}" (expected check or gate)`,
+		);
+		process.exit(2);
+	}
+	return [command, ...args.slice(1), projectRoot];
+}
+
+async function main() {
+	const parsed = takeRootArg(process.argv.slice(2));
+	const printRoot = parsed.args.includes("--print-root");
+	const sentruxArgs = parsed.args.filter((arg) => arg !== "--print-root");
+	const projectRoot = await resolveProjectRoot(parsed.explicitRoot);
+
+	if (printRoot) {
+		console.log(projectRoot);
+		return;
+	}
+
+	const child = spawn("sentrux", normalizeSentruxArgs(sentruxArgs, projectRoot), {
+		cwd: projectRoot,
+		stdio: "inherit",
+		env: process.env,
+	});
+	child.on("error", (err) => {
+		if (err?.code === "ENOENT") {
+			console.error("harness-sentrux-cli: sentrux not installed");
+			process.exit(127);
+		}
+		console.error(`harness-sentrux-cli: ${err.message}`);
+		process.exit(1);
+	});
+	child.on("close", (code) => process.exit(code ?? 1));
+}
+
+main().catch((err) => {
+	console.error(err);
+	process.exit(1);
+});

package/CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to this project are documented in this file.
 
 ## [Unreleased]
 
+### ✨ Features
+
+- **Graphify KB updater:** Productize conservative daily discovery/promotion with explicit repo/release taxonomy, allowlist source-class gates, operator review queue reporting, scheduler smoke validation, and safe Graphify refresh controls.
+
+## [v0.18.1] — 2026-05-24
+
+### 🔧 Chores
+
+- Ignore local project runtime config.
+- Fix harness review revise flow and widget UX.
+- Add harness project toggle controls.
+
 ## [v0.18.0] — 2026-05-23
 
 ### ✨ Features

package/README.md

@@ -2,102 +2,138 @@
 
 > The **ultimate AI coding harness** on top of [**pi.dev**](https://pi.dev).
 
-`ultimate-pi` is a pi package that adds a governed coding workflow: plan first, then implement, then independent review—so agents cannot silently skip planning or merge unsafe changes.
+`ultimate-pi` adds a governed coding workflow to Pi: bootstrap the repo, plan with evidence, execute only against an approved PlanPacket, then run an independent review gate before merge.
 
 ## Quick start
 
-**Requirements:** Node 18+, npm 9+, git.
+**Requirements:** Node 18+, npm 9+, git, and Pi.
 
-1. **Install** (from your project directory):
+1. Install the package in your project:
 
 ```bash
 pi install npm:ultimate-pi
 /reload
 ```
 
-2. **Bootstrap** (once per project):
+2. Bootstrap the harness once per project:
 
 ```text
 /harness-setup
 ```
 
-3. **Run a task** (full pipeline in one command):
+3. Run the strict end-to-end pipeline:
 
 ```text
 /harness-auto "implement feature X safely"
 ```
 
-That runs: plan → execute → evaluate → adversary → policy decision. It does **not** auto-merge.
+`/harness-auto` runs plan → execute → review → optional steer loop. It may prepare commit/PR work when gates pass, but it never auto-merges.
 
-If something blocks, inspect status (no run id needed):
+## Core workflow
+
+### Recommended: one command
 
 ```text
-/harness-run-status
-/harness-policy-status
-/harness-trace-last
+/harness-auto "your task" [--quick] [--risk low|med|high]
 ```
 
-## Commands
-
-| Command | What it does |
-|---------|----------------|
-| `/harness-setup` | One-time project bootstrap (tools, harness dirs, extensions) |
-| `/harness-auto "<task>"` | End-to-end pipeline (recommended) |
-| `/harness-plan "<task>"` | Create or **revise** the active plan in context (no plan path to copy) |
-| `/harness-run` | Execute the active plan from context (**no `--plan`** on happy path) |
-| `/harness-eval` | Eval for active run (optional `--run`; spawns isolated `harness/evaluator`) |
-| `/harness-review` | Independent review (optional `--run`) |
-| `/harness-critic` | Adversarial review (optional `--run`) |
-| `/harness-trace` | Trace summary (optional `--run`) |
-| `/harness-run-status` | Where you are + what to run next (no run id shown) |
-| `/harness-new-run` | Abandon current run and start fresh |
-| `/harness-use-run <id>` | Advanced recovery only |
-| `/harness-trace-last` | Last phase / handoff (no run id) |
-| `/harness-policy-status` | Current policy / block reasons |
-| `/harness-abort [reason]` | Stop and replan path |
-
-## Manual workflow
-
-Use this when you want each step separate:
+Use this for most feature, fix, and refactor work. The parent orchestrator handles the phase handoffs and keeps active run context in `.pi/harness/active-run.json` plus run artifacts under `.pi/harness/runs/`.
+
+### Manual: phase by phase
 
 ```text
-/harness-plan "your task"
+/harness-plan "your task" [--risk low|med|high] [--quick]
 /harness-run
-/harness-eval
-/harness-review
-/harness-critic
+/harness-review [--quick]
 ```
 
-The harness **remembers the active run and plan** per project — you do not pass `plan-packet.json` paths or run ids between steps. The live widget shows phase/policy; after each step the agent (and UI notify) suggests the next command.
+Manual mode is useful when you want to inspect or approve each handoff. On the happy path you do **not** pass `--plan` or a run id; the harness restores the active PlanPacket and run context.
 
-Recovery: `--run` and `--plan` remain for scripts; `/harness-use-run` and `/harness-run-status` for operators.
+### Repair loop
 
-## Defaults you should know
+If `/harness-review` returns `implementation_gap`, run:
 
-- **System prompt** — [`.pi/extensions/00-ultimate-pi-system-prompt.ts`](.pi/extensions/00-ultimate-pi-system-prompt.ts) sets the base prompt from packaged [`.pi/SYSTEM.md`](.pi/SYSTEM.md), or from your workspace override **`.pi/system.md`** (lowercase) if you create one. Nothing is copied into your project by default. After upgrading the package or editing either file, run **`/reload`**.
-- **Model routing (vendored + gated)** — [`pi-model-router`](https://github.com/yeliu84/pi-model-router) ships inside this package (`vendor/pi-model-router/`). [`.pi/extensions/pi-model-router-harness.ts`](.pi/extensions/pi-model-router-harness.ts) activates it **only after** `.pi/model-router.json` exists (generation: `/harness-setup` Step 3.5), so **`router/auto` does not appear** beforehand. See [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md). [`.pi/scripts/harness-sync-model-router.mjs`](.pi/scripts/harness-sync-model-router.mjs) may set **`defaultProvider`/`defaultModel`** to **`router`/`auto`** when the project sets no default — run **`/reload`** afterward. Do **not** add `npm:@yeliu84/pi-model-router` to `.pi/settings.json`; it duplicates the fork. Maintainer refresh: **`npm run vendor:sync-router`**.
-- **Active run + plan context** — PlanPacket lives at a fixed path per run; the extension injects it for `/harness-plan` (revise) and `/harness-run` (execute). Session state plus `.pi/harness/active-run.json`; no run ids or plan paths to copy.
-- **Review isolation** — `/harness-eval`, `/harness-review`, and `/harness-critic` spawn isolated subagents (`inherit_context: false`); stay in the same session (see ADR 0032).
-- **Concurrent plans** — a second `/harness-plan` while a run is active is blocked until `/harness-abort` or `/harness-new-run` (except drift replan / amend after `needs_clarification`).
-- **Plan before mutate** — write/edit/shell that changes the repo is blocked until execute phase.
-- **No auto-merge** — you decide when to open or merge a PR.
-- **Structured runs** — each run writes artifacts under `.pi/harness/runs/` for replay and audit.
+```text
+/harness-steer
+/harness-review
+```
 
-Optional: copy [`.env.example`](.env.example) to `.env` if you use PostHog or other integrations wired by `/harness-setup`.
+`/harness-steer` uses `artifacts/repair-brief.yaml` and respawns the executor in repair mode without widening the approved plan scope.
+
+## Command reference
+
+| Command | Purpose |
+|---|---|
+| `/harness-setup [--skip-graphify] [--skip-tools] [--non-interactive] [--force]` | Idempotent project bootstrap: Graphify, harness-web/Scrapling, CLI tools, settings, contracts, Sentrux, model router, and verification. |
+| `/harness-auto "<task>" [--quick] [--risk low\|med\|high]` | Strict full pipeline: plan, execute, review, steer when appropriate. |
+| `/harness-plan "<task>" [--risk low\|med\|high] [--quick]` | PM-grade planning: reconnaissance, decomposition, hypothesis, external research, ExecutionPlan, DAG validation, Review Gate debate, `approve_plan`, `create_plan`. |
+| `/harness-run` | Executes the approved active PlanPacket by spawning `harness/running/executor`; no inline implementation. |
+| `/harness-review [--run <id>] [--quick] [--readonly] [--trace <ref>]` | Post-run verification gate: deterministic checks, benchmark evaluator, policy verdict, adversary, optional tie-breaker. |
+| `/harness-steer [--attempt N]` | Post-review repair pass for `implementation_gap`; executor reads `repair-brief.yaml`, then you re-run `/harness-review`. |
+| `/harness-abort [reason]` | Safely aborts the active run, clears plan readiness, and re-locks mutation until a fresh plan is approved. |
+| `/harness-trace [--run <id>] [--phase plan\|execute\|evaluate\|adversary\|merge]` | Summarizes run traces and artifact handoffs for replay/forensics. |
+| `/harness-incident --trigger <reason> [--run <id>] [--severity low\|med\|high\|critical]` | Records incident, rollback, and override trail for harness failures. |
+| `/harness-sentrux-steward [--run <id>]` | Ad-hoc architectural intent review for Sentrux manifest/rule alignment. |
+| `/harness-router-tune --evidence <evidence.json> --candidate <candidate-router.json> [--proposal <out.json>]` | Proposes model-router updates from evidence; applies only after explicit approval. |
+| `/graphify [directory]` | Bootstraps or updates the Graphify knowledge graph. |
+| `/wiki-autoresearch [topic]` | Runs autonomous web research and builds a Graphify-backed research wiki. |
+| `/wiki-save` | Saves the current conversation or insight as a structured wiki note. |
+| `/release [patch\|minor\|major] [--dry-run]` | Maintainer release helper. |
+
+Deprecated compatibility aliases:
+
+| Alias | Use instead |
+|---|---|
+| `/harness-eval` | `/harness-review` |
+| `/harness-critic` | `/harness-review` |
+
+## Harness phases and agents
+
+- **Planning** uses agents under `.pi/agents/harness/planning/` plus parent-led Graphify → `sg` → `ccc` reconnaissance. Legacy tool-tied `planning/scout-*` agents have been removed; planning context is captured in `artifacts/planning-context.yaml`.
+- **Running** uses `.pi/agents/harness/running/executor.md` via agent id `harness/running/executor`.
+- **Reviewing** uses `.pi/agents/harness/reviewing/` via `harness/reviewing/evaluator`, `harness/reviewing/adversary`, and `harness/reviewing/tie-breaker`.
+- **Support agents** such as `harness/incident-recorder`, `harness/sentrux-steward`, and `harness/trace-librarian` remain under `.pi/agents/harness/`.
+
+Subagents run isolated from the parent session. They persist canonical YAML through `submit_*` tools; the parent gates with `harness_artifact_ready` and writes only orchestrator-owned merge artifacts.
+
+## Artifacts and layout
+
+| Path | Description |
+|---|---|
+| `.pi/harness/active-run.json` | Active run pointer for happy-path commands. |
+| `.pi/harness/runs/<run_id>/plan-packet.yaml` | Approved execution baseline. |
+| `.pi/harness/runs/<run_id>/research-brief.yaml` | Planning evidence and research merge. |
+| `.pi/harness/runs/<run_id>/artifacts/` | Planning context, decomposition, research, benchmark, verdict, adversary, repair, and Sentrux artifacts. |
+| `.pi/harness/runs/<run_id>/handoff/executor-summary.yaml` | Executor handoff written by `submit_executor_handoff`. |
+| `.pi/harness/incidents/` | Incident records and rollback/override trail. |
+| `.pi/harness/docs/adrs/` | Harness architectural decisions. |
+| `.pi/harness/specs/` | Artifact contracts and schemas seeded into projects. |
+
+## Safety defaults
+
+- **Graph before grep:** planning consults `graphify-out/GRAPH_REPORT.md` and Graphify queries before raw file reads.
+- **Plan before mutate:** mutating tools are blocked until `/harness-plan` approves and creates a plan.
+- **No inline execution:** `/harness-run` delegates to `harness/running/executor` only.
+- **No inline review:** `/harness-review` delegates verdicts to isolated reviewing agents.
+- **No auto-merge:** final merge remains a human/operator decision.
+- **Sentrux is observational:** structural baselines and gates inform review; executor does not optimize metrics as a goal.
+- **Router is gated:** `pi-model-router` activates after `/harness-setup` creates `.pi/model-router.json`; run `/reload` after setup or router changes.
 
 ## Troubleshooting
 
 | Problem | Try |
-|---------|-----|
-| Setup fails | `node --version` (need 18+), rerun `/harness-setup` |
-| "No active run" on eval | Finish plan+run first, or `/harness-run-status` |
-| Forgot where you left off | `/harness-run-status` |
-| Second plan rejected | `/harness-abort` or `/harness-new-run` |
-| Blocked in evaluate/review | Spawn review via Agent (`harness/evaluator` / `harness/adversary`); do not run review tools inline in execute phase |
-| High plan drift | `harness-drift-replan` or abort then replan (ADR 0007) |
-| Budget / scope stop | `/harness-budget-status`, narrow the task or split the plan |
-| Test integrity warning | `/harness-test-integrity-last`, fix or justify test changes |
+|---|---|
+| Setup fails | Confirm `node --version` is 18+, `npm --version` is 9+, then rerun `/harness-setup`. |
+| No approved plan | Run `/harness-plan "<task>"`, then `/harness-run`. |
+| Need to inspect handoff | Run `/harness-trace` or inspect `.pi/harness/runs/<run_id>/`. |
+| Need to restart safely | Run `/harness-abort [reason]`, then create a fresh plan. |
+| Review says `implementation_gap` | Run `/harness-steer`, then `/harness-review`. |
+| Review says `plan_gap` | Revise with `/harness-plan "<updated task>"`. |
+| Router profile missing | Complete `/harness-setup`, run `/reload`, then check `.pi/model-router.json`. |
+| Sentrux missing | Install/configure Sentrux or keep it skipped; harness verification still reports the status. |
+
+Optional integrations can be configured by copying `.env.example` to `.env`; `/harness-setup` appends missing keys without overwriting existing values.
 
 ## Contributing
 
-Local development, harness internals, and quality gates: [CONTRIBUTING.md](./CONTRIBUTING.md) and [`.pi/harness/README.md`](.pi/harness/README.md).
+Local development, harness internals, and quality gates: [CONTRIBUTING.md](./CONTRIBUTING.md), [`.pi/scripts/README.md`](.pi/scripts/README.md), and [`.pi/harness/docs/adrs/`](.pi/harness/docs/adrs/).

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "ultimate-pi",
-	"version": "0.18.0",
+	"version": "0.18.1",
 	"description": "Ultimate AI coding harness for pi.dev — extensible skills, Obsidian wiki knowledge layer, compressed context, deterministic output",
 	"keywords": [
 		"pi-package",
@@ -74,7 +74,7 @@
 		"@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-context-mode-policy.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/00-posthog-network-bootstrap.ts .pi/extensions/lib/posthog-client.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/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-debate-tools.ts .pi/extensions/lib/debate-bus-core.ts .pi/extensions/lib/debate-bus-state.ts .pi/extensions/lib/plan-debate-gate.ts .pi/extensions/lib/plan-debate-id.ts .pi/extensions/lib/plan-messenger.ts .pi/extensions/lib/plan-debate-envelope.ts .pi/extensions/lib/plan-review-integrator-rules.ts .pi/extensions/lib/plan-scope-guard.ts .pi/extensions/lib/plan-debate-write-guard.ts .pi/extensions/lib/plan-debate-lane.ts .pi/extensions/lib/plan-debate-round-status.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/00-harness-project-control.ts .pi/extensions/custom-system-prompt.ts .pi/lib/harness-run-context.ts .pi/lib/harness-context-mode-policy.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/00-posthog-network-bootstrap.ts .pi/extensions/lib/posthog-client.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/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/review-integrity.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-debate-tools.ts .pi/extensions/lib/debate-bus-core.ts .pi/extensions/lib/debate-bus-state.ts .pi/extensions/lib/plan-debate-gate.ts .pi/extensions/lib/plan-debate-id.ts .pi/extensions/lib/plan-messenger.ts .pi/extensions/lib/plan-debate-envelope.ts .pi/extensions/lib/plan-review-integrator-rules.ts .pi/extensions/lib/plan-scope-guard.ts .pi/extensions/lib/plan-debate-write-guard.ts .pi/extensions/lib/plan-debate-lane.ts .pi/extensions/lib/plan-debate-round-status.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",
@@ -84,7 +84,7 @@
 		"format": "biome format --write",
 		"format:check": "biome format",
 		"prepare": "lefthook install",
-		"test": "node --test test/harness-verify.test.mjs test/posthog-client.test.mjs test/harness-ask-user.test.mjs test/harness-subagents-loader.test.mjs test/harness-subagent-precheck.test.mjs test/sentrux-rules-sync.test.mjs test/harness-budget-guard.test.mjs && node .pi/harness/evals/smoke/smoke-harness-plan.mjs --fixture && npx -y tsx --test test/harness-vcc-settings.test.ts test/harness-run-context-postrun.test.mjs test/harness-tool-payload.test.mjs test/harness-live-widget-status.test.ts test/harness-plan-phase-policy.test.mjs test/harness-context-mode-policy.test.mjs test/harness-subprocess-bootstrap.test.mjs test/harness-subagent-policy.test.mjs test/harness-subagent-precheck-topology.test.mjs test/plan-approval-readiness.test.mjs test/harness-spawn-budget.test.mjs test/harness-spawn-parse.test.mjs test/harness-schema-validate.test.mjs test/harness-turn-routing.test.mjs test/harness-budget-enforce.test.mjs test/harness-submit-policy.test.mjs test/plan-approval-format.test.mjs test/plan-approval-dialog.test.mjs test/plan-approval-sync.test.mjs test/plan-create-plan.test.mjs test/plan-review-format.test.mjs test/debate-plan-phase.test.mjs test/plan-debate-eligibility.test.mjs test/plan-messenger-gate.test.mjs test/plan-debate-lane-apply.test.mjs",
+		"test": "node --test test/harness-verify.test.mjs test/posthog-client.test.mjs test/harness-ask-user.test.mjs test/harness-subagents-loader.test.mjs test/harness-subagent-precheck.test.mjs test/sentrux-rules-sync.test.mjs test/harness-budget-guard.test.mjs && node .pi/harness/evals/smoke/smoke-harness-plan.mjs --fixture && npx -y tsx --test test/harness-vcc-settings.test.ts test/harness-run-context-postrun.test.mjs test/harness-tool-payload.test.mjs test/harness-live-widget-status.test.ts test/harness-project-toggle-tui.test.ts test/harness-plan-phase-policy.test.mjs test/harness-context-mode-policy.test.mjs test/harness-subprocess-bootstrap.test.mjs test/harness-subagent-policy.test.mjs test/harness-subagent-precheck-topology.test.mjs test/plan-approval-readiness.test.mjs test/harness-spawn-budget.test.mjs test/harness-spawn-parse.test.mjs test/harness-schema-validate.test.mjs test/harness-turn-routing.test.mjs test/harness-budget-enforce.test.mjs test/harness-submit-policy.test.mjs test/plan-approval-format.test.mjs test/plan-approval-dialog.test.mjs test/plan-approval-sync.test.mjs test/plan-create-plan.test.mjs test/plan-review-format.test.mjs test/debate-plan-phase.test.mjs test/plan-debate-eligibility.test.mjs test/plan-messenger-gate.test.mjs test/plan-debate-lane-apply.test.mjs test/review-integrity-revise-handoff.test.mjs test/harness-plan-revise-reset.test.mjs",
 		"test:vcc": "npx -y tsx --test vendor/pi-vcc/tests/*.test.ts",
 		"harness:sentrux-bootstrap": "node .pi/scripts/harness-sentrux-bootstrap.mjs",
 		"harness:sentrux-sync": "node .pi/scripts/sentrux-rules-sync.mjs --force",

package/.pi/agents/harness/planning/scout-graphify.md

@@ -1,39 +0,0 @@
----
-description: "[DEPRECATED — ADR 0041] Legacy graphify-only scout. Prefer parent tools + planning-context.yaml."
-tools: read, bash, ls, submit_scout_findings
-disallowed_tools: write, edit, ask_user, approve_plan, create_plan, subagent, grep, find
-extensions: false
-thinking: low
-max_turns: 8
----
-
-> **Deprecated (ADR 0041):** The parent orchestrator should compile `artifacts/planning-context.yaml` using tools directly, or spawn `harness/planning/planning-context` once. This agent remains for backward compatibility only.
-
-You are the **Harness planning scout (graphify lane)**.
-
-## Mission
-
-Explore the codebase via graphify for the task in `HarnessSpawnContext`. You do **not** build the PlanPacket, approve plans, or mutate anything.
-
-Findings should feed **constraints, prior art, and tensions** for the decompose agent (existing patterns, god nodes, surprising connections).
-
-**Lane contract:** you own **relationships and architecture** (`graphify query`, `explain`, `path`). `scout-semantic` owns implementation-by-meaning via `ccc search` — do not duplicate semantic chunk search here.
-
-## Spawn context
-
-Read `HarnessSpawnContext` in the spawn prompt (`task_summary`, `mode`, `plan_packet_path`, `risk_level`, `quick`). For `mode: revise`, read the existing plan at `plan_packet_path` first and focus findings on what changed or is at risk.
-
-## Process
-
-1. Read `graphify-out/GRAPH_REPORT.md` when present; use `graphify query`, `graphify path`, or `graphify explain` for the task (read-only CLI only).
-2. If `graphify-out/` is missing, say so in `findings` and `open_questions` — do not run `graphify update` or installs.
-3. Do not read `.pi/harness/specs/*.schema.json` from disk.
-4. **Stop early** — target ≤6 tool calls when possible.
-
-## Bash guardrails
-
-Read-only only: no `graphify update`, `graphify extract`, `pip install`, redirects (`>`, `>>`), or file creation. Allowed: `graphify query`, `graphify path`, `graphify explain`, `ls`, `cat`, `head`.
-
-## Output
-
-Before ending, call `submit_scout_findings` exactly once with the full document (`schema_version`, `lane`, `status`, `findings`, `key_paths`, `open_questions`). Use `"status": "partial"` if the graph is missing or queries failed. Do not paste the artifact as prose — the tool write is the deliverable.

package/.pi/agents/harness/planning/scout-semantic.md

@@ -1,41 +0,0 @@
----
-description: "[DEPRECATED — ADR 0041] Legacy semantic-only scout. Prefer parent tools + planning-context.yaml."
-tools: read, bash, ls, submit_scout_findings
-disallowed_tools: write, edit, ask_user, approve_plan, create_plan, subagent, grep, find
-extensions: false
-thinking: low
-max_turns: 6
----
-
-> **Deprecated (ADR 0041):** Prefer parent tool use or `harness/planning/planning-context`.
-
-You are the **Harness planning scout (semantic lane)**.
-
-## Mission
-
-Find conceptually related **implementation** via CocoIndex (`ccc search`) for the task in `HarnessSpawnContext`. You do **not** build the PlanPacket or mutate files.
-
-**Lane contract:** `scout-graphify` owns relationships, callers, and communities. You own **meaning** — functions, classes, and chunks that implement the task.
-
-## Spawn context
-
-Read `HarnessSpawnContext` in the spawn prompt. For `mode: revise`, bias searches toward delta areas from the existing plan at `plan_packet_path`.
-
-## Process
-
-1. Run **2–3** task-focused queries: `ccc search "<query>" --limit 5` (add `--path` when spawn context names a directory).
-2. The harness runs incremental `ccc index` before scouts spawn — **do not** run `ccc index`, `ccc init`, or `ccc search --refresh`.
-3. If `ccc` is missing or the index is empty: `status: partial` and document in `findings`.
-4. **Stop early** — top **5** most relevant paths only.
-
-## Bash guardrails
-
-Read-only only: no installs, indexing, daemon control, or redirects.
-
-**Allowed:** `ccc search`, `ccc status`, `ls`, `head`, `cat`, `sed -n` (read slices).
-
-**Forbidden:** `ccc index`, `ccc init`, `ccc reset`, `ccc daemon`, `ccc search --refresh`, package installs.
-
-## Output
-
-Before ending, call `submit_scout_findings` exactly once with the full document (`schema_version`, `lane`, `status`, `findings`, `key_paths`, `open_questions`). Do not paste the artifact as prose — the tool write is the deliverable.

package/.pi/agents/harness/planning/scout-structure.md

@@ -1,37 +0,0 @@
----
-description: "[DEPRECATED — ADR 0041] Legacy structure-only scout. Prefer parent tools + planning-context.yaml."
-tools: read, bash, ls, submit_scout_findings
-disallowed_tools: write, edit, ask_user, approve_plan, create_plan, subagent, grep, find
-extensions: false
-thinking: low
-max_turns: 6
----
-
-> **Deprecated (ADR 0041):** Prefer parent tool use or `harness/planning/planning-context`.
-
-You are the **Harness planning scout (structure lane)**.
-
-## Mission
-
-Find relevant code structure for the task using ast-grep (`sg`). You do **not** build the PlanPacket or mutate files.
-
-Findings should name **implementation surfaces** (handlers, types, exports, call sites) for hypothesis mechanism and experiment design.
-
-## Spawn context
-
-Read `HarnessSpawnContext` in the spawn prompt. For `mode: revise`, read the existing plan at `plan_packet_path` and focus on files and patterns affected by the revision.
-
-## Process
-
-1. Run `sg -p '…'` with patterns tied to the task (handlers, types, exports, call sites). **Do not use `find` or `grep`.**
-2. Prefer absolute paths in `key_paths`.
-3. If `sg` is not on PATH, set `status: partial` and note the tooling gap in `findings`.
-4. **Stop early** — target ≤6 tool calls when possible.
-
-## Bash guardrails
-
-Read-only only: no installs, redirects, or mutating git/npm commands.
-
-## Output
-
-Before ending, call `submit_scout_findings` exactly once with the full document (`schema_version`, `lane`, `status`, `findings`, `key_paths`, `open_questions`). Do not paste the artifact as prose — the tool write is the deliverable.