opencode-agent-skill 10.0.0 → 12.0.0-beta.0

package/docs/ENGINEERING-DESIGN.md

@@ -1,6 +1,6 @@
 # UES engineering design
 
-UES 8 evolves the project from an engineering workflow harness into a **long-horizon execution engine** designed to reduce context pressure on coding models.
+V11 evolves the project from an engineering workflow harness into a **perception-aware adaptive execution engine** designed to reduce context pressure on coding models while keeping evidence needed for correctness.
 
 The selected model remains the selected model. UES improves orchestration, evidence, task boundaries, state persistence and verification; it does not claim model equivalence.
 
@@ -44,11 +44,11 @@ Models still reason about semantics and read affected code.
 
 ### Progressive disclosure
 
-The catalog remains 39 skills. UES prefers a small active skill set and loads deeper references only when needed.
+The catalog spans 48 skills. UES prefers a small active skill set and loads deeper references only when needed.
 
 ### Hard gates, not reminders
 
-V8 machine-enforces the important boundaries:
+V11 machine-enforces the important boundaries:
 
 1. long/high-risk plans are not executable until a structured plan-verification receipt matches the current plan hash;
 2. long/high-risk task completion requires a successful verification receipt for the active run and the current workspace fingerprint;
@@ -133,7 +133,7 @@ Only UES-managed resources are rewritten/removed.
 
 UES separates:
 
-1. **static skill contract** — 34 scenarios covering the 39-skill catalog;
+1. **static skill contract** — 43 scenarios covering the 48-skill catalog;
 2. **V2 router precision matrix** — 120 required-route/negative-guard cases;
 3. **standard live benchmark** — 20 executable hidden-graded tasks;
 4. **long-horizon benchmark** — 5 tasks, including one 15-source-file integration workload;

package/docs/EVALS.md

@@ -1,10 +1,10 @@
 # UES evaluations
 
-UES 8 separates catalog correctness, routing precision, benchmark integrity, final behavior, long-horizon orchestration and cross-stack coverage.
+V11 separates catalog correctness, routing precision, benchmark integrity, final behavior, long-horizon orchestration and cross-stack coverage.
 
 ## 1. Static skill-routing contract
 
-`evals/routing.json` keeps 34 representative scenarios and covers all installed skills.
+`evals/routing.json` keeps 43 representative scenarios and covers all installed skills.
 
 ```bash
 npm run evals
@@ -141,7 +141,7 @@ Compare the same model, variant, prompt, fixture, grader and environment. Report
 A benchmark result is evidence only for the measured workload. UES does not claim to turn one base model into another.
 
 
-## V8 live-run observability and evidence gate
+## V11 live-run observability and evidence gate
 
 Live runs accept:
 

package/docs/GITHUB-RULESET.md

@@ -0,0 +1,50 @@
+# GitHub Ruleset Readiness
+
+This document records the recommended GitHub repository ruleset configuration for the `main` branch, to be activated only after CI Gate and Security Gate have each achieved at least one successful run.
+
+## Recommended ruleset
+
+- **Ruleset name:** `main-protection`
+- **Target:** default branch / `main`
+- **Enforcement:** Active
+
+## Rules
+
+1. **Restrict deletions** — block deleting the default branch or force-pushing over it.
+2. **Block force pushes** — no `git push --force` or `git push -f` to `main`.
+3. **Require pull request before merge** — all changes must go through a PR.
+4. **Require conversation resolution** — PR reviewers must resolve all inline comments before merge.
+5. **Require status checks** — PRs must have passing CI Gate and Security Gate checks before merge.
+6. **Require branch up to date** — PR branches must be up to date with `main` before merge (applies when there are multiple contributors; can be relaxed for single-maintainer setups).
+7. **Required check: CI Gate** — the aggregate CI check from `.github/workflows/ci.yml`.
+8. **Required check: Security Gate** — the aggregate security check from `.github/workflows/security.yml`.
+
+## Approval policy for single-maintainer repo
+
+This repository currently has one maintainer. Setting `required approval = 1` would prevent the owner from merging their own PRs (they cannot approve their own PR). Therefore:
+
+- **Required approval = 0** for now.
+- When a collaborator or external reviewer is added, raise to `required approval = 1` to restore oversight.
+
+## Classic branch protection vs ruleset
+
+GitHub supports both classic branch protection rules and repository rulesets simultaneously. When both are configured:
+
+- They can apply independently to different aspects of branch protection.
+- Be cautious of duplicate or conflicting protections (e.g., two rules both requiring status checks but with different required lists).
+- If migrating from classic protection to ruleset, remove the classic rule after confirming the ruleset is active and working.
+
+## Activation prerequisite
+
+Do not enable the ruleset until:
+
+1. CI Gate has at least one successful run on `main`.
+2. Security Gate has at least one successful run on `main` or a PR.
+
+Without these prerequisites, the ruleset would block all merges immediately after activation, effectively locking the repository.
+
+## Current status
+
+- **CI Gate:** Added in `.github/workflows/ci.yml`. Awaiting first successful run.
+- **Security Gate:** Added in `.github/workflows/security.yml`. Awaiting first successful run.
+- **Ruleset:** NOT YET ACTIVATED. Will be configured via GitHub admin settings after both gates have successful runs.

package/docs/NPM-PUBLISH.md

@@ -17,7 +17,7 @@ opencode-agent-skill
 npm run ci
 ```
 
