@walwal-harness/cli 7.1.38 → 7.1.40

package/HR-Resource/cto/SKILL.md

@@ -30,6 +30,14 @@ Before engineering work, read `.harness/conventions/shared.md`, `.harness/conven
 
 Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
 
+## Browser Automation Briefing
+
+Every CTO worker brief that may use Playwright, browser automation, browser-based inspection, E2E, or visual verification must explicitly include this requirement:
+
+> Run Playwright/browser automation with a visible browser. Set `headless: false` in launch/config code, use headed test mode (`--headed`, `PWDEBUG=1`, or equivalent), prefer `channel: 'chrome'` when available, and do not use headless mode unless the Owner has explicitly approved an exception in this mission.
+
+CTO must not accept worker plans or reports that omit this requirement when browser automation is in scope.
+
 ## Hard Rules
 
 CTO must not directly write code, create build scripts, choose detailed implementation content, run technical QA as the evaluator, or produce final implementation artifacts. CTO may only design boundaries, brief workers, coordinate ports/config, review worker outputs, and record accepted decisions with worker names and report paths.

package/HR-Resource/ops/SKILL.md

@@ -50,6 +50,16 @@ OPS must actively watch the runtime while CQO evaluator workers test the product
 - CQO cannot issue PASS for a runnable product while OPS reports an open INCIDENT, missing runtime mapping, missing logs required by the mission, or an unmonitored service that is part of the tested scenario.
 - OPS does not wait for the Owner to notice defects. Owner acceptance starts only after CQO evidence and OPS runtime evidence are both clean, or after CEO explicitly reports remaining operational risk.
 
+## Dev-Mode Prompt Inspector
+
+When OPS builds or runs a React/Next.js UI in development mode, and screen-level discussion would benefit from selecting visible UI elements and mapping intended REST/API behavior, OPS must use the installed `harness-ops-prompt-inspector` skill.
+
+- Use Prompt Inspector only for development builds or verification environments. Do not inject it into production builds or production service environments.
+- Install it from the project-local skill path under `.claude/skills/harness-ops-prompt-inspector/` or `.codex/skills/harness-ops-prompt-inspector/`; do not download it at mission runtime.
+- Run its installer against the target app path before or during the dev-mode run so the toolbar is available in the browser for UI/API binding notes.
+- Record the install result, target app path, dev server URL, and generated API discovery evidence in OPS environment evidence.
+- If the project is not React/Next.js or the build is not development mode, report Prompt Inspector as not applicable instead of forcing installation.
+
 ## Post-Launch Watch
 
 After service launch, OPS continues the same monitoring duty against `runtime.production.services[]`.
@@ -84,6 +94,14 @@ After service launch, OPS continues the same monitoring duty against `runtime.pr
 
 Before launching any fresh worker session, update `.harness/progress.json` with `scripts/harness-progress-set.sh` so dashboards can show the worker as active. Record the worker name, owning CXX, report path, and `status:"running"` under `company_state.workers`, increment `company_state.active_workers`, and set `conductor.current_action` to `spawn:{worker-name}`. After the worker report is accepted, update that worker to `status:"complete"` and decrement `active_workers`. Do not leave `active_workers:0` while a worker session is running.
 
+## Browser Automation Briefing
+
+Every OPS worker brief that may use Playwright, browser automation, browser-based monitoring, E2E, or visual/runtime verification must explicitly include this requirement:
+
+> Run Playwright/browser automation with a visible browser. Set `headless: false` in launch/config code, use headed test mode (`--headed`, `PWDEBUG=1`, or equivalent), prefer `channel: 'chrome'` when available, and do not use headless mode unless the Owner has explicitly approved an exception in this mission.
+
+OPS must not accept worker plans or reports that omit this requirement when browser automation is in scope.
+
 ## Required Output Sections
 
 1. Worker Task Briefs — monitoring/recovery task, capability needed, selected worker or hiring request, acceptance criteria.

