create-harness-vibe-coding 0.7.2 → 0.8.1

package/templates/optional/catalog.json

@@ -1,43 +1,77 @@
-{
-  "skills": [
-    {
+{
+  "skills": [
+    {
       "id": "browser-e2e",
       "title": "Browser E2E",
       "description": "Mandatory real-browser smoke workflow using Playwright, Chrome DevTools/CDP, or documented manual evidence.",
       "files": ["skills/browser-e2e"],
       "tags": ["e2e", "browser", "playwright", "cdp"]
-    },
+    },
+    {
+      "id": "ui-ux-review",
+      "title": "UI/UX Review",
+      "description": "Screenshot-driven responsive, accessibility, and visual polish review workflow.",
+      "files": ["skills/ui-ux-review"],
+      "tags": ["ui", "ux", "accessibility", "review"]
+    },
+    {
+      "id": "github-pr-review",
+      "title": "GitHub PR Review",
+      "description": "GitHub CLI based PR diff, checks, review findings, and CI evidence workflow.",
+      "files": ["skills/github-pr-review"],
+      "tags": ["github", "pr", "review", "ci"]
+    },
+    {
+      "id": "python-backend",
+      "title": "Python Backend",
+      "description": "Python backend workflow for FastAPI or similar APIs with unittest or pytest verification.",
+      "files": ["skills/python-backend"],
+      "tags": ["python", "fastapi", "unittest", "pytest", "api"]
+    },
+    {
+      "id": "ts-react-frontend",
+      "title": "TypeScript React Frontend",
+      "description": "TypeScript React workflow for typecheck, component tests, builds, and browser smoke.",
+      "files": ["skills/ts-react-frontend"],
+      "tags": ["typescript", "react", "vite", "frontend"]
+    }
+  ],
+  "presets": {
+    "web-app": ["ts-react-frontend", "browser-e2e", "ui-ux-review"],
+    "fullstack": ["ts-react-frontend", "python-backend", "browser-e2e", "github-pr-review"]
+  },
+  "externalRecommendations": [
     {
-      "id": "ui-ux-review",
-      "title": "UI/UX Review",
-      "description": "Screenshot-driven responsive, accessibility, and visual polish review workflow.",
-      "files": ["skills/ui-ux-review"],
-      "tags": ["ui", "ux", "accessibility", "review"]
+      "id": "superpowers",
+      "title": "Superpowers",
+      "description": "Community skill registry for agent workflows and reusable coding skills.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/obra/Superpowers",
+      "tags": ["skills", "community", "subagents"]
     },
     {
-      "id": "github-pr-review",
-      "title": "GitHub PR Review",
-      "description": "GitHub CLI based PR diff, checks, review findings, and CI evidence workflow.",
-      "files": ["skills/github-pr-review"],
-      "tags": ["github", "pr", "review", "ci"]
+      "id": "caveman",
+      "title": "Caveman",
+      "description": "External terse-agent capability to evaluate for low-token behavior and memory compression.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/JuliusBrussee/caveman",
+      "tags": ["workflow", "implementation", "style"]
     },
     {
-      "id": "python-backend",
-      "title": "Python Backend",
-      "description": "Python backend workflow for FastAPI or similar APIs with unittest or pytest verification.",
-      "files": ["skills/python-backend"],
-      "tags": ["python", "fastapi", "unittest", "pytest", "api"]
+      "id": "agent-research",
+      "title": "Agent Research",
+      "description": "External research-agent capability for broader product, dependency, and ecosystem investigation.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/lingzhi227/agent-research-skills",
+      "tags": ["research", "agents", "discovery"]
     },
     {
-      "id": "ts-react-frontend",
-      "title": "TypeScript React Frontend",
-      "description": "TypeScript React workflow for typecheck, component tests, builds, and browser smoke.",
-      "files": ["skills/ts-react-frontend"],
-      "tags": ["typescript", "react", "vite", "frontend"]
+      "id": "codegraph",
+      "title": "Code Graph",
+      "description": "External code graph or repository map capability for dependency and architecture exploration.",
+      "installMode": "recommend-only",
+      "url": "https://github.com/colbymchenry/codegraph",
+      "tags": ["code graph", "architecture", "analysis"]
     }
-  ],
-  "presets": {
-    "web-app": ["ts-react-frontend", "browser-e2e", "ui-ux-review"],
-    "fullstack": ["ts-react-frontend", "python-backend", "browser-e2e", "github-pr-review"]
-  }
+  ]
 }

package/templates/optional/skills/browser-e2e/.claude/skills/wf-browser/SKILL.md

@@ -1,194 +1,194 @@
----
-name: wf-browser
-description: AI-driven browser automation for E2E testing, web scraping, form filling, and UI verification. Powered by Browser Use (89.1% WebVoyager benchmark). Use for /wf-browser, browser testing, web automation, page interaction, form filling, screenshot verification, or any task requiring real browser control. Dual mode: CLI (fast iteration, no LLM needed) + Python Agent API (complex multi-step workflows with AI reasoning).
----
-
-# WF Browser — AI Browser Automation
-
-Load:
-
-- `Harness/workflows/browser-e2e.md`
-- Official `browser-use` skill at `~/.claude/skills/browser-use/SKILL.md` (auto-installed if missing)
-- `Harness/PROGRESS.md` when work is active
-
-## Modes
-
-Choose based on task complexity:
-
-### Mode 1: CLI (fast iteration, ~50ms per call)
-
-Best for: single-page checks, quick screenshots, form fills, element inspection. No LLM needed — Claude Code reasons and issues CLI commands.
-
-```bash
-browser-use --headed open https://example.com   # Open page (headed = visible browser)
-browser-use state                                # Get page title, text, interactive elements with indices
-browser-use screenshot evidence.png              # Capture screenshot as evidence
-browser-use click 5                              # Click element by index from state output
-browser-use input 3 "user@example.com"           # Fill input field by index
-browser-use eval "document.title"                # Run JavaScript in page
-browser-use close                                # Close browser when done
-```
-
-Daemon keeps the browser open between commands — no cold-start per action.
-
-### Mode 2: Python Agent API (multi-step AI reasoning)
-
-Best for: complex multi-page workflows, dynamic navigation, data extraction across pages. Needs LLM API key.
-
-```python
-from browser_use.beta import Agent, BrowserProfile
-from browser_use.llm import ChatAnthropic
-
-agent = Agent(
-    task="Go to github.com, search for 'browser-use', click the first result, and report the star count",
-    llm=ChatAnthropic(model="claude-haiku-4-5-20251001"),
-    browser_profile=BrowserProfile(headless=False),
-)
-history = await agent.run()
-print(history.final_result())
-```
-
-## Environment Setup
-
-Run once per machine:
-
-```bash
-# 1. Install browser-use with CLI extras
-pip install "browser-use[cli]"
-
-# 2. Install Chromium browser
-browser-use install
-
-# 3. Verify installation
-browser-use doctor
-
-# 4. (Optional) Set LLM API key for Agent mode
-# Create .env file with: ANTHROPIC_API_KEY=sk-ant-...
-# Or: OPENAI_API_KEY=sk-...
-# Or: BROWSER_USE_API_KEY=bu-...
-```
-
-### Windows GBK Encoding Fix
-
-If you see `UnicodeEncodeError: 'gbk' codec can't encode character`, the install is auto-patched. If not, set env var before commands:
-
-```bash
-set PYTHONIOENCODING=utf-8
-```
-
-### Windows Daemon Patches
-
-Browser Use v0.13.1 has two known issues on Windows that are auto-patched on install. If `browser-use open` fails with "Failed to start daemon" or socket timeout, re-apply:
-
-```bash
-python -c "
-import browser_use.skill_cli.main as m
-p = m.__file__
-c = open(p, encoding='utf-8').read()
-# Patch 1: auto-clean stale state on dead PID
-c = c.replace(
-    'probe = _probe_session(session)\n\n\t# Socket reachable',
-    'probe = _probe_session(session)\n\n\t# Auto-clean stale state\n\tif not probe.socket_reachable and not probe.pid_alive and probe.phase:\n\t\t_clean_session_files(session)\n\t\tprobe = _probe_session(session)\n\n\t# Socket reachable'
-)
-# Patch 2: auto-recover from stale session instead of erroring
-c = c.replace(
-    \"f'Error: Session {session!r} is alive (phase={probe.phase}) but socket unreachable.\",\"
-    \"f'Warning: Session {session!r} has stale state (phase={probe.phase}), auto-cleaning...\",\"
-)
-c = c.replace(
-    \"sys.exit(1)\n\n\t\telif probe.phase == 'shutting_down'\",
-    \"_terminate_pid(probe.pid)\n\t\t\t_clean_session_files(session)\n\n\t\telif probe.phase == 'shutting_down'\"
-)
-# Patch 3: extend daemon startup timeout (15s -> 30s)
-c = c.replace('deadline = time.time() + 15', 'deadline = time.time() + 30')
-open(p, 'w', encoding='utf-8').write(c)
-print('Patches applied')
-"
-```
-
-### Requirements
-
-| Requirement | Version | Check |
-|-------------|---------|-------|
-| Python | >= 3.11 | `python --version` |
-| pip | any | `pip --version` |
-| Chromium | auto-installed | `browser-use doctor` |
-| LLM API key | for Agent mode only | check `.env` |
-
-## Common Patterns
-
-### Login Persistence
-
-```bash
-# Use real Chrome profile (preserves cookies/logins)
-browser-use --profile "Default" open https://app.target.com
-# Or connect to running Chrome with remote debugging
-browser-use connect
-```
-
-### E2E Test Flow
-
-```bash
-browser-use --headed open https://yourapp.local
-browser-use state                          # Verify page loaded
-browser-use screenshot step1-landing.png   # Evidence
-browser-use input 3 "test@email.com"       # Fill email
-browser-use input 5 "password123"          # Fill password
-browser-use click 8                        # Click login button
-browser-use wait text "Dashboard"           # Wait for navigation text
-browser-use state                          # Verify logged in
-browser-use screenshot step2-dashboard.png # Evidence
-browser-use close
-```
-
-### Console & Network Log Capture
-
-```bash
-browser-use eval "console.log('checkpoint');"   # Inject log marker
-browser-use eval "document.title"                # Read page state via JS
-browser-use get text 5                           # Get text of element index 5
-browser-use get value 3                          # Get value of input element index 3
-# For full console/network: use Python Agent mode with Playwright's page.on('console') and page.on('request')
-```
-
-### Error Recovery
-
-```bash
-# If daemon crashes or gets stuck:
-browser-use close          # Clean shutdown
-# Then restart:
-browser-use open <url>     # Fresh daemon starts automatically
-```
-
-## Verification Contract
-
-Every browser task must produce:
-
-1. **State evidence**: `browser-use state` output or screenshot
-2. **Action log**: sequence of commands issued
-3. **Result assertion**: explicit before/after state comparison
-
-No browser/UI claim without real-browser evidence.
-
-## Architecture Note
-
-Browser Use wraps Playwright with AI reasoning. The daemon keeps Chromium running between CLI commands (~50ms latency). The Agent mode adds an LLM observation→decision→action loop on top. This replaces fragile CSS-selector scripts with semantic element targeting via accessibility tree snapshots.
-
-Benchmarks: 89.1% WebVoyager (SOTA), 78k+ GitHub stars, MIT license.
-
-## Security
-
-- **Never log or screenshot credentials** — redact password fields, API keys, tokens before capturing evidence
-- **Chrome profiles contain sensitive data** — only use `--profile` with explicit user approval; never share profile data
-- **Screenshots may capture PII** — review before saving to task evidence directory
-- **Scraping targets need approval** — confirm the target site's ToS allow automated access before scraping
-- **`browser-use input` commands with passwords** — use placeholder values in documentation; never hardcode real credentials
-- **Agent mode sandbox** — run Agent API with `allowed_domains` restriction when possible
-
-## Return
-
-- CLI commands issued and their output
-- screenshot paths
-- agent history (if Agent mode used)
-- verification pass/fail with evidence
-- remaining risks (flaky selectors, auth issues, CAPTCHAs)
+---
+name: wf-browser
+description: AI-driven browser automation for E2E testing, web scraping, form filling, and UI verification. Powered by Browser Use (89.1% WebVoyager benchmark). Use for /wf-browser, browser testing, web automation, page interaction, form filling, screenshot verification, or any task requiring real browser control. Dual mode: CLI (fast iteration, no LLM needed) + Python Agent API (complex multi-step workflows with AI reasoning).
+---
+
+# WF Browser — AI Browser Automation
+
+Load:
+
+- `Harness/workflows/browser-e2e.md`
+- Official `browser-use` skill at `~/.claude/skills/browser-use/SKILL.md` (auto-installed if missing)
+- `Harness/PROGRESS.md` when work is active
+
+## Modes
+
+Choose based on task complexity:
+
+### Mode 1: CLI (fast iteration, ~50ms per call)
+
+Best for: single-page checks, quick screenshots, form fills, element inspection. No LLM needed — Claude Code reasons and issues CLI commands.
+
+```bash
+browser-use --headed open https://example.com   # Open page (headed = visible browser)
+browser-use state                                # Get page title, text, interactive elements with indices
+browser-use screenshot evidence.png              # Capture screenshot as evidence
+browser-use click 5                              # Click element by index from state output
+browser-use input 3 "user@example.com"           # Fill input field by index
+browser-use eval "document.title"                # Run JavaScript in page
+browser-use close                                # Close browser when done
+```
+
+Daemon keeps the browser open between commands — no cold-start per action.
+
+### Mode 2: Python Agent API (multi-step AI reasoning)
+
+Best for: complex multi-page workflows, dynamic navigation, data extraction across pages. Needs LLM API key.
+
+```python
+from browser_use.beta import Agent, BrowserProfile
+from browser_use.llm import ChatAnthropic
+
+agent = Agent(
+    task="Go to github.com, search for 'browser-use', click the first result, and report the star count",
+    llm=ChatAnthropic(model="claude-haiku-4-5-20251001"),
+    browser_profile=BrowserProfile(headless=False),
+)
+history = await agent.run()
+print(history.final_result())
+```
+
+## Environment Setup
+
+Run once per machine:
+
+```bash
+# 1. Install browser-use with CLI extras
+pip install "browser-use[cli]"
+
+# 2. Install Chromium browser
+browser-use install
+
+# 3. Verify installation
+browser-use doctor
+
+# 4. (Optional) Set LLM API key for Agent mode
+# Create .env file with: ANTHROPIC_API_KEY=sk-ant-...
+# Or: OPENAI_API_KEY=sk-...
+# Or: BROWSER_USE_API_KEY=bu-...
+```
+
+### Windows GBK Encoding Fix
+
+If you see `UnicodeEncodeError: 'gbk' codec can't encode character`, the install is auto-patched. If not, set env var before commands:
+
+```bash
+set PYTHONIOENCODING=utf-8
+```
+
+### Windows Daemon Patches
+
+Browser Use v0.13.1 has two known issues on Windows that are auto-patched on install. If `browser-use open` fails with "Failed to start daemon" or socket timeout, re-apply:
+
+```bash
+python -c "
+import browser_use.skill_cli.main as m
+p = m.__file__
+c = open(p, encoding='utf-8').read()
+# Patch 1: auto-clean stale state on dead PID
+c = c.replace(
+    'probe = _probe_session(session)\n\n\t# Socket reachable',
+    'probe = _probe_session(session)\n\n\t# Auto-clean stale state\n\tif not probe.socket_reachable and not probe.pid_alive and probe.phase:\n\t\t_clean_session_files(session)\n\t\tprobe = _probe_session(session)\n\n\t# Socket reachable'
+)
+# Patch 2: auto-recover from stale session instead of erroring
+c = c.replace(
+    \"f'Error: Session {session!r} is alive (phase={probe.phase}) but socket unreachable.\",\"
+    \"f'Warning: Session {session!r} has stale state (phase={probe.phase}), auto-cleaning...\",\"
+)
+c = c.replace(
+    \"sys.exit(1)\n\n\t\telif probe.phase == 'shutting_down'\",
+    \"_terminate_pid(probe.pid)\n\t\t\t_clean_session_files(session)\n\n\t\telif probe.phase == 'shutting_down'\"
+)
+# Patch 3: extend daemon startup timeout (15s -> 30s)
+c = c.replace('deadline = time.time() + 15', 'deadline = time.time() + 30')
+open(p, 'w', encoding='utf-8').write(c)
+print('Patches applied')
+"
+```
+
+### Requirements
+
+| Requirement | Version | Check |
+|-------------|---------|-------|
+| Python | >= 3.11 | `python --version` |
+| pip | any | `pip --version` |
+| Chromium | auto-installed | `browser-use doctor` |
+| LLM API key | for Agent mode only | check `.env` |
+
+## Common Patterns
+
+### Login Persistence
+
+```bash
+# Use real Chrome profile (preserves cookies/logins)
+browser-use --profile "Default" open https://app.target.com
+# Or connect to running Chrome with remote debugging
+browser-use connect
+```
+
+### E2E Test Flow
+
+```bash
+browser-use --headed open https://yourapp.local
+browser-use state                          # Verify page loaded
+browser-use screenshot step1-landing.png   # Evidence
+browser-use input 3 "test@email.com"       # Fill email
+browser-use input 5 "password123"          # Fill password
+browser-use click 8                        # Click login button
+browser-use wait text "Dashboard"           # Wait for navigation text
+browser-use state                          # Verify logged in
+browser-use screenshot step2-dashboard.png # Evidence
+browser-use close
+```
+
+### Console & Network Log Capture
+
+```bash
+browser-use eval "console.log('checkpoint');"   # Inject log marker
+browser-use eval "document.title"                # Read page state via JS
+browser-use get text 5                           # Get text of element index 5
+browser-use get value 3                          # Get value of input element index 3
+# For full console/network: use Python Agent mode with Playwright's page.on('console') and page.on('request')
+```
+
+### Error Recovery
+
+```bash
+# If daemon crashes or gets stuck:
+browser-use close          # Clean shutdown
+# Then restart:
+browser-use open <url>     # Fresh daemon starts automatically
+```
+
+## Verification Contract
+
+Every browser task must produce:
+
+1. **State evidence**: `browser-use state` output or screenshot
+2. **Action log**: sequence of commands issued
+3. **Result assertion**: explicit before/after state comparison
+
+No browser/UI claim without real-browser evidence.
+
+## Architecture Note
+
+Browser Use wraps Playwright with AI reasoning. The daemon keeps Chromium running between CLI commands (~50ms latency). The Agent mode adds an LLM observation→decision→action loop on top. This replaces fragile CSS-selector scripts with semantic element targeting via accessibility tree snapshots.
+
+Benchmarks: 89.1% WebVoyager (SOTA), 78k+ GitHub stars, MIT license.
+
+## Security
+
+- **Never log or screenshot credentials** — redact password fields, API keys, tokens before capturing evidence
+- **Chrome profiles contain sensitive data** — only use `--profile` with explicit user approval; never share profile data
+- **Screenshots may capture PII** — review before saving to task evidence directory
+- **Scraping targets need approval** — confirm the target site's ToS allow automated access before scraping
+- **`browser-use input` commands with passwords** — use placeholder values in documentation; never hardcode real credentials
+- **Agent mode sandbox** — run Agent API with `allowed_domains` restriction when possible
+
+## Return
+
+- CLI commands issued and their output
+- screenshot paths
+- agent history (if Agent mode used)
+- verification pass/fail with evidence
+- remaining risks (flaky selectors, auth issues, CAPTCHAs)

package/templates/optional/skills/browser-e2e/{docs → Harness}/workflows/browser-e2e.md

@@ -1,75 +1,75 @@
-# Browser E2E Workflow
-
-Optional workflow for browser-visible testing and automation. Installed when `browser-use` CLI is available.
-
-## When Active
-
-This workflow is active when:
-1. `browser-use` CLI is installed and `browser-use doctor` passes
-2. `Harness/workflows/browser-e2e.md` exists (this file)
-3. A task explicitly references `/wf-browser` or browser E2E testing
-
-## Contract
-
-Browser evidence in this project follows the contract:
-
-1. **Every browser claim needs real-browser evidence** — screenshot, state snapshot, or console output
-2. **CLI mode is preferred for deterministic steps** — use `browser-use open/state/click/screenshot` for predictable flows
-3. **Agent mode is for dynamic exploration** — use Browser Use Agent API when the page structure is unknown or changing
-4. **Evidence goes to the task directory** — `Harness/tasks/<task-id>/evidence/*.png`
-5. **Stable UI selector contract** — Stable accessible labels/roles and stable test hooks such as `data-testid` are required for critical UI controls and states: inputs, buttons, filters, rows, empty/error/loading states.
-
-## Chrome DevTools / CDP / MCP Checklist
-
-- [ ] record the URL and port
-- [ ] Verify available CDP, MCP, browser automation, or manual tooling
-- [ ] Check not just HTTP 200
-- [ ] Verify no runtime exceptions, console errors, and failed network requests
-- [ ] Confirm stable accessible labels/roles or `data-testid` on interactive elements
-- [ ] Test critical flow end-to-end
-- [ ] Capture screenshot, trace, video, or result artifact paths
-- [ ] Clean up any dev server or browser processes
-
-## Quick Install
-
-```bash
-# One-time setup
-pip install "browser-use[cli]"
-browser-use install
-browser-use doctor
-
-# Windows: if you see GBK encoding errors, set:
-set PYTHONIOENCODING=utf-8
-
-# Verify
-browser-use open https://example.com
-browser-use state
-browser-use screenshot test.png
-browser-use close
-```
-
-## Fallback
-
-If `browser-use` is not installed, fall back to:
-
-1. Playwright/Puppeteer MCP server (if configured)
-2. Chrome DevTools Protocol (CDP) manual inspection
-3. `Harness/WF.md#Browser And API Evidence` manual check contract
-
-## Integration Points
-
-- **WF mode**: when browser-visible changes are made, follow the evidence contract in `Harness/WF.md#Browser And API Evidence`
-- **wf-browser**: the `/wf-browser` slash command loads this workflow + the skill via `.claude/commands/wf-browser.md`
-- **MEMORY.md**: registered as optional workflow skill
-- **README.md**: routing table row "Browser E2E testing or automation" → browser-e2e
-
-## File Locations
-
-| File | Purpose |
-|------|---------|
-| `.claude/skills/wf-browser/SKILL.md` | Skill definition |
-| `.claude/commands/wf-browser.md` | Slash command bridge |
-| `Harness/workflows/browser-e2e.md` | This file — workflow contract and install guide |
-| `~/.claude/skills/browser-use/SKILL.md` | Official Browser Use skill (user-level, auto-downloaded) |
-| `pip show browser-use \| findstr Location` | Python package install location (run to find) |
-| `~/.browser-use/` | Daemon state and browser profiles |
+# Browser E2E Workflow
+
+Optional workflow for browser-visible testing and automation. Installed when `browser-use` CLI is available.
+
+## When Active
+
+This workflow is active when:
+1. `browser-use` CLI is installed and `browser-use doctor` passes
+2. `Harness/workflows/browser-e2e.md` exists (this file)
+3. A task explicitly references `/wf-browser`, `$wf-browser`, or browser E2E testing
+
+## Contract
+
+Browser evidence in this project follows the contract:
+
+1. **Every browser claim needs real-browser evidence** — screenshot, state snapshot, or console output
+2. **CLI mode is preferred for deterministic steps** — use `browser-use open/state/click/screenshot` for predictable flows
+3. **Agent mode is for dynamic exploration** — use Browser Use Agent API when the page structure is unknown or changing
+4. **Evidence goes to the task directory** — `Harness/tasks/<task-id>/evidence/*.png`
+5. **Stable UI selector contract** — Stable accessible labels/roles and stable test hooks such as `data-testid` are required for critical UI controls and states: inputs, buttons, filters, rows, empty/error/loading states.
+
+## Chrome DevTools / CDP / MCP Checklist
+
+- [ ] record the URL and port
+- [ ] Verify available CDP, MCP, browser automation, or manual tooling
+- [ ] Check not just HTTP 200
+- [ ] Verify no runtime exceptions, console errors, and failed network requests
+- [ ] Confirm stable accessible labels/roles or `data-testid` on interactive elements
+- [ ] Test critical flow end-to-end
+- [ ] Capture screenshot, trace, video, or result artifact paths
+- [ ] Clean up any dev server or browser processes
+
+## Quick Install
+
+```bash
+# One-time setup
+pip install "browser-use[cli]"
+browser-use install
+browser-use doctor
+
+# Windows: if you see GBK encoding errors, set:
+set PYTHONIOENCODING=utf-8
+
+# Verify
+browser-use open https://example.com
+browser-use state
+browser-use screenshot test.png
+browser-use close
+```
+
+## Fallback
+
+If `browser-use` is not installed, fall back to:
+
+1. Playwright/Puppeteer MCP server (if configured)
+2. Chrome DevTools Protocol (CDP) manual inspection
+3. `Harness/WF.md#Browser And API Evidence` manual check contract
+
+## Integration Points
+
+- **WF mode**: when browser-visible changes are made, follow the evidence contract in `Harness/WF.md#Browser And API Evidence`
+- **wf-browser**: Claude Code uses `.claude/skills/wf-browser/SKILL.md`; Codex uses `.agents/skills/wf-browser/SKILL.md`. Both load this workflow.
+- **MEMORY.md**: registered as optional workflow skill
+- **README.md**: routing table row "Browser E2E testing or automation" → browser-e2e
+
+## File Locations
+
+| File | Purpose |
+|------|---------|
+| `.claude/skills/wf-browser/SKILL.md` | Claude Code skill adapter |
+| `.agents/skills/wf-browser/SKILL.md` | Codex repo skill adapter |
+| `Harness/workflows/browser-e2e.md` | This file — workflow contract and install guide |
+| `~/.claude/skills/browser-use/SKILL.md` | Official Browser Use skill (user-level, auto-downloaded) |
+| `pip show browser-use \| findstr Location` | Python package install location (run to find) |
+| `~/.browser-use/` | Daemon state and browser profiles |