-V9 CI includes syntax validation, resource validation, static skill routing, the 120-case V2 router matrix, standard/long/polyglot hidden-grader integrity checks, unit/integration tests, package dry-run, packed global-install smoke, and a plain global-install compatibility smoke.
+CI includes syntax validation, resource validation, static skill routing, the 129-case V2 router matrix, 13 V11 contract tasks, standard/long/polyglot hidden-grader integrity checks, unit/integration tests, package dry-run, packed global-install smoke, and a plain one-command install/resource sync smoke.
 
 ## Manual release-like test
 
@@ -27,7 +27,7 @@ Use:
 
 ```cmd
 npm pack
-npm install -g .\opencode-agent-skill-9.0.0.tgz --allow-scripts=opencode-agent-skill
+npm install -g .\opencode-agent-skill-11.0.0.tgz --allow-scripts=opencode-agent-skill
 ocskill status
 ocskill doctor
 ```
@@ -47,14 +47,14 @@ After publication verify:
 
 ```cmd
 npm view opencode-agent-skill versions --json
-npm view opencode-agent-skill@9.0.0 version
+npm view opencode-agent-skill@11.0.0 version
 npm dist-tag ls opencode-agent-skill
 ```
 
 The expected release tag is:
 
 ```text
-latest: 9.0.0
+latest: 11.0.0
 ```
 
 ## GitHub Actions publishing

package/docs/OPENCODE-COMPAT.md

@@ -1,6 +1,6 @@
 # OpenCode compatibility
 
-UES 8 ships one npm package for OpenCode 1.x and 2.x, while only enabling V2-native runtime features when V2 is detected.
+V11 ships one npm package for OpenCode 1.x and 2.x, while only enabling V2-native runtime features when V2 is detected.
 
 ## Detection
 
@@ -23,9 +23,9 @@ The detected major is recorded in the managed state.
 
 UES installs:
 
-- 39 namespaced skills
+- 48 namespaced skills
 - 11 namespaced commands
-- 10 namespaced subagents using compatible V1 `permission` frontmatter
+- 12 namespaced subagents using compatible V1 `permission` frontmatter
 - managed global `AGENTS.md` block
 
 The V2 runtime plugin is not installed.

package/docs/TRACE-SCHEMA.md

@@ -75,7 +75,7 @@ Keep constant:
 Compare observable success, regressions, elapsed time, tool behavior and cost rather than narrative confidence.
 
 
-## V8 runtime and evidence fields
+## V11 runtime and evidence fields
 
 Each live result may additionally contain:
 

package/docs/V11-PERCEPTION-ADAPTIVE-EXECUTION.md

