ultimate-pi 0.18.0 → 0.18.1

package/.agents/skills/harness-decisions/SKILL.md

@@ -72,4 +72,4 @@ Parent orchestrator calls **`approve_plan`** with the full `plan_packet` (scroll
 
 - **Parent orchestrator** during `/harness-plan` — `ask_user` for clarification; **`approve_plan`** then **`create_plan`** for the plan file.
 - `harness/planning/*` (scouts, decompose, hypothesis, hypothesis-eval) — JSON only; no `ask_user` / `approve_plan` / `create_plan`.
-- `harness/evaluator`, `harness/adversary`, and `harness/tie-breaker` — emit `human_required`; the **parent orchestrator** calls `ask_user`.
+- `harness/reviewing/evaluator`, `harness/reviewing/adversary`, and `harness/reviewing/tie-breaker` — emit `human_required`; the **parent orchestrator** calls `ask_user`.

package/.agents/skills/harness-orchestration/SKILL.md

@@ -40,7 +40,7 @@ Harness subprocesses load **`harness-subagent-submit`** (`PI_HARNESS_SUBPROCESS=
 | Command | `agent` |
 |---------|---------|
 | `/harness-plan` | Parent: planning context (tools) → decompose → hypothesis → Phase 3.5 artifacts → PlanPacket → eligibility + Review Gate → `approve_plan` + `create_plan` |
-| `/harness-run` | `harness/executor` (single worker) |
+| `/harness-run` | `harness/running/executor` (single worker) |
 | `/harness-review` | Parent verify → `evaluator` benchmark → `evaluator` verdict → `adversary` → optional `tie-breaker` (ADR 0039) |
 | `/harness-eval` | **Deprecated** → `/harness-review` |
 | `/harness-critic` | **Deprecated** → `/harness-review` |
@@ -48,7 +48,7 @@ Harness subprocesses load **`harness-subagent-submit`** (`PI_HARNESS_SUBPROCESS=
 
 ## Review isolation
 
-Spawn `harness/evaluator` / `harness/adversary` via `subagent` in the **same** parent session. `review-integrity` allows `subagent` when `agent` is in the review set.
+Spawn `harness/reviewing/evaluator` / `harness/reviewing/adversary` via `subagent` in the **same** parent session. `review-integrity` allows `subagent` when `agent` is in the review set.
 
 ## ask_user policy
 
@@ -56,8 +56,8 @@ Spawn `harness/evaluator` / `harness/adversary` via `subagent` in the **same** p
 |------|------------|
 | Parent orchestrator | Yes (plan clarification, `approve_plan`, router tune) |
 | `harness/planning/*` | No — `human_required` in output if stuck |
-| `harness/evaluator`, `harness/adversary`, `harness/tie-breaker` | `human_required` in subprocess JSON |
-| `harness/executor` | No — parent handles governance |
+| `harness/reviewing/evaluator`, `harness/reviewing/adversary`, `harness/reviewing/tie-breaker` | `human_required` in subprocess JSON |
+| `harness/running/executor` | No — parent handles governance |
 
 ## Spawn pattern (`/harness-plan`)
 

package/.agents/skills/harness-review/SKILL.md

@@ -21,20 +21,20 @@ description: >-
 
 | Phase | Practice | Actor | Artifact |
 |-------|----------|-------|----------|
-| 1 | Automated QC + Sentrux fitness functions | Parent | `harness-verify.mjs`, `sentrux gate .`, `benchmark-log.yaml`, `sentrux-signal.yaml` |
-| 2 | Measure actuals (EVM) | `harness/evaluator` benchmark | `eval-verdict.yaml` |
+| 1 | Automated QC + Sentrux fitness functions | Parent | `harness-verify.mjs`, `harness-sentrux-cli.mjs gate`, `benchmark-log.yaml`, `sentrux-signal.yaml` |
+| 2 | Measure actuals (EVM) | `harness/reviewing/evaluator` benchmark | `eval-verdict.yaml` |
 | 2b | Controlling | Parent | Write `review-outcome.yaml`; route via `remediation_class` (not fail-fast abort) |
 | 6 | Outcome | Parent | `review-outcome.yaml` → `/harness-steer` or replan |
-| 3 | Policy audit | `harness/evaluator` verdict | same YAML |
-| 4 | Red team | `harness/adversary` | `adversary-report.yaml` |
-| 5 | Arbitration | `harness/tie-breaker` | only if block + conditional_pass |
+| 3 | Policy audit | `harness/reviewing/evaluator` verdict | same YAML |
+| 4 | Red team | `harness/reviewing/adversary` | `adversary-report.yaml` |
+| 5 | Arbitration | `harness/reviewing/tie-breaker` | only if block + conditional_pass |
 
 ## Phase 1 — Sentrux (structural actuals)
 
 When `HARNESS_SENTRUX_REQUIRED=true` (default in `.env.example`):
 
-1. `node "$UP_PKG/.pi/scripts/harness-verify.mjs"` — rules drift + `sentrux check` when CLI installed.
-2. `sentrux gate .` — compare to baseline saved during `/harness-run`.
+1. `node "$UP_PKG/.pi/scripts/harness-verify.mjs"` — rules drift + Sentrux check when CLI installed.
+2. `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate` — compare to baseline saved during `/harness-run`.
 3. Write `artifacts/sentrux-signal.yaml` and append session entry `harness-sentrux-signal` (observation bus / PostHog).
 4. Optional `artifacts/benchmark-log.yaml` fields: `sentrux_check`, `sentrux_gate`, `harness_verify`.
 

package/.agents/skills/harness-sentrux-setup/SKILL.md

@@ -18,7 +18,7 @@ description: Bootstrap Sentrux architectural rules for harness projects — seed
 | **Bootstrap** | `harness/sentrux-bootstrap`, `harness-sentrux-bootstrap.mjs` | Greenfield seed + first sync |
 | **Steward** | `harness/sentrux-steward`, `/harness-sentrux-steward` | Proposes manifest changes (`artifacts/sentrux-manifest-proposal.yaml`); chair applies |
 | **Sync** | `sentrux-rules-sync.mjs`, `/harness-sentrux-sync` | Regenerates `rules.toml` from manifest after intent change |
-| **Observation** | `/harness-run`, `/harness-review` | `sentrux gate --save` / `check` / `gate` → `artifacts/sentrux-signal.yaml` |
+| **Observation** | `/harness-run`, `/harness-review` | `harness-sentrux-cli.mjs gate --save` / `check` / `gate` → `artifacts/sentrux-signal.yaml` |
 
 Never auto-sync manifest from directory trees. Material manifest edits need steward evidence + chair approval (ADR 0009).
 
@@ -39,6 +39,7 @@ Custom TOML **outside** `# --- harness:managed:start/end ---` is preserved on ev
 | First-time / harness-setup (idempotent) | `node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs"` |
 | After manifest edits | `node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs" --force` |
 | CI / verify only | `node "$UP_PKG/.pi/scripts/sentrux-rules-sync.mjs" --check` |
+| Run/review Sentrux observation | `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check` / `gate [--save]` |
 | In pi session | `/harness-sentrux-sync` (extension; uses `--force`) |
 
 **Bootstrap vs `--force`:** Default bootstrap/sync skips rewriting `rules.toml` when the manifest hash is unchanged. Use `--force` (or `/harness-sentrux-sync`) after changing `architecture.manifest.json` or when verify reports drift.
@@ -51,7 +52,7 @@ Custom TOML **outside** `# --- harness:managed:start/end ---` is preserved on ev
    node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs"
    ```
 3. Optional: `sentrux plugin add-standard` (language plugins; harness-setup Step 2.8).
-4. `sentrux check .` — fix violations or tune manifest `max_cc` / layers.
+4. `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check` — fix violations or tune manifest `max_cc` / layers.
 5. Commit `.sentrux/rules.toml` and project-specific `architecture.manifest.json`.
 
 ## External repos
@@ -63,6 +64,6 @@ Do **not** copy ultimate-pi's layer paths blindly into unrelated layouts — edi
 ## References
 
 - ADR 0009 — `.pi/harness/docs/adrs/0009-sentrux-rules-lifecycle.md`
-- Scripts — `.pi/scripts/sentrux-rules-sync.mjs`, `harness-sentrux-bootstrap.mjs`
+- Scripts — `.pi/scripts/sentrux-rules-sync.mjs`, `harness-sentrux-bootstrap.mjs`, `harness-sentrux-cli.mjs`
 - Agents — `harness/sentrux-bootstrap` (setup), `harness/sentrux-steward` (intent proposals)
 - Specs — `sentrux-manifest-proposal.schema.json`, `sentrux-signal.schema.json`

package/.agents/skills/harness-steer/SKILL.md

@@ -8,7 +8,7 @@ description: Post-review repair loop via harness-steer and executor repair mode
 Use after `/harness-review` when `artifacts/review-outcome.yaml` has `remediation_class: implementation_gap`.
 
 1. Read `repair-brief.yaml` and `plan_packet_path` (paths only).
-2. Set policy phase `execute`; spawn `harness/executor` with `mode: repair`.
+2. Set policy phase `execute`; spawn `harness/running/executor` with `mode: repair`.
 3. Always follow with `/harness-review`.
 
 See `.pi/prompts/harness-steer.md` and `.pi/harness/docs/adrs/0044-harness-steer-loop.md`.

package/.agents/skills/sentrux/SKILL.md

@@ -35,22 +35,22 @@ sentrux plugin add-standard
 
 ## Core workflows (project root)
 
-Run from the **target repo root** (where `.sentrux/rules.toml` lives).
+Run from the **target repo root** (where `.sentrux/rules.toml` lives), or prefer the bundled wrapper when invoked by harness commands from run directories.
 
 | When | Command | Notes |
 |------|---------|-------|
-| CI / pre-commit | `sentrux check .` | Exit 0 = pass, 1 = violations |
-| Before agent work | `sentrux gate --save .` | Save session baseline |
-| After agent work | `sentrux gate .` | Detect degradation vs baseline |
+| CI / pre-commit | `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check` | Exit 0 = pass, 1 = violations |
+| Before agent work | `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate --save` | Save session baseline |
+| After agent work | `node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate` | Detect degradation vs baseline |
 | Explore structure | `sentrux` or `sentrux .` | GUI treemap (optional) |
 
 Typical agent loop:
 
 ```bash
-sentrux gate --save .
+node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate --save
 # … agent edits …
-sentrux check .          # rules still pass?
-sentrux gate .           # structural regression?
+node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check  # rules still pass?
+node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" gate   # structural regression?
 ```
 
 If `check` fails, fix violations or tune manifest constraints (see **Rules** below). If `gate` reports degradation, inspect changed modules before merging.
@@ -73,7 +73,7 @@ Custom TOML outside `# --- harness:managed:start/end ---` is preserved on sync.
 |-------|------|
 | `sentrux-rules-sync` extension | Session start: warns if `rules.toml` drifts; auto-sync after plan/merge phases |
 | `/harness-sentrux-sync` | Force-regenerate rules from manifest (pi command) |
-| `harness-verify.mjs` | Runs `sentrux check .` when rules present |
+| `harness-verify.mjs` | Runs rules sync and Sentrux checks when rules are present |
 | **observation-bus** | Maps `harness-sentrux-signal` custom entries → evaluator observations |
 | **harness-eval** | Evaluate phase may require a Sentrux quality signal (stub or future MCP) per ADR 0006 |
 
@@ -90,7 +90,7 @@ High level: **execute** uses CLI gate/check around edits; **evaluate** consumes
 - Assume Sentrux **MCP** tools (`scan`, `session_start`, `health`, etc.) exist in **Pi** — they do not; use CLI only
 - Edit or rely on `.pi/mcp.json` for Pi sessions
 - Duplicate bootstrap/sync steps from **harness-sentrux-setup**
-- Skip `sentrux check .` after large refactors when `.sentrux/rules.toml` exists
+- Skip the root-resolving Sentrux check after large refactors when `.sentrux/rules.toml` exists
 
 ## References
 

package/.pi/agents/harness/planning/decompose.md

@@ -23,7 +23,7 @@ Read `HarnessSpawnContext` and the merged **scout lane JSON** in the spawn promp
 
 1. Read Phase 1 reconnaissance from spawn context paths — prefer `artifacts/planning-context.yaml`; legacy `artifacts/scout-*.yaml` lanes are accepted when present.
 2. Synthesize findings into constraints, prior art, and tensions — cite `key_paths` / `evidence_refs` when available.
-3. **Graphify dedup:** If `planning-context.yaml` has `coverage.architecture.status` of `ok`, or legacy `scout-graphify.yaml` has `status: ok`, do **not** run `graphify query` / `graphify explain` / `graphify path`. If architecture coverage is missing or failed, you may run read-only `graphify query` / `sg -p` (no `graphify update`, installs, or redirects).
+3. **Graphify dedup:** If `planning-context.yaml` has `coverage.architecture.status` of `ok`, do **not** run `graphify query` / `graphify explain` / `graphify path`. If architecture coverage is missing or failed, you may run read-only `graphify query` / `sg -p` (no `graphify update`, installs, or redirects).
 4. Do not read `.pi/harness/specs/*.schema.json` from disk.
 
 ## Phase 1 — DeepMind-style decomposition

package/.pi/extensions/00-harness-project-control.ts

@@ -0,0 +1,133 @@
+/**
+ * harness-project-control — always-on enable/disable for harness governance.
+ *
+ * Writes `.pi/harness/project.json`, blocks workflow slash commands while disabled,
+ * and emits `harness-project-enabled:changed` so live TUI surfaces update immediately.
+ */
+
+import type {
+	ExtensionAPI,
+	ExtensionCommandContext,
+} from "@earendil-works/pi-coding-agent";
+import {
+	isHarnessProjectEnabled,
+	isHarnessWorkflowCommand,
+	readHarnessProjectConfig,
+	writeHarnessProjectEnabled,
+} from "../lib/harness-project-config.js";
+import { parseHarnessSlashInput } from "../lib/harness-run-context.js";
+
+function showCommandMessage(
+	pi: ExtensionAPI,
+	ctx: ExtensionCommandContext,
+	text: string,
+): void {
+	if (ctx.hasUI) {
+		ctx.ui.notify(text, "info");
+		return;
+	}
+	pi.sendMessage({
+		customType: "harness-project-control",
+		content: text,
+		display: true,
+	});
+}
+
+function formatStatus(projectRoot: string): string {
+	const config = readHarnessProjectConfig(projectRoot);
+	const env = process.env.HARNESS_ENABLED?.trim();
+	const lines = [
+		`Harness governance: ${config.enabled ? "enabled" : "disabled"}`,
+		`Config: .pi/harness/project.json`,
+	];
+	if (env) {
+		lines.push(`Env override: HARNESS_ENABLED=${env}`);
+	}
+	if (config.updated_at) {
+		lines.push(`Updated: ${config.updated_at}`);
+	}
+	if (!config.enabled) {
+		lines.push(
+			"Workflow commands (/harness-plan, /harness-run, …) are blocked until you run /harness-enable.",
+		);
+	} else {
+		lines.push("Run /harness-disable to turn governance off.");
+	}
+	return lines.join("\n");
+}
+
+export default function harnessProjectControl(pi: ExtensionAPI) {
+	pi.on("input", async (event) => {
+		if (event.source === "extension") {
+			return { action: "continue" as const };
+		}
+		const parsed = parseHarnessSlashInput(event.text);
+		if (!parsed || !isHarnessWorkflowCommand(parsed.command)) {
+			return { action: "continue" as const };
+		}
+		if (isHarnessProjectEnabled()) {
+			return { action: "continue" as const };
+		}
+		return {
+			action: "handled" as const,
+			message: [
+				`Harness governance is disabled — /${parsed.command} was not started.`,
+				"Run /harness-enable to restore the workflow command surface.",
+			].join("\n"),
+		};
+	});
+
+	pi.registerCommand("harness-enable", {
+		description: "Enable harness governance for this project",
+		handler: async (_args, ctx) => {
+			const projectRoot = process.cwd();
+			const config = writeHarnessProjectEnabled(projectRoot, true);
+			const effectiveConfig = readHarnessProjectConfig(projectRoot);
+			pi.events.emit("harness-project-enabled:changed", {
+				enabled: effectiveConfig.enabled,
+				projectRoot,
+				updated_at: config.updated_at,
+			});
+			showCommandMessage(
+				pi,
+				ctx,
+				[
+					"Harness governance enabled.",
+					`Wrote .pi/harness/project.json (enabled=true, updated ${config.updated_at}).`,
+					"Live TUI surfaces were refreshed.",
+				].join("\n"),
+			);
+		},
+	});
+
+	pi.registerCommand("harness-disable", {
+		description: "Disable harness governance for this project",
+		handler: async (_args, ctx) => {
+			const projectRoot = process.cwd();
+			const config = writeHarnessProjectEnabled(projectRoot, false);
+			const effectiveConfig = readHarnessProjectConfig(projectRoot);
+			pi.events.emit("harness-project-enabled:changed", {
+				enabled: effectiveConfig.enabled,
+				projectRoot,
+				updated_at: config.updated_at,
+			});
+			showCommandMessage(
+				pi,
+				ctx,
+				[
+					"Harness governance disabled.",
+					`Wrote .pi/harness/project.json (enabled=false, updated ${config.updated_at}).`,
+					"Workflow slash commands are blocked immediately.",
+					"Live TUI surfaces were refreshed.",
+				].join("\n"),
+			);
+		},
+	});
+
+	pi.registerCommand("harness-enabled-status", {
+		description: "Show whether harness governance is enabled for this project",
+		handler: async (_args, ctx) => {
+			showCommandMessage(pi, ctx, formatStatus(process.cwd()));
+		},
+	});
+}

package/.pi/extensions/budget-guard.ts

@@ -12,6 +12,7 @@ import {
 	isHarnessBudgetEnforceOn,
 	shouldEmitBlockingBudgetExhausted,
 } from "../lib/harness-budget-enforce.js";
+import { isHarnessProjectEnabled } from "../lib/harness-project-config.js";
 import { getRunIdFromSession } from "../lib/harness-run-context.js";
 
 type HarnessPhase = "plan" | "execute" | "evaluate" | "adversary" | "merge";
@@ -203,6 +204,7 @@ async function emitBudgetEvent(
 const debouncedSoftLimit = new Map<string, boolean>();
 
 export default function budgetGuard(pi: ExtensionAPI) {
+	if (!isHarnessProjectEnabled()) return;
 	pi.on("tool_call", async (_event, ctx) => {
 		const policy = getPolicyContext(ctx);
 		if (policy.phase === null || policy.budgetBypass) return undefined;

package/.pi/extensions/debate-orchestrator.ts

@@ -6,6 +6,7 @@
 
 import { join } from "node:path";
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
+import { isHarnessProjectEnabled } from "../lib/harness-project-config.js";
 import { getRunIdFromSession } from "../lib/harness-run-context.js";
 import {
 	acceptDebateRound,
@@ -32,6 +33,7 @@ function getRunId(ctx: {
 }
 
 export default function debateOrchestrator(pi: ExtensionAPI) {
+	if (!isHarnessProjectEnabled()) return;
 	const hooks = {
 		appendEntry: (customType: string, data: unknown) =>
 			pi.appendEntry(customType, data),

package/.pi/extensions/harness-ask-user.ts

@@ -18,13 +18,13 @@ import {
 	toToolDetails,
 	validateAskParams,
 } from "./lib/ask-user/validate.js";
-import { claimExtensionLoad } from "./lib/extension-load-guard.js";
+import { claimHarnessGovernanceLoad } from "./lib/extension-load-guard.js";
 
 // @ts-expect-error pi extensions run as ESM
 const MODULE_URL = import.meta.url;
 
 export default function harnessAskUser(pi: ExtensionAPI) {
-	if (!claimExtensionLoad("harness-ask-user", MODULE_URL)) return;
+	if (!claimHarnessGovernanceLoad("harness-ask-user", MODULE_URL)) return;
 	pi.registerTool({
 		name: "ask_user",
 		label: "Ask User",

package/.pi/extensions/harness-debate-tools.ts

@@ -24,7 +24,7 @@ import {
 	openDebateBus,
 } from "./lib/debate-bus-core.js";
 import { getDebateState } from "./lib/debate-bus-state.js";
-import { claimExtensionLoad } from "./lib/extension-load-guard.js";
+import { claimHarnessGovernanceLoad } from "./lib/extension-load-guard.js";
 import { captureHarnessEvent } from "./lib/harness-posthog.js";
 import { DEBATE_AGENT_SUBMIT_TOOL } from "./lib/harness-subagent-submit-registry.js";
 import {
@@ -115,7 +115,7 @@ function subagentResults(
 const USE_SUBMIT_TOOLS = process.env.HARNESS_SUBMIT_TOOLS !== "0";
 
 export default function harnessDebateTools(pi: ExtensionAPI) {
-	if (!claimExtensionLoad("harness-debate-tools", MODULE_URL)) return;
+	if (!claimHarnessGovernanceLoad("harness-debate-tools", MODULE_URL)) return;
 
 	pi.on("tool_result", async (event, ctx) => {
 		if (event.isError || event.toolName !== "subagent") return;

package/.pi/extensions/harness-live-widget.ts

@@ -2,6 +2,7 @@ import type {
 	ExtensionAPI,
 	ExtensionContext,
 } from "@earendil-works/pi-coding-agent";
+import { isHarnessProjectEnabled } from "../lib/harness-project-config.js";
 import { evaluateCrossSessionResume } from "../lib/harness-run-context.js";
 import {
 	deriveHarnessStatusHint,
@@ -245,7 +246,7 @@ export default function harnessLiveWidget(pi: ExtensionAPI) {
 	let mountCtx: ExtensionContext | null = null;
 
 	function mountHarnessWidget(ctx: ExtensionContext): void {
-		if (!ctx.hasUI) return;
+		if (!ctx.hasUI || !isHarnessProjectEnabled()) return;
 		const state = stateStore.refresh(ctx);
 		lastRenderHash = computeRenderHash(state);
 
@@ -270,9 +271,21 @@ export default function harnessLiveWidget(pi: ExtensionAPI) {
 		updateStatusFallback(ctx, state);
 	}
 
+	function clearHarnessWidget(ctx: ExtensionContext): void {
+		if (!ctx.hasUI) return;
+		const tui = tuiHandle;
+		ctx.ui.setWidget("harness-live", undefined);
+		ctx.ui.setStatus("harness-mode", undefined);
+		widgetMounted = false;
+		tuiHandle = null;
+		component = null;
+		lastRenderHash = "";
+		tui?.requestRender();
+	}
+
 	function remountHarnessLiveWidget(ctx: ExtensionContext): void {
 		if (!ctx.hasUI || !widgetMounted) return;
-		ctx.ui.setWidget("harness-live", undefined);
+		clearHarnessWidget(ctx);
 		mountHarnessWidget(ctx);
 	}
 
@@ -300,6 +313,20 @@ export default function harnessLiveWidget(pi: ExtensionAPI) {
 		if (mountCtx) scheduleRefresh(mountCtx);
 	});
 
+	pi.events.on("harness-project-enabled:changed", (payload: unknown) => {
+		const data =
+			payload && typeof payload === "object"
+				? (payload as { enabled?: boolean })
+				: null;
+		if (!mountCtx || typeof data?.enabled !== "boolean") return;
+		if (data.enabled) {
+			mountHarnessWidget(mountCtx);
+			tuiHandle?.requestRender();
+			return;
+		}
+		clearHarnessWidget(mountCtx);
+	});
+
 	function updateStatusFallback(
 		ctx: ExtensionContext,
 		state: HarnessUiState,
@@ -330,6 +357,10 @@ export default function harnessLiveWidget(pi: ExtensionAPI) {
 		refreshQueued = true;
 		queueMicrotask(() => {
 			refreshQueued = false;
+			if (!isHarnessProjectEnabled()) {
+				clearHarnessWidget(ctx);
+				return;
+			}
 			const state = stateStore.refresh(ctx);
 			const hash = computeRenderHash(state);
 			updateStatusFallback(ctx, state);

package/.pi/extensions/harness-plan-approval.ts

@@ -12,7 +12,7 @@ import {
 	parsePlanApprovalFromMessage,
 	planPacketSummary,
 } from "../lib/harness-run-context.js";
-import { claimExtensionLoad } from "./lib/extension-load-guard.js";
+import { claimHarnessGovernanceLoad } from "./lib/extension-load-guard.js";
 import {
 	CREATE_PLAN_GUIDELINES,
 	CREATE_PLAN_SNIPPET,
@@ -52,7 +52,7 @@ import { validatePlanDebateGate } from "./lib/plan-debate-gate.js";
 const MODULE_URL = import.meta.url;
 
 export default function harnessPlanApproval(pi: ExtensionAPI) {
-	if (!claimExtensionLoad("harness-plan-approval", MODULE_URL)) return;
+	if (!claimHarnessGovernanceLoad("harness-plan-approval", MODULE_URL)) return;
 	pi.registerMessageRenderer(
 		"harness-plan-draft",
 		(message, _options, theme) => {