@event4u/agent-config 8.9.0 → 8.10.0

package/dist/agent-src/skills/existing-ui-audit/SKILL.md

@@ -33,6 +33,36 @@ Do NOT use when:
 - `directive_set="backend"` — no UI surface to inventory
 - The audit findings already exist in `state.ui_audit` for this state-file (cached) — re-run only if `package.json` or `composer.json` mtime changed
 
+## Resource-first context gate (design fidelity)
+
+Any request to **recreate, redesign, mock, prototype, or improve** a UI runs
+this gate BEFORE styling — the Inspect stage of the
+[design-artifact lifecycle](../../../docs/contracts/design-artifact-lifecycle.md).
+Design starts from project truth, not generic aesthetic memory.
+
+- **Search first (owned UI).** Before proposing anything, search the project
+  for: design tokens, global CSS, the component library / design system (§ 2),
+  supplied screenshots or exported design context, Figma/exported context when
+  connected, assets (logos, icons, fonts), and copy tone. Procedure steps 1–5
+  produce this inventory — do not skip them for a "quick" redesign.
+- **Hard stop on a promised-but-inaccessible source.** When the user explicitly
+  references a design system, local folder, Figma file, or codebase you cannot
+  read, STOP and ask for access — never invent a design from memory to paper
+  over the missing source. A promised source that can't be reached is a blocking
+  question ([`ask-when-uncertain`](../../rules/ask-when-uncertain.md)), not a
+  licence to improvise. (fixture: `daf-inaccessible-design-system`.)
+- **Source priority — code beats screenshots.** For exact values (tokens,
+  spacing, component props) the design-system/code context is authoritative; a
+  screenshot conveys gestalt but is not enough for component/token fidelity.
+  Never read pixel values off a screenshot when the source is available.
+- **Tool composition — inspect before you generate.** Owned UI → repository
+  search + local files FIRST. Connected/imported design data (Figma, tokens
+  export) → that connector next, when available. Browser / image search → only
+  for public references or current product/place imagery, never a substitute
+  for inspecting owned code. Generated imagery → only when the user asks for
+  synthetic assets, or no real inspection is required. (fixtures:
+  `daf-no-context`, `daf-missing-asset`.)
+
 ## Procedure: Audit the existing UI surface
 
 ### 0. Inspect stack and input

package/dist/agent-src/skills/existing-ui-audit/evals/triggers.json

@@ -0,0 +1,47 @@
+{
+    "skill": "existing-ui-audit",
+    "last_eval": "2026-07-10",
+    "description": "5 should-trigger + 5 should-not-trigger queries for the resource-first context gate (road-to-design-artifact-fidelity Phase 2). Should-trigger covers the four Phase-2 cases — redesign with code present, screenshot-only, no-assets/owned-UI, and an inaccessible referenced source — plus an improve-existing case; all require inventorying project context BEFORE styling rather than starting from aesthetic memory. Should-not-trigger covers near-miss neighbours whose vocabulary overlaps (backend/API, non-UI, general design knowledge, a genuinely trivial one-line UI edit) that must NOT force a full audit.",
+    "queries": [
+        {
+            "q": "redesign our dashboard — the React components are in src/components, make it cleaner",
+            "trigger": true
+        },
+        {
+            "q": "here is a screenshot of our current app, recreate this screen for us",
+            "trigger": true
+        },
+        {
+            "q": "rebuild our landing page in the same style as the rest of the product",
+            "trigger": true
+        },
+        {
+            "q": "match our Figma file at this link and rebuild the settings page (you may not be able to open it)",
+            "trigger": true
+        },
+        {
+            "q": "improve the UI of our existing checkout flow",
+            "trigger": true
+        },
+        {
+            "q": "add a rate limiter to the /orders API endpoint",
+            "trigger": false
+        },
+        {
+            "q": "write the SQL migration that adds a status column to the orders table",
+            "trigger": false
+        },
+        {
+            "q": "what is the difference between CSS flexbox and grid?",
+            "trigger": false
+        },
+        {
+            "q": "fix the typo in the README heading",
+            "trigger": false
+        },
+        {
+            "q": "explain how our CI release pipeline is structured",
+            "trigger": false
+        }
+    ]
+}