package/HR-Resource/ops-prompt-inspector/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: harness-ops-prompt-inspector
+description: "OPS-only dev-mode visual API binding for React/Next.js UI elements and REST endpoints."
+permissionMode: bypassPermissions
+---
+
+# OPS Prompt Inspector
+
+OPS-only visual tool for binding UI elements to REST APIs in React/Next.js projects during development builds.
+
+Use this skill only when OPS is responsible for a dev-mode build/run or verification environment where screen-level communication would be improved by an on-page inspector. Do not install it into production builds.
+
+## Quick Setup
+
+**Recommended: Use the installation agent for seamless setup:**
+
+```
+Task(
+  subagent_type="harness-ops-prompt-inspector:installer",
+  prompt="Install PromptInspector to <project_path>",
+  permissionMode="bypassPermissions"
+)
+```
+
+**Or run manually:**
+
+```bash
+bash scripts/install.sh <project_path>
+```
+
+This automatically:
+1. Detects project type (Next.js App/Pages Router)
+2. Copies component to `components/PromptInspector.tsx`
+3. Injects into root layout (dev mode only)
+4. Discovers all APIs in the project
+
+## Workflow
+
+```
+1. Setup     → Run setup.py (auto-injects component)
+2. Discover  → Run discover_apis.py (find all APIs)
+3. Bind      → Select elements, configure API connections
+4. Export    → Copy markdown spec for implementation
+```
+
+## Step 1: Discover APIs
+
+```bash
+python3 scripts/discover_apis.py <project_path>
+```
+
+Finds:
+- Backend: Express, FastAPI, NestJS, Next.js API routes
+- Frontend: axios, fetch, ky, SWR, React Query
+
+## Step 2: Visual Binding
+
+After setup, toolbar appears at bottom-right in dev mode:
+
+1. **Select Element** → Click any UI element
+2. **Choose Action** → Comment Only / Connect API
+3. **Configure** (for API):
+   - Select API from discovered list
+   - Trigger: Mount, PageLoad, Click, Submit, Blur, Change
+   - OnSuccess: toast/popup/redirect + message
+   - OnError: Multiple cases with optional error codes
+4. **Export** → Copies markdown specification
+
+## Output Format
+
+```markdown
+# Route: /users
+
+## 1. POST /api/users
+- Selector: `button.submit-btn`
+- Trigger: onClick
+- OnSuccess: toast ("User created")
+- OnError #1: [ERR_DUPLICATE] toast ("Already exists")
+- OnError #2: toast ("Unknown error")
+
+## 2. Comment
+- Selector: `#header`
+- Comment: Needs redesign
+```
+
+## Manual Setup (if auto fails)
+
+1. Copy `assets/PromptInspector.tsx` to project's `components/`
+
+2. Add to root layout:
+```tsx
+import { PromptInspector } from '@/components/PromptInspector';
+
+// Inside layout, before </body>:
+{process.env.NODE_ENV === 'development' && <PromptInspector />}
+```
+
+## Handler Templates
+
+See [references/handler-templates.md](references/handler-templates.md) for code generation patterns.

package/HR-Resource/ops-prompt-inspector/agents/installation-agent.json

@@ -0,0 +1,7 @@
+{
+  "name": "prompt-inspector-installer",
+  "description": "Installs PromptInspector component with auto-update check. Handles file copying and layout injection without requiring individual permission prompts.",
+  "permissionMode": "bypassPermissions",
+  "tools": ["Read", "Write", "Edit", "Bash", "Glob"],
+  "prompt": "You are the Prompt Inspector installation agent. Your job is to:\n\n1. Run the setup script: `python3 scripts/setup.py <project_path> --force`\n2. Run the API discovery: `python3 scripts/discover_apis.py <project_path>`\n3. Report installation results to the user\n\nExecute these steps without asking for additional permissions."
+}