@@ -0,0 +1,75 @@
+# V11 Perception & Adaptive Execution
+
+## Goal
+
+V11 minimizes context and model cost without deleting evidence needed for correctness. It adds perception-aware UI/browser verification so the system can reason about **what an element is, where it is and how it looks** using different evidence channels.
+
+## Runtime layers
+
+```text
+Task
+  -> intent/risk
+  -> capability requirements
+  -> adaptive evidence budget
+  -> semantic/index evidence
+  -> content-addressed evidence pointers
+  -> focused skills
+  -> capability-aware model
+  -> fresh executor
+  -> deterministic verification
+  -> visual/browser verifier when required
+  -> diagnosis + evidence expansion only on failure
+```
+
+## Evidence Store
+
+Large raw tool output, durable specs and dependency reports are stored under:
+
+```text
+.ues-cache/evidence-v1/<hash-prefix>/<sha256>.blob
+.ues-cache/evidence-v1/<hash-prefix>/<sha256>.json
+```
+
+A prompt receives a bounded excerpt and a reference such as `evidence:sha256:<hash>`. Use `ocskill store get` to retrieve only the needed slice. `.ues-cache` is runtime state and is excluded from workspace verification fingerprints.
+
+## Adaptive evidence budget
+
+FAST/STANDARD/DEEP remain outer safety ceilings. Inside that ceiling V11 allocates characters by evidence role instead of treating all context as equally valuable. Debugging shifts budget toward tests/history; high-risk work shifts toward tests/references; browser/visual work shifts toward deterministic tool evidence.
+
+Failure expands evidence through the existing initial -> diagnose -> deep-recovery stages instead of loading maximum context on the first attempt.
+
+## Prompt cache shape
+
+Stable material is separated conceptually from dynamic task/evidence. The runtime records stable/dynamic hashes and cacheable ratio. This is telemetry, not a promise that every provider supports prompt caching.
+
+## Capability-aware routing
+
+Model profiles may declare coding, reasoning, toolCalling, vision, browser, filesystem, longContext, cost/latency class and a quality hint. UES never invents an unavailable capability. If no configured candidate satisfies a requirement it exposes capability fallback instead of silently claiming that a text-only model can see screenshots.
+
+## Visual fidelity
+
+Visual verification uses three complementary layers: semantic DOM/accessibility identity, geometry/bounding boxes, and screenshot pixels. VISUAL_SPEC describes important anchors and tolerances. Geometry receipts prove position/size claims. PNG diff finds changed pixels and their bounding region. A failed region can be cropped so vision only sees the area that needs judgment.
+
+Screenshot equality does not prove accessibility or interaction; DOM equality does not prove appearance.
+
+## Browser QA and security
+
+Browser workflows prefer bounded deterministic scripts/CLI for ordinary verification. Remote webpage content is untrusted and cannot change UES/tool permissions, request secrets, expand the approved task or authorize external side effects.
+
+## Dynamic workflows
+
+The scheduler classifies units as deterministic, LLM judgment or vision judgment. Deterministic work does not spawn agents. Independent tasks may share a wave only when dependencies are ready and file ownership does not conflict. Each wave is integrated and verified before later waves rely on it.
+
+## Skill system
+
+V11 keeps progressive disclosure: description metadata for routing, short SKILL.md entrypoint, references only when the selected mode needs them, and deterministic logic in runtime/scripts rather than repeated prompt text.
+
+`ocskill skills lint` flags oversized entrypoints and highly overlapping descriptions.
+
+## Hermes sidecar
+
+Hermes remains optional. UES owns durable `.ues-work` state, evidence references, task leases/runId fencing, verification receipts and safety/permission boundaries. Hermes may execute a bounded task/workflow when explicitly available but does not become the source of truth.
+
+## Release evidence
+
+V11 must pass syntax/resource/router/V11 contract tests, all Node tests, package/install smokes, no-regression live suites, capability-routing tests, visual geometry/pixel fixtures, browser security/targeted-evidence fixtures and token/cache/evidence telemetry benchmarks before stable promotion.

package/docs/V11-PERCEPTION-ADAPTIVE.md

