agentic-qe 3.9.7 → 3.9.9

package/.claude/skills/qe-browser/SKILL.md

@@ -0,0 +1,409 @@
+---
+name: "qe-browser"
+description: "Browser automation for QE agents using Vibium (WebDriver BiDi) with assertions, batch execution, visual diff, prompt-injection scanning, and semantic intents. Use when any QE skill needs to drive a real browser — visual testing, accessibility audits, E2E flow verification, pentest validation, or exploratory testing."
+trust_tier: 3
+validation:
+  schema_path: schemas/output.json
+  validator_path: scripts/validate-config.json
+  eval_path: evals/qe-browser.yaml
+---
+
+# QE Browser
+
+Thin AQE-owned wrapper around [Vibium](https://github.com/VibiumDev/vibium) that adds QE-specific primitives: typed assertions, batch execution, visual-diff against baselines, prompt-injection scanning, and semantic intent scoring.
+
+**Engine:** Vibium — single ~10MB Go binary, built on WebDriver BiDi (W3C standard), Apache-2.0 licensed, published on npm/PyPI/Maven Central. Auto-launches a background daemon and auto-downloads Chrome for Testing on first use.
+
+**Why Vibium, not Playwright?**
+- 10MB binary vs ~300MB Playwright install
+- WebDriver BiDi standard (not CDP) — future-proof for Firefox/Safari
+- `--json` mode on every command (matches AQE structured-output rule)
+- Built-in MCP server: `npx -y vibium mcp`
+- First-class semantic locators: `find text|label|placeholder|testid|role|xpath|alt|title`
+
+## Platform support (verified 2026-04-09 against Vibium v26.3.18)
+
+| Platform | `npm install -g vibium` | `vibium go <url>` | smoke-test.sh |
+|---|---|---|---|
+| macOS arm64 (Apple Silicon native) | ✅ | ✅ | ✅ |
+| macOS x64 (Intel) | ✅ | ✅ | ✅ |
+| Linux x86_64 | ✅ | ✅ | ✅ |
+| Windows x64 | ✅ | ✅ | not yet tested |
+| **Linux ARM64 (aarch64)** | ✅ binary itself | ⚠️ **Workaround required** | ✅ after workaround |
+
+### Linux ARM64 workaround
+
+Google Chrome for Testing does not publish a `linux-arm64` build. Vibium falls back to `chrome-linux64` (x86_64) on aarch64 hosts, which fails under Rosetta with `failed to open elf at /lib64/ld-linux-x86-64.so.2`. To run qe-browser on a Linux ARM64 codespace or container:
+
+```bash
+# 1. Install Vibium normally — the vibium binary itself IS native ARM64
+npm install -g vibium
+
+# 2. Install Debian's native ARM64 chromium + chromedriver
+sudo apt-get update
+sudo apt-get install -y chromium chromium-driver
+
+# 3. Symlink Vibium's broken cached binaries to the native system ones.
+#    Run after `vibium install` (auto-runs on first `vibium go`).
+for dir in ~/.cache/vibium/chrome-for-testing/*/; do
+  # Newer Vibium layout (v26.3.x): chromedriver and chrome at the root
+  if [ -e "$dir/chromedriver" ]; then
+    rm -f "$dir/chromedriver" "$dir/chrome"
+    ln -s /usr/bin/chromedriver "$dir/chromedriver"
+    ln -s /usr/bin/chromium     "$dir/chrome"
+  fi
+  # Older Vibium layout: chromedriver-linux64/ and chrome-linux64/ subdirs
+  if [ -e "$dir/chromedriver-linux64/chromedriver" ]; then
+    rm -f "$dir/chromedriver-linux64/chromedriver" "$dir/chrome-linux64/chrome"
+    ln -s /usr/bin/chromedriver "$dir/chromedriver-linux64/chromedriver"
+    ln -s /usr/bin/chromium     "$dir/chrome-linux64/chrome"
+  fi
+done
+
+# 4. Verify
+vibium --headless go https://httpbin.org/html
+vibium --headless title  # → "Herman Melville - Moby-Dick"
+```
+
+This workaround is verified working on Debian bookworm aarch64 with chromium 146.0.7680.177-1~deb12u1. Track upstream — when Vibium adds a `--browser-path` flag or Google ships `linux-arm64` Chrome for Testing, this section becomes obsolete.
+
+## Headless mode
+
+Helper scripts (`assert.js`, `batch.js`, `visual-diff.js`, `check-injection.js`, `intent-score.js`) automatically inject `--headless` into every `vibium` invocation because the qe-browser skill is designed for QE/CI use cases where there's no display server. **Vibium itself defaults to "visible by default"** — running `vibium go` on a headless container without `--headless` fails with `Missing X server or $DISPLAY`.
+
+Opt out for interactive debugging:
+```bash
+QE_BROWSER_HEADED=1 node .claude/skills/qe-browser/scripts/assert.js --checks '...'
+```
+
+When you call `vibium` directly (not through a helper), pass `--headless` yourself if you're in a container:
+```bash
+vibium --headless go https://example.com
+vibium --headless title
+```
+
+## Activation
+
+- When a QE skill needs to navigate, read, interact with, or capture a web page
+- When running visual regression tests against stored baselines
+- When asserting page state (URL, text visibility, console errors, network failures)
+- When validating exploitability of security findings (pentest)
+- When scanning untrusted pages for prompt injection
+- When running batch automation with explicit pass/fail gates
+
+## Core Workflow
+
+Every browser-driven QE task follows the same shape:
+
+1. **Navigate** — `vibium go <url>`
+2. **Map** — `vibium map` to get element refs (`@e1`, `@e2`, …)
+3. **Interact** — `vibium click @e1`, `vibium fill @e2 "text"`
+4. **Verify** — use this skill's `assert.js` to run typed checks, OR use `vibium diff map` to see what changed
+5. **Re-map** if DOM changed
+
+```bash
+# Typical login flow verification
+vibium go https://app.example.com/login
+vibium map --json > /tmp/refs.json
+vibium fill @e1 "$USERNAME"
+vibium fill @e2 "$PASSWORD"
+vibium click @e3
+vibium wait url "/dashboard"
+node .claude/skills/qe-browser/scripts/assert.js --checks '[
+  {"kind": "url_contains", "text": "/dashboard"},
+  {"kind": "no_console_errors"},
+  {"kind": "no_failed_requests"}
+]'
+```
+
+## Ref Lifecycle — use `diff map`
+
+Vibium refs are invalidated when the DOM changes. Instead of versioning refs manually, Vibium gives you `vibium diff map` which shows exactly what's new, removed, or repositioned since the last `map` call. After any interaction that changes the DOM:
+
+```bash
+vibium click @e3
+vibium diff map --json   # shows added/removed/moved refs
+```
+
+This is cleaner than tracking version numbers — you get a structured delta you can feed directly into the next action.
+
+## QE Primitives (this skill's value-add)
+
+All scripts live in `.claude/skills/qe-browser/scripts/` and shell out to `vibium`. They expect `vibium` to be on PATH (installed by `aqe init`).
+
+### `assert.js` — Typed assertions with 16 check kinds
+
+```bash
+node scripts/assert.js --checks '[
+  {"kind": "url_contains", "text": "/dashboard"},
+  {"kind": "text_visible", "text": "Welcome"},
+  {"kind": "selector_visible", "selector": "#user-menu"},
+  {"kind": "value_equals", "selector": "input[name=email]", "value": "user@test.com"},
+  {"kind": "no_console_errors"},
+  {"kind": "no_failed_requests"},
+  {"kind": "response_status", "url": "/api/user", "status": 200},
+  {"kind": "element_count", "selector": ".result", "op": ">=", "count": 5}
+]'
+```
+
+All 16 kinds: `url_contains`, `url_equals`, `text_visible`, `text_hidden`, `selector_visible`, `selector_hidden`, `value_equals`, `attribute_equals`, `no_console_errors`, `no_failed_requests`, `response_status`, `request_url_seen`, `console_message_matches`, `element_count`, `title_matches`, `page_source_contains`.
+
+Full reference: [references/assertion-kinds.md](references/assertion-kinds.md).
+
+Exit code is non-zero if any check fails. Output is JSON: `{ "passed": N, "failed": M, "results": [...] }`.
+
+### `batch.js` — Multi-step execution with stop-on-failure
+
+```bash
+node scripts/batch.js --steps '[
+  {"action": "go", "url": "https://example.com/login"},
+  {"action": "fill", "ref": "@e1", "text": "user@test.com"},
+  {"action": "fill", "ref": "@e2", "text": "secret"},
+  {"action": "click", "ref": "@e3"},
+  {"action": "wait_url", "pattern": "/dashboard"},
+  {"action": "assert", "checks": [{"kind": "no_console_errors"}]}
+]' --summary-only
+```
+
+Reduces round-trips vs calling `vibium` per step. Supports `--stop-on-failure` (default true) and `--summary-only`.
+
+### `visual-diff.js` — Pixel diff against stored baselines
+
+```bash
+# First run — creates baseline
+node scripts/visual-diff.js --name "homepage"
+
+# Subsequent runs — compare
+node scripts/visual-diff.js --name "homepage" --threshold 0.05
+
+# Scope to an element
+node scripts/visual-diff.js --name "hero" --selector "#hero"
+
+# Reset baseline after intentional change
+node scripts/visual-diff.js --name "homepage" --update-baseline
+```
+
+Baselines stored in `.aqe/visual-baselines/` (project-local, gitignored by default). Uses `pixelmatch` for pixel comparison; returns similarity % and diff image path.
+
+### `check-injection.js` — Prompt injection scanner
+
+Scans the current page content for known prompt-injection patterns (ignore previous instructions, system prompts in hidden text, etc.). Ported from gsd-browser's heuristic scanner (MIT/Apache).
+
+```bash
+vibium go https://untrusted-page.com
+node scripts/check-injection.js --include-hidden --json
+```
+
+Returns severity-ranked findings. Intended for `pentest-validation`, `injection-analyst`, and `aidefence-guardian`.
+
+### `intent-score.js` — 15 semantic intents
+
+Heuristic-scored element discovery — no LLM round-trip. Ported from gsd-browser's `intent.rs:59-385` (MIT/Apache).
+
+```bash
+node scripts/intent-score.js --intent accept_cookies
+node scripts/intent-score.js --intent submit_form --scope "#login-form"
+node scripts/intent-score.js --intent primary_cta
+```
+
+Intents: `submit_form`, `close_dialog`, `primary_cta`, `search_field`, `next_step`, `dismiss`, `auth_action`, `back_navigation`, `fill_email`, `fill_password`, `fill_username`, `accept_cookies`, `main_content`, `pagination_next`, `pagination_prev`.
+
+Returns top 5 candidates with scores and selectors. Useful for dismissing cookie banners, finding login forms, and navigating through wizards without having to map the whole page.
+
+## Common QE Patterns
+
+### Pattern 1 — Visual regression in CI
+
+```bash
+vibium go "$STAGING_URL"
+vibium wait load
+node scripts/visual-diff.js --name "homepage-$(uname -m)" --threshold 0.02
+# Non-zero exit if diff exceeds threshold
+```
+
+### Pattern 2 — E2E flow with explicit assertions
+
+```bash
+node scripts/batch.js --steps @flows/login-flow.json
+node scripts/assert.js --checks @assertions/post-login.json
+```
+
+### Pattern 3 — Accessibility audit without axe round-trip
+
+```bash
+vibium go "$URL"
+vibium a11y-tree --json > a11y.json
+# Analyze a11y.json with axe-core or in-skill rules
+```
+
+### Pattern 4 — Auth state reuse
+
+```bash
+# Once: log in and save state
+vibium go https://app.example.com/login
+vibium fill "input[name=email]" "$USERNAME"
+vibium fill "input[name=password]" "$PASSWORD"
+vibium click "button[type=submit]"
+vibium wait url "/dashboard"
+vibium storage -o .aqe/auth/myapp.json
+
+# Every subsequent run
+vibium storage restore .aqe/auth/myapp.json
+vibium go https://app.example.com/dashboard
+```
+
+### Pattern 5 — Pentest exploit validation
+
+```bash
+vibium go "$TARGET"
+node scripts/check-injection.js --include-hidden > injection-report.json
+vibium record start --name "exploit-$(date +%s)"
+# Perform exploit steps via vibium commands
+vibium record stop -o evidence.zip
+```
+
+### Pattern 6 — Semantic cookie banner dismissal
+
+```bash
+vibium go "$URL"
+# Heuristic scoring — no LLM needed
+ACCEPT=$(node scripts/intent-score.js --intent accept_cookies --json | jq -r '.candidates[0].selector // empty')
+[ -n "$ACCEPT" ] && vibium click "$ACCEPT"
+```
+
+## MCP Integration
+
+Vibium ships its own MCP server. Use via:
+
+```bash
+claude mcp add vibium -- npx -y vibium mcp
+```
+
+When Vibium MCP tools are available (`mcp__vibium__*`), prefer them over shell-out for the core navigate/map/click/fill operations. Continue to use this skill's `scripts/` for the QE-specific primitives (assertions, batch, visual-diff, injection, intents) — they are not part of Vibium.
+
+## Fallback Policy
+
+If `vibium` is not installed (e.g., `aqe init` hasn't run or user opted out), the qe-browser helper scripts implement the contract automatically. **You don't have to grep error strings.** Each script:
+
+1. Catches the `VibiumUnavailableError` thrown by `lib/vibium.js` when the binary isn't on PATH
+2. Emits a structured `skipped` envelope (see Output Contract below) with `vibiumUnavailable: true` at the top level and `output.reason: "browser-engine-unavailable"`
+3. Exits with **exit code 2** (skipped, distinct from 0=success and 1=failed)
+4. Never silently falls back to Playwright or puppeteer-extra
+
+Downstream skills that shell out to these helpers can branch on the structured fields:
+
+```bash
+node .claude/skills/qe-browser/scripts/assert.js --checks "$CHECKS"
+EXIT=$?
+case $EXIT in
+  0) echo "passed" ;;
+  1) echo "failed" ; cat last-output.json ;;
+  2) echo "skipped — vibium not installed; run \`aqe init\` or \`npm install -g vibium\`" ;;
+esac
+```
+
+Or in Node:
+```javascript
+const result = JSON.parse(stdout);
+if (result.vibiumUnavailable) {
+  // Surface skipped status to the caller; do NOT mark as failed
+  return { status: 'skipped', reason: result.output.reason };
+}
+```
+
+## Migration from Playwright
+
+If you have an existing Playwright test:
+
+```javascript
+// Playwright
+await page.goto('https://example.com');
+await page.fill('input[name=email]', 'user@test.com');
+await page.click('button[type=submit]');
+await expect(page).toHaveURL(/dashboard/);
+```
+
+Becomes:
+
+```bash
+# qe-browser
+vibium go https://example.com
+vibium fill "input[name=email]" "user@test.com"
+vibium click "button[type=submit]"
+vibium wait url "/dashboard"
+node .claude/skills/qe-browser/scripts/assert.js --checks '[
+  {"kind": "url_contains", "text": "/dashboard"}
+]'
+```
+
+Full migration guide: [references/migration-from-playwright.md](references/migration-from-playwright.md).
+
+## Output Contract
+
+All scripts emit a structured JSON envelope. There are three valid `status` values:
+
+### success (exit code 0)
+
+```json
+{
+  "skillName": "qe-browser",
+  "version": "1.0.0",
+  "timestamp": "2026-04-09T12:00:00Z",
+  "status": "success",
+  "trustTier": 3,
+  "output": {
+    "operation": "assert",
+    "summary": "All 6 assertions passed",
+    "assert": { ... }
+  },
+  "metadata": { "executionTimeMs": 142 }
+}
+```
+
+### failed (exit code 1)
+
+Same shape; `status: "failed"` indicates a genuine assertion failure or operation error. The `output.*` block carries the per-check details.
+
+### skipped (exit code 2) — F1 contract
+
+Emitted when vibium is not installed on PATH. Top-level `vibiumUnavailable: true` is the **canonical signal** for downstream skills.
+
+```json
+{
+  "skillName": "qe-browser",
+  "version": "1.0.0",
+  "timestamp": "2026-04-09T12:00:00Z",
+  "status": "skipped",
+  "trustTier": 3,
+  "vibiumUnavailable": true,
+  "output": {
+    "operation": "assert",
+    "summary": "vibium binary not found on PATH. Install via `npm install -g vibium` or run `aqe init`.",
+    "reason": "browser-engine-unavailable",
+    "error": "vibium binary not found on PATH...",
+    "remediation": [
+      "Install vibium globally: `npm install -g vibium`",
+      "Or re-run `aqe init` to install via the AQE bootstrap",
+      "Set QE_BROWSER_HEADED=1 only for interactive debugging (not the cause here)"
+    ]
+  },
+  "metadata": { "executionTimeMs": 0 }
+}
+```
+
+### Exit code summary
+
+| Exit | Status      | Meaning                                                   |
+|------|-------------|-----------------------------------------------------------|
+| 0    | `success`   | every assertion passed / operation completed              |
+| 1    | `failed`    | genuine assertion failure or operation error              |
+| 2    | `skipped`   | vibium unavailable; environment problem, not a test result |
+
+CI tooling can use the exit code to distinguish "test legitimately failed" (block the build) from "we couldn't run the test because the browser engine isn't installed" (warn but don't block).
+
+Validate with `scripts/validate-config.json` + `schemas/output.json`.
+
+## Attribution
+
+- Prompt-injection scanner and intent-scoring logic ported from [gsd-browser](https://github.com/gsd-build/gsd-browser) (MIT/Apache-2.0).
+- Engine: [Vibium](https://github.com/VibiumDev/vibium) (Apache-2.0).

package/.claude/skills/qe-browser/evals/qe-browser.yaml

@@ -0,0 +1,291 @@
+skill: qe-browser
+version: 1.0.0
+status: design-spec
+description: >
+  Manual smoke-test plan for the qe-browser fleet skill, NOT yet a runnable
+  automated eval.
+
+  HONESTY NOTE (devil's-advocate H8): the test cases below use structured
+  assertion fields (`exit_code`, `json_fields`, `severity_at_least`,
+  `candidate_count_at_least`) that the existing AQE eval runner
+  (`src/validation/parallel-eval-runner.ts`) does NOT support — it expects
+  `expected_output.must_contain` keyword matching only. This file is
+  therefore a SPECIFICATION for what the eval should do, not a runnable
+  yaml. Two paths to make it runnable:
+
+  1. Extend the eval runner with a `structured_assertions` block that
+     evaluates JSON paths against script JSON envelopes (preferred — gives
+     us the precision the qe-browser primitives need).
+  2. Rewrite each tc as a `must_contain` test by piping the script's JSON
+     envelope through jq and matching keywords (loses precision).
+
+  Until one of those lands, run `scripts/smoke-test.sh` (alongside this
+  file) for the same fixture coverage in shell-script form. That script IS
+  runnable today and is what gates PR-reopen per ADR-091 Phase 3.
+
+models_to_test:
+  - claude-3.5-sonnet
+  - claude-3-haiku
+
+mcp_integration:
+  enabled: true
+  namespace: skill-validation
+  query_patterns: true
+  track_outcomes: true
+  store_patterns: true
+  target_agents:
+    - qe-visual-tester
+    - qe-accessibility-auditor
+    - qe-pentest-validator
+
+learning:
+  store_success_patterns: true
+  pattern_ttl_days: 90
+
+result_format:
+  json_output: true
+  include_timing: true
+  include_token_usage: true
+
+setup:
+  required_tools:
+    - vibium
+    - node
+    - jq
+  optional_tools:
+    - pixelmatch
+    - pngjs
+  local_fixtures:
+    # A tiny static server serving this repo's .claude/skills/ docs.
+    # Rationale (feedback_synthetic_fixtures_dont_count.md): rather than a
+    # synthetic fixture, we serve real markdown content from the repo via a
+    # one-liner Node server so every run tests against prose that actually
+    # exists and is versioned with the skill.
+    local_docs_server:
+      command: "node .claude/skills/qe-browser/fixtures/serve-skills.js"
+      port: 8088
+      base_url: "http://localhost:8088"
+
+fixtures:
+  public_pinned:
+    # Pinned public endpoints — chosen because they're stable, well-known, and
+    # serve predictable forms / HTML. Per feedback_no_unverified_failure_modes,
+    # these are the canonical "does the tool actually work" fixtures.
+    httpbin_form:
+      url: "https://httpbin.org/forms/post"
+      description: "Classic simple form — custname, custtel, custemail, size, toppings"
+    httpbin_html:
+      url: "https://httpbin.org/html"
+      description: "Static HTML page with known headings"
+    httpbin_status_404:
+      url: "https://httpbin.org/status/404"
+      description: "Known 404 for testing no_failed_requests"
+  pinned_docs_site:
+    # Pinned to a specific Git tag so the docs don't change under us.
+    url: "https://vibiumdev.github.io/vibium/tutorials/getting-started-js"
+    pin_version: "v26.3.18"
+    description: "Vibium's own getting-started docs — stable, public, versioned"
+  local_skills_docs:
+    base_url: "http://localhost:8088"
+    pages:
+      - "/qe-browser/SKILL.md.html"
+      - "/qe-browser/references/assertion-kinds.md.html"
+
+test_cases:
+  # -------- assert.js --------
+  - id: tc001_assert_url_contains_httpbin
+    description: "url_contains assertion on pinned httpbin form page"
+    category: assert
+    priority: critical
+    input:
+      setup:
+        - "vibium go https://httpbin.org/forms/post"
+      command: |
+        node .claude/skills/qe-browser/scripts/assert.js --checks \
+          '[{"kind": "url_contains", "text": "httpbin.org/forms"}]'
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.assert.passed": 1
+        ".output.assert.failed": 0
+
+  - id: tc002_assert_selector_visible_h1
+    description: "selector_visible on pinned httpbin /html page"
+    category: assert
+    priority: critical
+    input:
+      setup:
+        - "vibium go https://httpbin.org/html"
+      command: |
+        node .claude/skills/qe-browser/scripts/assert.js --checks \
+          '[{"kind": "selector_visible", "selector": "h1"}]'
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+
+  - id: tc003_assert_failure_detected
+    description: "Failing assertion must exit non-zero and report failed>0"
+    category: assert
+    priority: critical
+    input:
+      setup:
+        - "vibium go https://httpbin.org/html"
+      command: |
+        node .claude/skills/qe-browser/scripts/assert.js --checks \
+          '[{"kind": "url_contains", "text": "this-does-not-exist"}]'
+    expected:
+      exit_code: 1
+      json_fields:
+        ".status": "failed"
+        ".output.assert.failed": 1
+
+  # -------- batch.js --------
+  - id: tc004_batch_navigate_and_assert
+    description: "batch: navigate + wait + assert in a single call"
+    category: batch
+    priority: critical
+    input:
+      command: |
+        node .claude/skills/qe-browser/scripts/batch.js --steps \
+          '[
+            {"action": "go", "url": "https://httpbin.org/html"},
+            {"action": "wait_load"},
+            {"action": "assert", "checks": [
+              {"kind": "url_contains", "text": "/html"},
+              {"kind": "selector_visible", "selector": "h1"}
+            ]}
+          ]' --summary-only
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.batch.passedSteps": 3
+        ".output.batch.totalSteps": 3
+
+  - id: tc005_batch_stops_on_failure
+    description: "batch: stop-on-failure halts after failed step"
+    category: batch
+    priority: high
+    input:
+      command: |
+        node .claude/skills/qe-browser/scripts/batch.js --steps \
+          '[
+            {"action": "go", "url": "https://httpbin.org/html"},
+            {"action": "click", "selector": "#does-not-exist"},
+            {"action": "go", "url": "https://httpbin.org/forms/post"}
+          ]'
+    expected:
+      exit_code: 1
+      json_fields:
+        ".status": "failed"
+        ".output.batch.passedSteps": 1
+        ".output.batch.failedStep.index": 1
+
+  # -------- visual-diff.js --------
+  - id: tc006_visual_diff_baseline_created
+    description: "First run creates a baseline and reports baseline_created"
+    category: visual-diff
+    priority: high
+    input:
+      setup:
+        - "vibium go http://localhost:8088/qe-browser/SKILL.md.html"
+        - "rm -rf .aqe/visual-baselines/eval_local_docs*"
+      command: |
+        node .claude/skills/qe-browser/scripts/visual-diff.js \
+          --name eval_local_docs --threshold 0.02
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.visualDiff.status": "baseline_created"
+
+  - id: tc007_visual_diff_match_second_run
+    description: "Second identical run reports match"
+    category: visual-diff
+    priority: high
+    input:
+      setup:
+        - "vibium go http://localhost:8088/qe-browser/SKILL.md.html"
+      command: |
+        node .claude/skills/qe-browser/scripts/visual-diff.js \
+          --name eval_local_docs --threshold 0.02
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.visualDiff.status": "match"
+
+  # -------- check-injection.js --------
+  - id: tc008_check_injection_clean_page
+    description: "Clean page (httpbin /html) reports no findings"
+    category: check-injection
+    priority: critical
+    input:
+      setup:
+        - "vibium go https://httpbin.org/html"
+      command: |
+        node .claude/skills/qe-browser/scripts/check-injection.js --include-hidden
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.checkInjection.severity": "none"
+
+  - id: tc009_check_injection_poisoned_page
+    description: "Local poisoned fixture with hidden instructions is detected"
+    category: check-injection
+    priority: critical
+    input:
+      setup:
+        - "vibium go http://localhost:8088/fixtures/injection-poisoned.html"
+      command: |
+        node .claude/skills/qe-browser/scripts/check-injection.js --include-hidden
+    expected:
+      exit_code: 1
+      json_fields:
+        ".status": "failed"
+      severity_at_least: "high"
+
+  # -------- intent-score.js --------
+  - id: tc010_intent_submit_form_on_httpbin
+    description: "find submit_form on the httpbin form"
+    category: intent-score
+    priority: critical
+    input:
+      setup:
+        - "vibium go https://httpbin.org/forms/post"
+      command: |
+        node .claude/skills/qe-browser/scripts/intent-score.js \
+          --intent submit_form
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "success"
+        ".output.intentScore.intent": "submit_form"
+      candidate_count_at_least: 1
+
+  - id: tc011_intent_fill_email_returns_empty_for_non_form_page
+    description: "fill_email returns no candidates on httpbin /html"
+    category: intent-score
+    priority: medium
+    input:
+      setup:
+        - "vibium go https://httpbin.org/html"
+      command: |
+        node .claude/skills/qe-browser/scripts/intent-score.js --intent fill_email
+    expected:
+      exit_code: 0
+      json_fields:
+        ".status": "partial"
+        ".output.intentScore.candidateCount": 0
+
+validation:
+  required_pass_rate: 0.9
+  critical_must_pass: true
+  notes: |
+    Evaluation assumes:
+      - `vibium` v26.3.x+ is on PATH (from `aqe init` or `npm install -g vibium`)
+      - Network access to httpbin.org (public, stable)
+      - Local fixtures server running on :8088 (started in setup.local_docs_server)