@lifeaitools/rdc-skills 0.35.4 → 0.35.6

package/skills/brochurify/SKILL.md

@@ -12,6 +12,7 @@ triggers:
   - monkey_dispatch payload with skill="brochurify"
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 # rdc:brochurify Orchestrator
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Report brochure job state, artifacts, and blockers directly; do not dump raw tool logs.

package/skills/clean-code-analyzer/SKILL.md

@@ -8,6 +8,7 @@ description: >-
   mechanical AST checks, not LLM judgment — see `scripts/clean-code-score.mjs`.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/collab/SKILL.md

@@ -230,7 +230,7 @@ most common failure and it fails at the guard layer, not the prompt layer.
 > version of this table said the opposite.** Managed identity is an 8-field record
 > (`lane, role, repoIdentity, ownerPid, ownerStartFingerprint, sessionId,
 > leaseEpoch, ownerToken`) built by `buildStartupIdentity()` in
-> [`pool/codex-topology.mjs`](file:///C:/Dev/lifeai-env/pool/codex-topology.mjs)
+> [`pool/codex-topology.mjs`](file:///C:/Dev/lifeai/node_modules/@lifeai/lifeai-env/pool/codex-topology.mjs)
 > and minted **only by the interactive launcher**, which also claims the lease.
 > `codex exec` has no lane-claim path, so it cannot produce that record — which
 > means **a headless Codex peer cannot write in any lane, including its own**.
@@ -245,7 +245,7 @@ most common failure and it fails at the guard layer, not the prompt layer.
 > fires when there is **no lease at all** (`ownerMatchesLease` returns false for a
 > null lease), so it will send you hunting a conflicting owner that does not exist.
 
-file:///C:/Dev/lifeai-env/pool/codex-topology.mjs
+file:///C:/Dev/lifeai/node_modules/@lifeai/lifeai-env/pool/codex-topology.mjs
 | **`local-llm`** | local endpoint per `.claude/context/clauth.md`; credential via `curl -s http://127.0.0.1:52437/v/<service>` | none (no repo attachment) | Small context windows: send the contract and the open points, never the whole document. Link paths instead of pasting files. |
 | **`claude-agent`** | `Agent` tool, or `claude -p --bare` / `claude --bg` | **`isolation: "worktree"` as an actual tool parameter** if it will commit — a prose claim of isolation is inert | Parallel agents on a shared checkout race on `git stash` and `.git/index`. See `.claude/rules/subagent-credentials.md`. |
 | **`claude-ai`** | chitchat MCP (`chitchat_send` / `chitchat_poll` / `chitchat_reply`) + SSE | session-scoped | Messages evaporate when the session stops — export durable decisions to TinTin. |

package/skills/convert/SKILL.md

@@ -3,6 +3,7 @@ name: convert
 description: "Usage `rdc:convert <input> [--out <dir>] [--to markdown|word] [--images assets|base64|s3]` — Convert .docx/.pptx/.ppt → Markdown (Word OMML equations as KaTeX TeX, tables, images) or Markdown → Word via the build-corpus CLI from npm `regen.mde`. Portable: runs in any session that can reach npm — Claude Code CLI, Codex, and claude.ai can fetch + run it. Use whenever the user asks to convert an Office document, build a Markdown corpus from .docx/.pptx, turn Markdown into a .docx, or open the report in the regen-mde editor on Windows."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 # rdc:convert — Office ↔ Markdown conversion (build-corpus) + regen-mde editor
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/skills/edit/SKILL.md

@@ -14,6 +14,18 @@ description: "Usage `rdc:edit <site|brand|route|file>` — open the local websit
 
 # rdc:edit — Local Website Editor Launcher
 
+**This skill is the designated handler `rdc-harness` dispatches to.**
+`packages/work/src/editors.mjs`'s `BY_CLASS` table maps `site-html`/`site-ts`
+product classes to editor id `'rdc:edit'` — when an agent calls
+`node C:/Dev/rdc-harness/bin/rdc-harness.mjs edit <slug>` against a website
+target, its receipt names `editorId: 'rdc:edit'` and an `editableBoundary`.
+This skill IS that handler: resolve the same target, launch/reuse the editor
+host, use the harness's `editableBoundary` as the save boundary if the call
+originated from a harness `edit` receipt. Every other product class
+(`app`/`package`/`mcp`/`model`/`artifact`) maps to editor id `'source'` — a
+boundary-checked file save with no live/co-editing surface at all; that gap
+is real and unbuilt, not something this skill covers.
+
 ## When to Use
 - The user wants to open a site, brand, route, or file in the local editor app
 - The user says "open this in the editor" or asks for the editor-host workflow

package/skills/env/SKILL.md

@@ -3,6 +3,7 @@ name: env
 description: "Usage `rdc:env [status|install|repair|update]` — Manage the LIFEAI environment harness: check status, install on a fresh box, repair broken services, or pull updates. Reads $LIFEAI_ENV/manifest.json as the source of truth. Use when: 'check the environment', 'install environment', 'repair environment', 'update environment', 'setup env', 'fix env', 'env status', or after a reboot/GPU crash."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.
@@ -13,17 +14,39 @@ description: "Usage `rdc:env [status|install|repair|update]` — Manage the LIFE
 - After a reboot or GPU crash — verify everything came back up
 - Setting up a fresh box — install all tools and services
 - Something is broken — repair services, MCPs, CodeFlow
-- Routine update — pull latest env repo and run drift check
+- Routine update — bring the harness current and run a drift check
 - "check the environment", "fix my setup", "install environment"
 
+## The harness arrives by one of two channels — find out which BEFORE acting
+
+`$LIFEAI_ENV` is **not** necessarily a git repo, and on a normal box it is not.
+
+| channel | what `$LIFEAI_ENV` is | who owns freshness |
+|---|---|---|
+| **npm** (the normal box) | an installed package, e.g. `C:/Dev/lifeai/node_modules/@lifeai/lifeai-env` | `npm` — `env-boot` installs into the owning prefix at session start |
+| **git** (the publishing box) | a checkout of `LIFEAI/environment` | `land.mjs` → fetch → `env-install` |
+
+Every `git` command in this skill applies to the **git** channel only. Against an
+npm install they fail outright — `fatal: not a git repository` — because there is
+no `.git` there at all. Ask first:
+
+```bash
+node "$LIFEAI_ENV/machines/env-boot.mjs" check
+```
+
+It reports the installed version, the published version, and which channel this
+box is on, and changes nothing. Do not infer the channel from the path: the git
+tree at `C:/Dev/lifeai-env` still exists on the publishing box alongside the npm
+install, so a path that looks familiar proves nothing.
+
 ## Subcommands
 
 | Command | What it does |
 |---------|-------------|
-| `status` (default) | Read-only check: env repo version, tool versions, MCP health, shim integrity, CodeFlow brain |
-| `install` | Full provision: clone env repo if missing, set LIFEAI_ENV, install tools, configure MCPs |
+| `status` (default) | Read-only check: channel + harness version, tool versions, MCP health, shim integrity, CodeFlow brain |
+| `install` | Full provision: install the harness if missing, set LIFEAI_ENV, install tools, configure MCPs |
 | `repair` | Diagnose and fix: restart crashed services, rebuild stale dists, fix broken shims |
-| `update` | Pull latest env repo, re-run audit, report drift, refresh shims if new scripts added |
+| `update` | Bring the harness current for its channel, re-run audit, report drift, refresh shims if new scripts added |
 
 ## Procedure
 
@@ -34,21 +57,42 @@ LIFEAI_ENV="${LIFEAI_ENV:-C:/Dev/lifeai-env}"
 ```
 
 If `$LIFEAI_ENV` is not set AND the default path doesn't exist:
-- For `install`: clone the repo and set the env var
-- For all others: STOP with `BLOCKED: environment repo not found. Run: rdc:env install`
+- For `install`: install the harness (see the channel table above — npm on a
+  normal box) and set the env var. `provision.ps1` is self-locating
+  (`$EnvRoot = $PSScriptRoot`), so running it *from* an install is what points
+  `LIFEAI_ENV` at that install. Machine scope needs elevation; without it it
+  falls back to User scope and says so.
+- For all others: STOP with `BLOCKED: environment harness not found. Run: rdc:env install`
 
 Read `$LIFEAI_ENV/manifest.json` — this is the harness inventory.
 
-### Step 1: Environment repo state
+### Step 1: Harness state — channel first, then freshness
 
 ```bash
-git -C "$LIFEAI_ENV" fetch origin 2>/dev/null
-git -C "$LIFEAI_ENV" rev-list --count HEAD..origin/main
+node "$LIFEAI_ENV/machines/env-boot.mjs" check
 ```
 
-Report: version from manifest.json, commits behind origin, last pull date.
+One command, both channels, no mutation. It prints the installed version, the
+published version, and — on an npm hub outside `npm root -g` — the prefix an
+update would target.
+
+Report: version from manifest.json, the channel, and how far behind it is.
+
+**For `update` and `repair`, bring it current by its own channel:**
+
+```bash
+# npm channel — env-boot derives the owning prefix itself. Do NOT hand-roll a
+# prefix, and do NOT use a bare `npm install -g`: on a hub outside `npm root -g`
+# that silently updates a DIFFERENT directory and the hub never moves.
+node "$LIFEAI_ENV/machines/env-boot.mjs"
+
+# git channel (publishing box only)
+git -C "$LIFEAI_ENV" pull --ff-only origin main
+```
 
-For `update`: pull if behind. For `repair`: pull if behind (stale harness may be the cause).
+> **Never report a version comparison as a freshness verdict without saying which
+> channel produced it.** On a git hub `env-boot` deliberately does not ask npm at
+> all — the two versions differing there is expected, not a broken publish.
 
 ### Step 2: Tool versions (audit)
 
@@ -123,8 +167,8 @@ This is the same check the startup guard runs. Zero blockers = environment healt
 
 | Check | Status | Detail |
 |-------|--------|--------|
-| Env repo | ✅ | v0.2.0, 0 behind origin |
-| LIFEAI_ENV | ✅ | C:/Dev/lifeai-env (Machine scope) |
+| Harness | ✅ | v0.8.119, npm channel, current |
+| LIFEAI_ENV | ✅ | C:/Dev/lifeai/node_modules/@lifeai/lifeai-env (Machine scope) |
 | Node | ✅ | v22.14.0 (min 22.0.0) |
 | pnpm | ✅ | 10.12.1 (min 10.0.0) |
 | clauth | ✅ | v1.30.2, unlocked |

package/skills/extract-verifier-rules/SKILL.md

@@ -12,6 +12,7 @@ triggers:
   - nightly cron at 3:00 AM PT
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 # rdc:extract-verifier-rules
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Return candidate rules, evidence, and PR status directly; do not dump raw tool logs.

package/skills/fs-mcp/SKILL.md

@@ -3,6 +3,7 @@ name: fs-mcp
 description: "Usage `rdc:fs-mcp <task>` — Use the File System MCP bridge for live repo reads, safe writes, cloud-to-local ingest, and GitHub-branch imports into a dirty local monorepo. Use when Claude.ai, Cowork, or CLI agents need fs_read/fs_write/fs_import_git_files guidance."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/help/SKILL.md

@@ -3,6 +3,7 @@ name: help
 description: "Usage `rdc:help` — Show all MCP skills with usage, requirements, slash forms, and codeflow status. Reads `.claude-plugin/plugin.json` skills_meta (single source of truth). Call when unsure which skill to use or what args it takes."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 

package/skills/lifeai-brochure-author/SKILL.md

@@ -20,6 +20,7 @@ required_validators:
     blocking: true
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 # LIFEAI Brochure Authoring Contract
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Return the authored JSX guidance or verification result directly; do not dump raw tool logs.

package/skills/new-model/SKILL.md

@@ -18,6 +18,7 @@ description: >
   Trigger when asked to create, register, or check whether a reference model exists.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/package-design/SKILL.md

@@ -6,6 +6,7 @@ description: >-
   and sit at the right size.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/pattern-advisor/SKILL.md

@@ -8,6 +8,7 @@ description: >-
   only; never rewrites code itself.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/pattern-refactoring-guide/SKILL.md

@@ -6,6 +6,7 @@ description: >-
   concrete before/after refactor plan. Produces a plan, does not apply it.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/refactor/SKILL.md

@@ -3,6 +3,7 @@ name: refactor
 description: "Usage `rdc:refactor <epic-id|topic> --takeover <reason>` — Governed consolidation and implementation of a cross-cutting refactor. Authorizes an explicit takeover, preserves evidence, re-parents relevant work through the consolidation RPC, isolates every writer, and uses the same review, validator, landing, and delivery gates as rdc:build."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **OUTPUT CONTRACT:** `guides/output-contract.md`
 
 # rdc:refactor

package/skills/regen-media/SKILL.md

@@ -3,6 +3,7 @@ name: regen-media
 description: "Usage `rdc:regen-media <generate|edit|upscale|upload> <brief-or-path>` - Primary image-generation and Regen Media asset workflow. Use for image generation, image editing/upscaling, GPT Image/gpt-image-2 requests, Codex built-in image_gen, and uploading finished images to regen-media/R2. The default path is keyless local Codex gpt-image-2 via the built-in image_gen tool; server-side regen-media MCP/API generation is fallback only."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/solid-validator/SKILL.md

@@ -8,6 +8,7 @@ description: >-
   `scripts/solid-score.mjs` for the mechanism.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/terminal-config/SKILL.md

@@ -3,6 +3,7 @@ name: terminal-config
 description: "Usage `rdc:terminal-config <task>` — read and safely modify Windows Terminal settings, shell profiles, and agent startup sequencing without relying on machine-specific paths."
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/skills/testing-strategy/SKILL.md

@@ -8,6 +8,7 @@ description: >-
   covers whether a surface's behavior is actually provable, and how.
 ---
 
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `.rdc/guides/agent-bootstrap.md`) — this is also where the global rdc-harness-use policy for create/open/build/deploy work lives.
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
 > Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
 > One checklist upfront, updated in place, shown again at end with a 1-line verdict.

package/tests/foreground-process-gate.test.mjs

@@ -0,0 +1,114 @@
+#!/usr/bin/env node
+/**
+ * foreground-process-gate.js — narrowed to Playwright headed/UI-mode only
+ * (epic 688ad6da WP-4, lifeai-env). Four window-focus/process-launch checks
+ * (checkWindowFocusApi, checkPowerShell, checkCmdStart, checkDirectShellLaunch)
+ * were removed; the replacement is lifeai-env's lib/TermLaunch.psm1 caller-
+ * logging, which lives in a different repo and is not this file's job to
+ * re-implement or re-check.
+ *
+ * This file's job is now to prove two things stay true going forward:
+ *   1. The four retired checks no longer block anything -- a real regression
+ *      here would silently reintroduce ceremony an operator explicitly
+ *      retired, with no other test anywhere positioned to catch it.
+ *   2. checkPlaywright survives untouched (Design Decision D3) -- this is a
+ *      SEPARATE safety property, not part of the terminal-launch
+ *      consolidation, and narrowing the file must never have narrowed this.
+ *
+ * Run: node tests/foreground-process-gate.test.mjs
+ */
+import { dirname, join, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { spawnSync } from 'node:child_process';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const REPO_ROOT = resolve(__dirname, '..');
+const HOOK = join(REPO_ROOT, 'hooks', 'foreground-process-gate.js');
+
+const failures = [];
+function assert(name, condition, detail = '') {
+  if (!condition) failures.push(`${name}${detail ? `: ${detail}` : ''}`);
+  else process.stdout.write(`  ok  ${name}\n`);
+}
+
+function runGate(command) {
+  const res = spawnSync(process.execPath, [HOOK], {
+    input: JSON.stringify({ tool_name: 'Bash', tool_input: { command } }),
+    encoding: 'utf8',
+  });
+  const blocked = res.status === 1;
+  return { blocked, stdout: res.stdout, status: res.status };
+}
+
+// ===========================================================================
+// 1. The four retired checks no longer block anything.
+// ===========================================================================
+
+{
+  const r = runGate('Start-Process -FilePath node.exe -ArgumentList "server.js"');
+  assert('Start-Process with no -WindowStyle Hidden no longer blocks (checkPowerShell retired)',
+    r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+{
+  const r = runGate('cmd /c start node.exe server.js');
+  assert('cmd /c start without /min no longer blocks (checkCmdStart retired)',
+    r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+{
+  const r = runGate('powershell.exe -File C:\\Dev\\some-script.ps1');
+  assert('bare PowerShell .ps1 launch no longer blocks (checkDirectShellLaunch retired)',
+    r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+{
+  const r = runGate('[Win32]::SetForegroundWindow($handle)');
+  assert('a window-focus Win32 API call no longer blocks (checkWindowFocusApi retired)',
+    r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+// ===========================================================================
+// 2. checkPlaywright survives, untouched -- a separate safety property.
+// ===========================================================================
+
+{
+  const r = runGate('npx playwright test --headed');
+  assert('Playwright --headed still blocks',
+    r.blocked === true, `status=${r.status} stdout=${r.stdout}`);
+  assert('Playwright --headed block message names the right reason',
+    /must run headless/.test(r.stdout), r.stdout);
+}
+
+{
+  const r = runGate('PWDEBUG=1 npx playwright test');
+  assert('Playwright PWDEBUG=1 still blocks',
+    r.blocked === true, `status=${r.status} stdout=${r.stdout}`);
+}
+
+{
+  const r = runGate('npx playwright show-report');
+  assert('Playwright show-report still blocks',
+    r.blocked === true, `status=${r.status} stdout=${r.stdout}`);
+  assert('Playwright show-report block message names the right reason',
+    /launches foreground UI/.test(r.stdout), r.stdout);
+}
+
+{
+  const r = runGate('npx playwright test --reporter=list');
+  assert('an ordinary headless Playwright run is NOT blocked',
+    r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+{
+  const r = runGate('git status');
+  assert('an unrelated ordinary command passes clean', r.blocked === false, `status=${r.status} stdout=${r.stdout}`);
+}
+
+// ===========================================================================
+if (failures.length > 0) {
+  console.error('\nforeground-process-gate tests — FAIL\n');
+  for (const f of failures) console.error(`  - ${f}`);
+  process.exit(1);
+}
+console.log('\nforeground-process-gate tests — PASS');

package/tests/harness-gates.test.mjs

@@ -146,34 +146,16 @@ const WI = 'aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee';
 }
 
 // ===========================================================================
-// 2. foreground-process-gate.js
+// 2. foreground-process-gate.js — moved to its own file, tests/foreground-process-gate.test.mjs
+//
+// Narrowed 2026-08-26 (epic 688ad6da WP-4, lifeai-env): the window-focus/
+// process-launch checks this section used to assert (SetForegroundWindow
+// blocking, hidden/minimized allowances) were retired — that whole class is
+// now caller-logged by lifeai-env's lib/TermLaunch.psm1, not hard-blocked
+// here. The dedicated test file covers what remains (checkPlaywright) plus
+// asserts the four retired checks stay retired, so removing this embedded
+// section is not a coverage loss — see that file instead.
 // ===========================================================================
-{
-  const focusPayload = {
-    tool_input: {
-      command: "powershell -NoProfile -Command \"Add-Type '[DllImport(\\\"user32.dll\\\")] public static extern bool SetForegroundWindow(System.IntPtr hWnd);'\"",
-    },
-  };
-  const r = runHook('foreground-process-gate.js', focusPayload, {});
-  assert('FPG blocks SetForegroundWindow focus API', r.status === 1, `status=${r.status} ${r.stdout}${r.stderr}`);
-  assert('FPG block mentions window focus operations', /Window focus\/restore\/minimize\/collapse/.test(r.stdout + r.stderr));
-
-  const hiddenPayload = {
-    tool_input: {
-      command: 'powershell.exe -NoProfile -NonInteractive -WindowStyle Hidden -File ".\\\\scripts\\\\helper.ps1"',
-    },
-  };
-  const h = runHook('foreground-process-gate.js', hiddenPayload, {});
-  assert('FPG allows hidden PowerShell helper', h.status === 0, `status=${h.status} ${h.stdout}${h.stderr}`);
-
-  const minimizedPayload = {
-    tool_input: {
-      command: 'Start-Process powershell.exe -WindowStyle Minimized -ArgumentList "-NoProfile"',
-    },
-  };
-  const m = runHook('foreground-process-gate.js', minimizedPayload, {});
-  assert('FPG allows minimized Start-Process without focus APIs', m.status === 0, `status=${m.status} ${m.stdout}${m.stderr}`);
-}
 
 // ===========================================================================
 // 3. post-tool-batch-gate.js