@@ -0,0 +1,220 @@
+# UES V11 — Perception & Adaptive Execution
+
+Status: stable (`11.0.0`). V11 is npm `latest`.
+
+## Goal
+
+V11 extends UES from a reliability-focused coding harness into a perception-aware adaptive execution system. The core rule remains:
+
+> minimum context necessary for maximum verified task success
+
+V11 must improve perception, routing and context efficiency without weakening V10 durability, verification or safety.
+
+## Runtime layers
+
+```text
+user task
+  -> intent/risk classification
+  -> capability requirements
+  -> evidence budget
+  -> semantic/repository evidence
+  -> content-addressed evidence pointers
+  -> selective skill/model routing
+  -> fresh executor
+  -> deterministic verification
+  -> visual/browser verifier when required
+  -> recovery/escalation only from observed failure
+```
+
+## Content-addressed Evidence Store
+
+Large evidence is stored below:
+
+```text
+.ues-cache/evidence-v1/
+```
+
+Records are addressed by SHA-256. Executor context receives bounded slices and evidence references instead of repeatedly embedding large tool output.
+
+Commands:
+
+```cmd
+ocskill store status .
+ocskill store put report.txt . --kind tool-output
+ocskill store get evidence:sha256:<hash> . --max 12000
+ocskill store gc . --max-entries 2000 --max-age-days 30
+```
+
+Evidence pointers are not proof by themselves. Any claim still needs the relevant content or a verification receipt.
+
+## Adaptive Evidence Budget
+
+V11 partitions context among instructions, task, declared code, tests, references, history and tools. Debugging, high-risk, visual and browser work can reallocate budget without automatically consuming the full 48k ceiling.
+
+Failure expands evidence in stages; it does not justify replaying already-proven exploration.
+
+## Prompt cache layout
+
+The prompt envelope is split into a stable prefix and dynamic tail.
+
+Stable:
+- role and invariants
+- loaded skill IDs
+- stable project facts
+- tool policy
+
+Dynamic:
+- current task
+- evidence pointers
+- recent failure
+- next action
+- recent messages
+
+Telemetry records stable/dynamic hashes, sizes and cacheable ratio. This is diagnostic; provider-side cache behavior is provider-dependent.
+
+## Capability-aware model routing
+
+Models may declare:
+- coding
+- reasoning
+- tool calling
+- vision
+- browser
+- filesystem
+- long context
+- cost class
+- latency class
+- quality hint
+
+Example:
+
+```cmd
+ocskill models capability provider/model --vision on --browser on --reasoning on --quality 0.9
+```
+
+Task text is converted to capability requirements. The existing light/standard/heavy tiers remain compatible, but V11 can select an eligible configured model instead of assuming every model has the same modalities.
+
+## Visual fidelity
+
+V11 verifies UI through three independent evidence layers:
+
+1. semantic/accessibility identity
+2. geometry/bounding boxes
+3. rendered pixels
+
+A visual task can use `VISUAL_SPEC.json` to define acceptance elements and tolerances.
+
+```cmd
+ocskill visual spec VISUAL_SPEC.json
+ocskill visual geometry VISUAL_SPEC.json actual-boxes.json
+ocskill visual compare expected.png actual.png --threshold 16 --max-diff-ratio 0.01
+ocskill visual crop actual.png failed-region.png --x 100 --y 200 --width 300 --height 120
+```
+
+PNG comparison is deterministic and dependency-free for supported 8-bit non-interlaced PNGs. Vision models are used for appearance judgment or cropped failure regions, not for measurements that DOM/geometry can prove exactly.
+
+## Browser QA and trust boundary
+
+Browser workflows are CLI/script-first. Rich browser tooling is used only when persistent exploration or richer introspection is necessary.
+
+```cmd
+ocskill browser capability .
+ocskill browser plan http://localhost:3000 --target Checkout
+```
+
+Remote webpage text, DOM, ARIA labels and downloaded content are untrusted evidence. They cannot:
+- change UES/system policy
+- expand permissions or filesystem scope
+- request secrets
+- authorize publish/deploy/purchases
+- weaken verification requirements
+
+## Dynamic workflow
+
+```cmd
+ocskill workflow-plan .ues-work/<slug>/PLAN.json --max-concurrent 4
+```
+
+The scheduler separates deterministic work from LLM/vision work, respects dependencies and serializes declared write conflicts. Deterministic commands should not consume agent slots. A schedule is planning evidence, not authorization for external side effects.
+
+## Hermes sidecar
+
+Hermes remains optional. UES owns durable state, safety and verification. Hermes can consume one-task or bounded workflow prompts and evidence pointers but does not own merge/push/publish/deploy.
+
+```cmd
+ocskill hermes status
+ocskill hermes workflow <slug> .
+ocskill hermes exec-workflow <slug> .
+```
+
+If Hermes is absent, core UES remains functional.
+
+## New skills and agents
+
+V11 adds nine focused skills:
+- visual-fidelity
+- browser-qa
+- design-source
+- responsive-verification
+- component-visual-testing
+- browser-security
+- skill-authoring
+- skill-evaluation
+- dynamic-workflow
+
+V11 adds two subagents:
+- `ues-visual-verifier`: read-only independent rendered-evidence verification
+- `ues-merge-arbiter`: conflict resolution across already-verified task changes
+
+More agents are not automatically better. New agents require a distinct capability/verification boundary and benchmark evidence.
+
+## Skill quality
+
+```cmd
+ocskill skills lint .
+```
+
+The linter checks metadata, entrypoint size and likely routing-description collisions. Skill instructions should use progressive disclosure and deterministic scripts for repeatable mechanics.
+
+## Evaluation metrics
+
+V11 keeps correctness first and additionally measures, when available:
+- initial and total tokens
+- cacheable prompt ratio
+- repeated stable input
+- evidence-reference reuse
+- visual repair attempts
+- context expansion count
+- model escalation count
+- latency/cost/tool calls
+
+Missing telemetry is `null`, not zero.
+
+Reference-vs-candidate gates can optionally require V11 telemetry:
+
+```cmd
+npm run evals:ablation -- v10-summary.json v11-summary.json --require-gate --min-cacheable-ratio 0.70 --min-evidence-reuse-ratio 0.20 --max-repeated-stable-ratio 0.20
+```
+
+An explicitly requested metric gate fails closed when its telemetry is unavailable.
+
+## Release gates
+
+Do not promote V11 to stable until all are satisfied:
+
+1. `npm run ci` passes on the V11 tree.
+2. No correctness/pass-rate regression versus the accepted V10 reference.
+3. Required initial-input/token efficiency gate passes.
+4. Visual geometry and PNG fixtures pass.
+5. Browser trust-boundary and routing tests pass.
+6. Compaction, timeout, provider recovery, lease recovery and loop guards remain green.
+7. Packed and plain npm-install smoke tests pass.
+8. Real weak-model evaluation shows no suite regression.
+9. Any configured cache/evidence target has sufficient telemetry and passes.
+10. npm `latest` is V11 stable; no release gate prevents promotion.
+
+## Compatibility
+
+OpenCode 1.x continues to receive resource/CLI behavior that does not require V2 runtime hooks.
+
+OpenCode 2.x receives the managed router plugin and fresh-session runtime, including V11 deterministic helper tools for capability inference, evidence retrieval, visual geometry/diff planning, browser planning and dynamic workflow scheduling.