package/dist/agent-src/skills/fe-design/SKILL.md

@@ -43,6 +43,15 @@ Do NOT use this skill to:
 - Audit an existing UI — that is `existing-ui-audit`
 - Drive the full UI flow — that is the `directives/ui/` orchestrator
 
+> **Resource-first, before taste.** Any request to recreate / redesign / mock /
+> prototype / improve an existing UI runs the
+> [resource-first context gate](../existing-ui-audit/SKILL.md#resource-first-context-gate-design-fidelity)
+> FIRST — search the project's tokens/design-system/assets, hard-stop and ask
+> when a referenced source is inaccessible (never invent from memory), and
+> prefer code over screenshots for exact values. Planning here starts from that
+> inventory, not from generic aesthetic memory (design-artifact lifecycle,
+> Inspect stage).
+
 ## How the directive set cites this skill
 
 `directives/ui/design.ts` produces the design brief (layout, components,
@@ -247,11 +256,33 @@ Animate `transform` and `opacity` only. Why: these run on the GPU compositor thr
 
 ## Presenting variants
 
-This skill produces ONE refined solution. When the user wants multiple options
-to compare (or a live tweak panel over one design), hand off to
-[`design-variations`](../design-variations/SKILL.md) — it owns the
-basic→bold variation method and the single-file tweak-panel mechanics
-(CSS custom properties + floating "Tweaks" panel + `localStorage`).
+This skill produces ONE refined solution by default. **Plan the variation
+decision before generating** — do not reflexively emit one generic design when
+exploration was asked, nor spam options when one production answer was asked.
+
+- **Decide whether to vary (ask only if ambiguous).** For ambiguous creative
+  work, decide the variation count and the axis that varies — visual direction,
+  UX flow, interaction model, copy, density, or brand strictness. Ask about
+  count + axis only when the choice changes the work materially; for a clear
+  implementation task, proceed with one answer. (fixture: `daf-requested-variations`.)
+- **Variation floors.** When the user asks to explore, produce **two to three
+  meaningfully different** options along the stated axis — different *decisions*,
+  not the same layout recoloured. When the user asks for one production answer,
+  produce one; no decorative option spam. (fixtures: `daf-requested-variations`,
+  `daf-unwanted-variations`.)
+- **Canvas / exploration contract (host-neutral).** Presenting side-by-side
+  concepts: give each a **stable frame label**, keep frames flat (no nested
+  cards), use generous spacing, and — on tools with a canvas — export-safe
+  coordinates so the layout survives export. Same labelled-frames shape whether
+  the host has a real canvas or just stacked sections.
+- **Cost / UX tie-breaker.** Ask about the axis only when it changes the work
+  materially; otherwise choose a strong default and **document the axis used in
+  the handoff** ("explored along visual-direction; density held constant").
+
+Hand off the actual variation **mechanics** — the basic→bold method and the
+single-file tweak-panel (CSS custom properties + floating "Tweaks" panel +
+`localStorage`) — to [`design-variations`](../design-variations/SKILL.md): this
+section owns the *planning decision*, that skill owns the *execution*.
 
 ## Cross-task design memory — read DESIGN.md / PRODUCT.md first
 

package/dist/agent-src/skills/fe-design/evals/triggers.json

@@ -0,0 +1,47 @@
+{
+    "skill": "fe-design",
+    "last_eval": "2026-07-10",
+    "description": "5 should-trigger + 5 should-not-trigger queries for the variation & canvas planning layer (road-to-design-artifact-fidelity Phase 4). Should-trigger covers exploration / variation planning and UI-design decisions where fe-design plans BEFORE generating (give me directions, explore, plan the flow, pattern choice). Should-not-trigger covers near-misses that must NOT invoke design planning: pure implementation of an already-selected design (apply-step), inventorying existing UI (existing-ui-audit), a surgical one-line edit, and non-UI/backend work.",
+    "queries": [
+        {
+            "q": "give me three directions for the pricing page",
+            "trigger": true
+        },
+        {
+            "q": "explore a few visual directions for the dashboard before we commit",
+            "trigger": true
+        },
+        {
+            "q": "design the multi-step onboarding flow",
+            "trigger": true
+        },
+        {
+            "q": "should this filter be a modal or an inline panel?",
+            "trigger": true
+        },
+        {
+            "q": "plan the responsive layout for the settings screen",
+            "trigger": true
+        },
+        {
+            "q": "implement the selected checkout design in React exactly as approved",
+            "trigger": false
+        },
+        {
+            "q": "what form components do we already have in the codebase?",
+            "trigger": false
+        },
+        {
+            "q": "change the primary button colour to green",
+            "trigger": false
+        },
+        {
+            "q": "add a database index on orders.status",
+            "trigger": false
+        },
+        {
+            "q": "fix the failing unit test in the auth module",
+            "trigger": false
+        }
+    ]
+}

package/dist/agent-src/skills/forecasting/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "forecasting",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "reconcile-topdown-bottomup",
+      "prompt": "Top-down says $30M ARR, bottom-up commit sums to $8.1M for Q1. Build the forecast call.",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "confidence"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "States the construction shape (top-down/bottom-up/hybrid) and attaches a confidence band; when they diverge, the divergence IS the forecast — not either single number."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/fundraising-narrative/evals/domain-truth.json

@@ -0,0 +1,16 @@
+{
+  "skill": "fundraising-narrative",
+  "domain": "founder",
+  "_note": "Rubric domain-truth fixture (road-to-domain-soundness Phase 2, rubric target). The criterion names a CITED EXTERNAL practice/standard — NOT the skill's own output (blocker: domain-competence-for-answer-keys, option a). Authored as a maintainer-RATIFICATION CANDIDATE: rubric is NON-deterministic (pinned-judge known-limit); the Phase-3 run + --write-floor ratchet-pin + per-domain backed-CLAIMS remain the maintainer's gate.",
+  "cases": [
+    {
+      "id": "matches-venture-pitch-arc",
+      "scenario": "Draft the fundraising narrative for our seed round.",
+      "source": "The standard venture seed-pitch narrative arc (problem -> why-now -> insight/solution -> traction -> team -> ask), the widely-taught pitch-structure convention.",
+      "check": {
+        "kind": "rubric",
+        "criterion": "Matches the standard venture pitch arc: problem, why-now, insight/solution, traction evidence, team, and a specific ask; surfaces the key risk and issues NO invest/raise verdict (finance safety floor) - not a feature list or an unopposed hype narrative."
+      }
+    }
+  ]
+}

package/dist/agent-src/skills/fundraising-narrative/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "fundraising-narrative",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "raise-narrative",
+      "prompt": "Draft the fundraising narrative for our seed round.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Builds a narrative around traction + why-now + why-us with a stated ask; surfaces the risk, does not issue a raise/don't-raise verdict (finance safety floor)."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/html-deck/SKILL.md

@@ -24,6 +24,12 @@ letterbox to any viewport. A deck is fixed-canvas media (default 1920×1080,
 
 ## When to use
 
+> **Cross-surface handoff.** A deck often consumes upstream analysis
+> (spreadsheet → deck, research → deck). Read the handoff envelope from
+> [`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md#cross-surface-handoff-envelope):
+> trust `verification_already_done` (don't recompute the source's numbers),
+> carry the asset list, and keep source restrictions intact.
+
 - The user asks for a deck, presentation, slides, or a pitch as a web/HTML
   deliverable.
 
@@ -32,6 +38,27 @@ one-off) → [`canvas-design`](../canvas-design/SKILL.md). Responsive product
 UI → [`fe-design`](../fe-design/SKILL.md) + stack executor. Multiple styled
 options of one screen → [`design-variations`](../design-variations/SKILL.md).
 
+## Deck fidelity floor
+
+The deck surface's floor (per
+[`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md)):
+
+- **Outline before slides.** Draft the slide outline (title + one-line intent
+  per slide) before building any slide; when audience or tone is ambiguous, ask
+  once. (fixture: `ssac-deck-missing-notes`.)
+- **Labels + speaker notes.** Every slide carries a stable label and speaker
+  notes, not just on-slide text.
+- **Visual rhythm + readable scale.** Consistent spacing/hierarchy across
+  slides; never sub-readable text (the type floors below). (fixture:
+  `ssac-tiny-slide-text`.)
+- **Image/asset provenance.** Real assets via the project path, no invented
+  brand evidence ([`design-fidelity`](../../rules/design-fidelity.md) § Asset &
+  imagery discipline).
+- **Export verification.** Verify the deck exports/renders
+  ([`design-artifact-verification`](../../../docs/contracts/design-artifact-verification.md));
+  on a host without export capability, say what could not be verified rather
+  than claiming a clean export.
+
 ## Procedure
 
 1. **Discovery.** Confirm: audience (engineers / executives / customers —

package/dist/agent-src/skills/iconography/SKILL.md

@@ -51,6 +51,30 @@ execution:
 5. **Verify** — check the resolved name on `iconify.design/icon/{set}:{name}`;
    confirm the icon renders as expected before shipping.
 
+## Iconography floor (design fidelity)
+
+Before resolving any new icon, honour the project's existing icon system — the
+Inspect stage of the
+[design-artifact lifecycle](../../../docs/contracts/design-artifact-lifecycle.md).
+
+- **Inspect first.** Detect the icon set already in use (imports, existing
+  `set:name` usages, brand assets) before picking one. A new icon matches the
+  incumbent set's **stroke weight, fill style, corner radius, size, and
+  metaphor** — do not introduce a second visual language (see
+  [`icon-consistency`](../../rules/icon-consistency.md)).
+- **No emoji-as-icon in serious UI.** An emoji is not an icon — never substitute
+  `⚙️`/`🔔`/`✅` for a real icon in a product/admin/marketing surface (functional
+  CLI/status markers are a different context, out of scope here).
+- **No hand-rolled icons when a set exists.** If the project has an icon library
+  or brand mark, use it — do not hand-author a one-off SVG that drifts from the
+  system. Hand-rolling is for a genuinely missing glyph, and then it matches the
+  set's grid + stroke.
+- **Flag substitutions when the exact asset is absent.** When the needed icon or
+  brand mark does not exist in the set, pick the nearest and **state the
+  substitution** ("no exact 'sync' glyph in Heroicons; used `arrow-path`") rather
+  than silently approximating or inventing. (fixtures: `daf-emoji-as-icon`,
+  `daf-fake-svg-logo`.)
+
 ## Output format
 
 1. **Iconify name** — `set:name` string, e.g. `lucide:arrow-right`.

package/dist/agent-src/skills/incident-commander/evals/domain-truth.json

@@ -0,0 +1,16 @@
+{
+  "skill": "incident-commander",
+  "domain": "ops",
+  "_note": "Rubric domain-truth fixture (road-to-domain-soundness Phase 2, rubric target). The criterion names a CITED EXTERNAL practice/standard — NOT the skill's own output (blocker: domain-competence-for-answer-keys, option a). Authored as a maintainer-RATIFICATION CANDIDATE: rubric is NON-deterministic (pinned-judge known-limit); the Phase-3 run + --write-floor ratchet-pin + per-domain backed-CLAIMS remain the maintainer's gate.",
+  "cases": [
+    {
+      "id": "matches-ics-sre-incident-practice",
+      "scenario": "Production checkout is failing for all users. Coordinate the incident from declaration to mitigation.",
+      "source": "Incident Command System (ICS — FEMA/NIMS) + Google SRE incident management ('SRE Workbook', Incident Response): declared severity, distinct IC/comms/ops roles, comms cadence, mitigation-before-root-cause.",
+      "check": {
+        "kind": "rubric",
+        "criterion": "Matches ICS / SRE incident-management practice: declares a severity level, assigns distinct Incident-Commander / communications / ops-lead roles, sets an external comms cadence, and drives mitigation before root-cause — not ad-hoc firefighting or a single-person response."
+      }
+    }
+  ]
+}

package/dist/agent-src/skills/incident-commander/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "incident-commander",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "coordinate-incident",
+      "prompt": "Production is down — checkout is failing for all users. Coordinate the incident.",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "sever"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Declares a severity, assigns IC/comms/ops roles, sets a comms cadence, and drives to mitigation-before-root-cause — matches a named IC practice."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/launch-readiness/evals/evals.json

@@ -0,0 +1,21 @@
+{
+  "skill": "launch-readiness",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "launch-go-no-go",
+      "prompt": "Are we ready to launch this feature to production?",
+      "assertions": [
+        {
+          "kind": "finding_floor",
+          "n": 3,
+          "pattern": "(?m)^\\s*[-*+]\\s+"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Surfaces blast radius, rollback path, and observability/monitoring as explicit gates; a missing gate blocks go."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/logging-monitoring/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "logging-monitoring",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "add-logging-endpoint",
+      "prompt": "Add logging to this login endpoint so we can debug failures.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Logs allowlisted structured fields (user_id, request_id, outcome) — never the raw request/credential/PII; the credential never reaches the log stream."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/messaging-architecture/evals/domain-truth.json

@@ -0,0 +1,16 @@
+{
+  "skill": "messaging-architecture",
+  "domain": "content",
+  "_note": "Rubric domain-truth fixture (road-to-domain-soundness Phase 2, rubric target). The criterion names a CITED EXTERNAL practice/standard — NOT the skill's own output (blocker: domain-competence-for-answer-keys, option a). Authored as a maintainer-RATIFICATION CANDIDATE: rubric is NON-deterministic (pinned-judge known-limit); the Phase-3 run + --write-floor ratchet-pin + per-domain backed-CLAIMS remain the maintainer's gate.",
+  "cases": [
+    {
+      "id": "matches-message-house-model",
+      "scenario": "Design the messaging architecture for our product launch.",
+      "source": "The message-house framework (one core message -> supporting pillars -> proof points per pillar) + positioning-before-messaging (Dunford, 'Obviously Awesome').",
+      "check": {
+        "kind": "rubric",
+        "criterion": "Matches the message-house model: exactly one core message, a small set of supporting pillars, and concrete proof points under each pillar, grounded in a NAMED target audience - not a flat list of slogans or adjectives."
+      }
+    }
+  ]
+}

package/dist/agent-src/skills/messaging-architecture/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "messaging-architecture",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "design-messaging",
+      "prompt": "Design the messaging architecture for our product.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Produces a layered message hierarchy (core → pillars → proof) grounded in a named audience, not generic slogans."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/perf-feedback-craft/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "perf-feedback-craft",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "perf-review-feedback",
+      "prompt": "Give this engineer performance feedback: they ship fast but skip tests.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Names the specific behaviour + its impact with an example, is balanced (strength + growth), and gives an actionable next step — not vague praise/blame."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/pest-testing/SKILL.md

@@ -56,6 +56,7 @@ discipline, mock-isolation gates, and the 12 process rationalizations
 - Keep setup minimal and relevant.
 - Favor confidence and maintainability over excessive mocking.
 - Cover happy path, validation failures, authorization failures, and important edge cases.
+- Enumerate the cases BEFORE writing — run the [`test-case-discovery`](../test-case-discovery/SKILL.md) funnel; floor per behavior: 1 happy + 1 boundary + 1 error (+1 abuse on security paths).
 
 ## TDD workflow (Red-Green-Refactor)
 
@@ -291,7 +292,6 @@ When generating Pest tests:
 - assert both response and side effects where relevant
 - keep tests readable, isolated, and maintainable
 
-
 ### Filter Pest output
 
 When triaging a verbose run, narrow the output with `--filter` (Pest)

package/dist/agent-src/skills/playwright-testing/SKILL.md

@@ -13,6 +13,11 @@ packs:
 
 ## When to use
 
+> **Design verification.** When exercising a UI artifact, run the
+> [design-artifact verification checklist](../../../docs/contracts/design-artifact-verification.md#verification-checklist)
+> (open → console/load → viewport → text-fit → assets → interaction) and capture
+> evidence; a design task with browser capability present is not "done" without it.
+
 Use this skill when:
 - Writing end-to-end tests with Playwright
 - Automating browser interactions for testing
@@ -31,6 +36,7 @@ Use this skill when:
 3. **Check existing tests** — match patterns in `tests/e2e/` or `e2e/`.
 4. **Check test utilities** — look for page objects, fixtures, helpers.
 5. **Check CI setup** — how are E2E tests run in the pipeline?
+6. **Enumerate the cases** — run the [`test-case-discovery`](../test-case-discovery/SKILL.md) funnel per user flow before writing specs; cover the happy flow AND at least one boundary (empty state, max input) and one error path (failed request, validation rejection) per flow — never the happy flow alone.
 
 ## Test structure
 
@@ -183,6 +189,12 @@ jq '.suites[].specs[] | select(.tests[].results[].status=="failed")' pw.json
 rg --color=never 'getByRole.*Submit' test-results/
 ```
 
+**Run verification.** The test run's **exit code** is the pass/fail signal — `0`
+means every spec passed, non-zero means at least one failed. Read the **command
+output** (or the `--reporter=json` above) to **diagnose** the failing spec's
+**root cause**; do not blindly re-run hoping it turns green — a retry-until-pass
+is not a fix, and a flaky green hides the real defect.
+
 ## Avoiding flaky tests
 
 | Problem | Solution |
@@ -263,3 +275,7 @@ await page.route('**/api/users', route =>
 - Do NOT test implementation details — test user-visible behavior.
 - Do NOT put assertions in Page Objects — assertions belong in test files.
 - Do NOT commit `.only` — enforce via `forbidOnly: !!process.env.CI`.
+
+## Anti-bruteforce — diagnose before retry
+
+When a spec fails, do not retry blindly by re-running, swapping locators at random, or bumping timeouts until green. Diagnose the root cause first: open the trace viewer, inspect the failing locator's `aria` tree, identify the real reason (timing, locator, app state), then apply a targeted fix. Trial-and-error locator swaps mask flaky test design.

package/dist/agent-src/skills/prompt-engineering-patterns/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "prompt-engineering-patterns",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "apply-prompt-pattern",
+      "prompt": "Which prompting pattern should I use to get structured extraction from messy text, and why?",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Names a concrete pattern (e.g. schema-constrained/structured-output, few-shot) matched to the extraction task, with the trade-off — not a generic tips list."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/refine-prompt/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "refine-prompt",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "refine-a-prompt",
+      "prompt": "Improve this prompt: 'write good marketing copy'.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Adds role, concrete task, constraints, and success criteria; removes vague adjectives — a measurably tighter prompt, not a paraphrase."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/refine-ticket/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "refine-ticket",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "refine-ticket-dor",
+      "prompt": "Refine this ticket: 'make search better'.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Tightens to a bounded scope with acceptance criteria + a definition-of-ready; asks the one blocking question rather than guessing scope."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/release-comms/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "release-comms",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "write-release-note",
+      "prompt": "Write the release announcement for our v-next dashboard redesign.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Leads with user value + what changed, notes any migration/breaking step, and matches the product voice — not a raw changelog dump."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/rice-prioritization/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "rice-prioritization",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "rice-rank-three",
+      "prompt": "Prioritize these three features with RICE: A (reach 5000, impact 2, conf 80%, effort 3), B (reach 1000, impact 3, conf 100%, effort 1), C (reach 8000, impact 1, conf 50%, effort 5).",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "RICE"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Computes RICE = Reach×Impact×Confidence/Effort per item (A≈2667, B=3000, C=800) and ranks by the score, not by gut feel."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/runway-cognition/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "runway-cognition",
+  "_calibration": "Behavioural fixture (road-to-skill-eval-coverage Phase 2, default-surface). Deterministic assertions on a real output property where reliable; rubric pins the qualitative core as a known-limit (pass ratified in PR review, not a hidden judge). finding_floor n is a conservative floor, not a calibrated per-host number.",
+  "scenarios": [
+    {
+      "id": "runway-shape-and-decision",
+      "prompt": "We have $4.2M cash and burn $560k/month. How long do we have and what should we do?",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "runway"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Computes months-of-runway = cash/burn (≈7.5) AND frames raise/hold/cut-vs-grow as a shape against the org-stage band, not a single number."
+        }
+      ]
+    }
+  ]
+}