package/docs/V12-WEAK-MODEL-INTELLIGENCE.md

@@ -0,0 +1,27 @@
+# V12 Weak-Model Intelligence Foundation
+
+Status: beta prerelease (`12.0.0-beta.0`, npm dist-tag `next`). V11 (`11.0.0`) remains the stable `latest` release until V12 earns stable-release evidence.
+
+## Goal
+
+V12 focuses on making weaker coding models more reliable on large repositories by improving measured context quality, empirical model routing, plan identity, bounded autonomous decisions, and repo-scale evaluation. It does not claim that orchestration makes one base model equivalent to a stronger model.
+
+## Foundations
+
+- Empirical model performance: observed pass rate, retries, token use and latency can rerank capability-eligible models by task class.
+- Context quality receipts: adaptive context reports required-file recall and irrelevant-context ratio.
+- Plan-scoped snapshots: every imported plan gets a SHA-256 keyed snapshot and active-plan fence before execution.
+- Decision policy: reversible local engineering choices can be auto-resolvable; publish/deploy/destructive/product decisions remain human-gated.
+- Repo-scale contract suite: deterministic generation of a 300-module monorepo fixture for larger-repository validation.
+
+## Release policy
+
+V12 is not stable merely because unit tests pass. Promotion requires healthy GitHub CI/Security gates, repo-scale validation, real weak-model baseline-vs-UES trials, no regression in existing suites, measured context recall, sufficient empirical routing samples, and Windows/Linux package/install smoke evidence.
+
+## Beta install
+
+```cmd
+npm install -g opencode-agent-skill@next
+ocskill install
+ocskill doctor
+```

package/evals/repo-scale/tasks.json

@@ -0,0 +1,62 @@
+{
+  "version": 1,
+  "kind": "repo-scale-contract-suite",
+  "description": "Deterministic large-repository contract tasks used to validate V12 weak-model context/routing foundations before live model runs.",
+  "minimumGeneratedModules": 300,
+  "tasks": [
+    {
+      "id": "cross-package-regression",
+      "category": "repo-scale",
+      "objective": "Trace a regression across package boundaries without loading the entire generated monorepo into context.",
+      "requiredFiles": [
+        "packages/pkg-0/src/mod049.mjs",
+        "packages/pkg-1/src/mod049.mjs"
+      ],
+      "acceptance": [
+        "Required-file context recall is measurable",
+        "Unrelated packages stay bounded"
+      ]
+    },
+    {
+      "id": "public-contract-ripple",
+      "category": "contract",
+      "objective": "Change a public API field and identify the API producer and web consumer that must move together.",
+      "requiredFiles": [
+        "contracts/public-api.json",
+        "apps/api/src/service.mjs",
+        "apps/web/src/consumer.mjs"
+      ],
+      "acceptance": [
+        "Contract producer and consumer are both discovered",
+        "Change-impact evidence is explicit"
+      ]
+    },
+    {
+      "id": "deep-chain-debug",
+      "category": "debugging",
+      "objective": "Diagnose a defect near the end of a fifty-module import chain using bounded evidence expansion.",
+      "requiredFiles": [
+        "packages/pkg-2/src/mod048.mjs",
+        "packages/pkg-2/src/mod049.mjs"
+      ],
+      "acceptance": [
+        "Initial context remains bounded",
+        "Recovery can expand around the failing chain"
+      ]
+    },
+    {
+      "id": "multi-package-refactor",
+      "category": "refactor",
+      "objective": "Coordinate a refactor touching several package endpoints while serializing shared contract writes.",
+      "requiredFiles": [
+        "packages/pkg-3/src/index.mjs",
+        "packages/pkg-4/src/index.mjs",
+        "contracts/public-api.json"
+      ],
+      "acceptance": [
+        "Cross-package scope is explicit",
+        "Shared contract changes are treated as a write-conflict surface"
+      ]
+    }
+  ]
+}

package/evals/router-triggers.json

@@ -1233,6 +1233,88 @@
         "ues-task-planner"
       ],
       "exclude": []
+    },
+    {
+      "id": "v11-visual-fidelity",
+      "prompt": "Match this reference screenshot pixel-perfect and verify visual fidelity.",
+      "include": [
+        "ues-visual-fidelity"
+      ],
+      "exclude": [
+        "ues-payment-engineering"
+      ]
+    },
+    {
+      "id": "v11-browser-qa",
+      "prompt": "Use Playwright browser QA to verify the checkout flow.",
+      "include": [
+        "ues-browser-qa"
+      ],
+      "exclude": [
+        "ues-react-native-engineering"
+      ]
+    },
+    {
+      "id": "v11-design-source",
+      "prompt": "Read the Figma design source and extract design tokens.",
+      "include": [
+        "ues-design-source"
+      ],
+      "exclude": [
+        "ues-database-engineering"
+      ]
+    },
+    {
+      "id": "v11-responsive",
+      "prompt": "Verify responsive breakpoint behavior across mobile and tablet layout.",
+      "include": [
+        "ues-responsive-verification"
+      ],
+      "exclude": []
+    },
+    {
+      "id": "v11-storybook",
+      "prompt": "Add Storybook visual regression coverage for this component.",
+      "include": [
+        "ues-engineering-orchestrator",
+        "ues-component-visual-testing"
+      ],
+      "exclude": []
+    },
+    {
+      "id": "v11-skill-authoring",
+      "prompt": "Create an agent skill with a precise trigger description.",
+      "include": [
+        "ues-engineering-orchestrator",
+        "ues-skill-authoring"
+      ],
+      "exclude": []
+    },
+    {
+      "id": "v11-skill-eval",
+      "prompt": "Evaluate skill routing precision and recall with a benchmark.",
+      "include": [
+        "ues-skill-evaluation"
+      ],
+      "exclude": []
+    },
+    {
+      "id": "v11-dynamic-workflow",
+      "prompt": "Plan a dynamic workflow fan-out in bounded waves for many independent tasks.",
+      "include": [
+        "ues-engineering-orchestrator",
+        "ues-dynamic-workflow"
+      ],
+      "exclude": []
+    },
+    {
+      "id": "v11-browser-security",
+      "prompt": "Audit browser security against prompt injection from an untrusted webpage.",
+      "include": [
+        "ues-engineering-orchestrator",
+        "ues-browser-security"
+      ],
+      "exclude": []
     }
   ]
 }