@event4u/agent-config 8.9.0 → 8.10.0

package/dist/agent-src/contexts/execution/orchestration-telemetry.md

@@ -26,7 +26,9 @@ v1 forward-compat rule on unknown fields).
   "dispatch_tokens": null,
   "session_tier": null,
   "escalated_from": null,
-  "verify_result_by_tier": null
+  "verify_result_by_tier": null,
+  "first_pass_success": null,
+  "escalated": null
 }
 ```
 
@@ -34,22 +36,24 @@ v1 forward-compat rule on unknown fields).
 
 | Field | Type | Meaning |
 |---|---|---|
-| `task_size_estimate` | int | Pre-dispatch estimate of the task's size (orchestrator's sizing heuristic). Counts only, no body. |
-| `spawn_count` | int | Subagents dispatched for this task. `0` → handled in-session. |
-| `tiers` | string[] | Model tiers dispatched to, one per spawn class (e.g. `["sonnet","opus"]`). Tier names only, no prompts. |
-| `token_delta` | int | Net token cost vs the in-session baseline. Positive = cost more; negative = saved. Counts only. |
-| `token_delta_provenance` | enum | `"measured"` from host-reported `usage` metadata (preferred); `"estimated"` when self-estimated from response length (mark always when host usage unavailable). |
-| `wall_clock_ms` | int | Dispatch wall-clock duration, milliseconds. |
+| `task_size_estimate` | int | Pre-dispatch estimate of the task's size (the orchestrator's sizing heuristic). Counts only, no body. |
+| `spawn_count` | int | Number of subagents dispatched for this task. `0` → handled in-session. |
+| `tiers` | string[] | Model tiers dispatched to, one entry per spawn class (e.g. `["sonnet","opus"]`). Tier names only, no prompts. |
+| `token_delta` | int | Net token cost of the dispatch versus the in-session baseline. Positive = orchestration cost more; negative = saved tokens. Counts only. |
+| `token_delta_provenance` | enum | `"measured"` when sourced from host-reported `usage` metadata (preferred); `"estimated"` when self-estimated from response length (mark always when host usage is unavailable). |
+| `wall_clock_ms` | int | Wall-clock duration of the dispatch, milliseconds. |
 | `outcome` | enum | One of `DONE` · `DONE_WITH_CONCERNS` · `NEEDS_CONTEXT` · `BLOCKED` · `killed`. |
-| `verify_mode` | enum | How output was verified: `deterministic` · `judge` · `none`. |
-| `verdict_changed_outcome` | bool \| null | **A3 extension (ADR-109 Track A).** For a review/verdict subagent (e.g. `production-validator`): did the verdict change the outcome vs the in-session baseline? `true` = caught a real issue the baseline missed / flipped a false `READY`→`NOT READY`; `false` = no lift; `null` = not a verdict dispatch / not measured. **Negative-control (clean single-file) tasks MUST record `false`** — a `true` on a control = spurious findings, fails Gate A. Additive field on THIS object, not a second schema. Boolean/counts only, no bodies. |
+| `verify_mode` | enum | How the dispatch's output was verified: `deterministic` · `judge` · `none`. |
+| `verdict_changed_outcome` | bool \| null | **A3 extension (ADR-109 Track A).** For a review/verdict subagent (e.g. `production-validator`): did the subagent's verdict actually change the outcome versus the in-session baseline? `true` = it caught a real issue the baseline missed or flipped a false `READY`→`NOT READY`; `false` = same outcome as baseline (no lift); `null` = not a verdict dispatch / not measured. **Negative-control tasks (a clean single-file task) MUST record `false`** — a subagent that reports `true` on a control is producing spurious findings and fails Gate A. This is an additive field on THIS object, not a second schema. Counts/boolean only, no bodies. |
 | `task_class` | string \| null | **Routing extension (road-to-cost-aware-model-routing Phase 0).** Category id of the dispatched slice (e.g. `read-only-fanout`, `mechanical-edit`, `implementation`, `review-synthesis`). Enum-style id only, never free-form task text. `null` = pre-extension line / unclassified. |
 | `tier_chosen` | string \| null | Tier the slice was dispatched on (`lite` \| `medium` \| `high`). `null` = pre-extension line. |
 | `tier_source` | enum \| null | Where `tier_chosen` came from: `static` (frontmatter/category pin) · `inferred` (deterministic per-slice inference) · `inherit` (session tier — no downshift decision). Lets the evidence gate score inferred routing separately from static pinning. |
-| `escalated_from` | string \| null | When the slice re-dispatched after a verification failure: tier of the FAILED attempt (e.g. `lite` when a lite return failed verify and the slice re-ran on `medium`). `null` = no escalation. |
-| `verify_result_by_tier` | object \| null | Map tier → verification result per attempt of this slice (e.g. `{"lite":"fail","medium":"pass"}`). Values: `pass` \| `fail` \| `skipped`. Feeds the per-tier verify-pass-rate tripwire. Enums only, no verdict bodies. |
+| `escalated_from` | string \| null | When the slice was re-dispatched after a verification failure: the tier of the FAILED attempt (e.g. `lite` when a lite return failed verify and the slice re-ran on `medium`). `null` = no escalation. |
+| `verify_result_by_tier` | object \| null | Map of tier → verification result for every attempt of this slice (e.g. `{"lite":"fail","medium":"pass"}`). Values: `pass` \| `fail` \| `skipped`. Feeds the per-tier verify-pass-rate tripwire. Enums only, no verdict bodies. |
 | `dispatch_tokens` | int \| null | **Cost-% extension.** Absolute tokens the dispatched slice consumed (measured subagent usage). Feeds the MODELED cost-% in `orchestration_savings_report`, which needs an absolute base the token-count delta lacks. `null` = not recorded. Counts only. |
 | `session_tier` | string \| null | **Cost-% extension.** The orchestrator's OWN tier — the baseline the downshift cost-% measures `tier_chosen` against (a `high`→`lite` downshift is a rate win the token count can't see). `null` = not recorded. |
+| `first_pass_success` | bool \| null | **QUALITY extension (council verdict: quality × cost paired).** `true` = the subagent return was adopted without parent rework; `false` = the parent had to rework the return before adopting. `null` = pre-extension line / not measured. Boolean only, no bodies. |
+| `escalated` | bool \| null | **QUALITY extension (council verdict: quality × cost paired).** `true` = the slice was retried on a higher tier after a verification failure; `false` = no escalation. `null` = pre-extension line / not measured. Boolean only, no bodies. |
 
 These routing + cost fields are additive and optional — a line without them is
 still a valid orchestration line; readers ignore unknown fields per the v1
@@ -74,49 +78,58 @@ object is an additive extension on an otherwise standard audit-log-v1 line:
 
 After every auto-dispatched orchestration run, the orchestrating agent writes one
 telemetry line to `agents/runtime/state/audit/YYYY-MM.jsonl` (the existing
-audit-log-v1 path; `YYYY-MM` = current UTC month). The line is a standard
-audit-log-v1 object with `input_kind: "orchestration"` and an `orchestration`
-sub-object carrying this shape.
+audit-log-v1 path, where `YYYY-MM` is the current UTC month). The line is a
+standard audit-log-v1 object with `input_kind: "orchestration"` and an
+`orchestration` sub-object carrying this shape.
 
-**No hook or daemon required.** The agent writes the line directly —
-no-runtime-compatible capture path (decided 2026-06-30, maintainer decision; see
-`road-to-subagent-value-realization.md § Council notes`). Do NOT hand-author the
-JSON: run the recorder, which validates + builds a conformant line from the
-counts you already have:
+**No hook or daemon required.** The agent writes the line directly — the
+no-runtime-compatible capture path (decided 2026-06-30, maintainer decision;
+see `road-to-subagent-value-realization.md § Council notes`). Do NOT
+hand-author the JSON: run the recorder, which validates the inputs and builds a
+conformant audit-log-v1 line from the counts you already have:
 
 ```bash
 ./scripts-run src/scripts/orchestration_record --spawn-count <n> \
   --token-delta <±n> --provenance measured|estimated \
   [--tier-chosen lite|medium|high] [--tier-source static|inferred|inherit] \
-  [--task-class <id>] [--tiers a,b] [--dispatch-outcome DONE|BLOCKED|…]
+  [--task-class <id>] [--tiers a,b] [--dispatch-outcome DONE|BLOCKED|…] \
+  [--first-pass-success true|false] [--escalated true|false]
 ```
 
-A capture **hook** is the wrong tool: the PostToolUse payload carries no subagent
-token usage (only the orchestrator sees it) and a hook reverses the 2026-06-30
-no-hook decision. Reader: `src/scripts/orchestration_savings_report.ts`.
+A capture **hook** is the wrong tool here: the PostToolUse payload carries no
+subagent token usage — only the orchestrator sees it (via the run result) — and
+a hook would reverse the 2026-06-30 no-hook decision. Reader:
+`src/scripts/orchestration_savings_report.ts`.
 
 **`token_delta` sourcing priority:**
 1. Host-reported: read `usage.output_tokens` (and `usage.input_tokens` if
-   available) from each subagent call's response metadata. Use the sum minus the
-   estimated single-agent baseline. Set `token_delta_provenance: "measured"`.
-2. Self-estimate fallback: host usage metadata unavailable → estimate from
+   available) from the response metadata of each subagent call. Use the sum
+   minus the estimated single-agent baseline. Set `token_delta_provenance:
+   "measured"`.
+2. Self-estimate fallback: if host usage metadata is unavailable, estimate from
    response length (chars / 4 ≈ tokens). Set `token_delta_provenance:
-   "estimated"`. Lossy; measured always preferred.
+   "estimated"`. This estimate is lossy; measured is always preferred.
 
 ## Savings report
 
-Aggregate accumulated telemetry into a token-savings report:
+Aggregate the accumulated telemetry into a token-savings report:
 
 ```bash
 ./scripts-run src/scripts/orchestration_savings_report [--dir <path>] [--format text|json]
 ```
 
-Sums `token_delta` across dispatches (negative = net saved); splits by
-provenance (measured vs estimated), `tier_chosen`, `task_class`. Reports
-**ABSOLUTE net tokens saved, never a percentage**: telemetry records net delta,
-not the absolute in-session baseline → "% of session saved" not derivable. A
-percentage needs an additive absolute-baseline field (deferred follow-up).
-Reader: [`src/scripts/_lib/orchestration_savings.ts`](../../../../src/scripts/_lib/orchestration_savings.ts).
+It sums `token_delta` across dispatches (negative = net saved) and splits by
+provenance (measured vs estimated), `tier_chosen`, and `task_class`. **Quality
+and cost render as PAIRED columns** (council verdict — never savings alone):
+`first_pass_success_rate` and `escalation_rate` aggregate over the lines that
+carry the quality booleans; with ≥ 20 such lines in the window the real rates
+render beside the savings figures, below 20 the quality columns render as
+`n/a (n=<count>)`. It reports
+**ABSOLUTE net tokens saved, never a percentage**: the telemetry records net
+delta, not the absolute in-session baseline, so a "% of session saved" is not
+derivable from this data. A percentage would require an additive
+absolute-baseline field on this object (deferred follow-up). Reader:
+[`src/scripts/_lib/orchestration_savings.ts`](../../../../src/scripts/_lib/orchestration_savings.ts).
 
 ## Related
 

package/dist/agent-src/rules/design-fidelity.md

@@ -88,6 +88,46 @@ redesign.
 - Treating an internal "honesty gate" or "stub" concern as licence to redesign the UI.
 - Re-running a redesign after the user already said "match the prototype".
 
+## Surgical visual edits
+
+A request to change one visual thing — a colour, a label, a single element — is
+a **targeted edit**, not a redesign licence. Apply the same
+[`minimal-safe-diff`](minimal-safe-diff.md) discipline to design work that
+backend edits have always owed.
+
+- **Change only the semantic target.** Preserve the surrounding layout,
+  spacing, typography, dimensions, content, animation, and interaction states.
+  Do not rewrite the component, reflow the section, or "modernise" neighbours
+  while you are in there. (fixtures: `daf-edit-preservation`, `daf-unwanted-variations`.)
+- **A broader redesign needs an explicit trigger.** Only phrases like *"new
+  direction"*, *"from scratch"*, *"make it feel premium"*, *"rework the flow"*,
+  or *"give me variations / options"* license a from-scratch rework. Absent such
+  a phrase, a "fix / change / update the X" request is surgical — when unsure
+  which, ask ([`ask-when-uncertain`](ask-when-uncertain.md)). (fixture: `daf-redesign-trigger`.)
+- **Preserve stable anchors.** Where the host exposes DOM/comment metadata, keep
+  comment anchors and screen labels intact so the edit stays locatable. Where
+  the host has no such surface, preserve stable semantic anchors already present
+  in source comments / `data-*` attributes — never strip them, and do not invent
+  new ones.
+
+## Asset & imagery discipline
+
+Visual artifacts carry **real assets or honest placeholders — never fabricated
+brand evidence**. The design-surface instance of the no-invented-facts floor.
+
+- **Copy owned assets through the project's accepted path.** Reference or copy
+  project-owned assets (logos, icons, fonts, images) via the target project's
+  asset directory/pipeline — never hotlink a design-system's internal URL, never
+  bulk-copy a huge source folder. (fixtures: `daf-missing-asset`, `daf-external-asset-url`.)
+- **Real imagery where inspection matters.** On visual pages/decks, use actual
+  product / place / object / state imagery where the image IS the proof (a
+  product screenshot, a real dashboard state). Decorative atmosphere is not proof
+  — never pass a stock-like or invented image off as the real product. An
+  invented product screenshot is fabricated evidence. (fixture: `daf-invented-screenshot`.)
+- **Icons follow the iconography floor** — no emoji-as-icon in serious UI, no
+  hand-rolled icon when a set exists; see
+  [`iconography`](../skills/iconography/SKILL.md) § Iconography floor.
+
 ## See also
 
 - [`brand-source-of-truth`](brand-source-of-truth.md) / [`brand-consistency`](brand-consistency.md) — same precedence shape, for registered brand tokens.

package/dist/agent-src/rules/spreadsheet-source-quality.md

@@ -0,0 +1,61 @@
+---
+type: "auto"
+tier: "2a"
+description: "Financial data in a spreadsheet uses official sources first (IR, regulatory filings); aggregator/news/social figures need explicit permission + a cell-level unofficial mark"
+triggers:
+  - keyword: "financial data"
+  - keyword: "financial model"
+  - keyword: "stock price"
+  - keyword: "revenue figures"
+  - keyword: "market data"
+  - phrase: "pull the numbers"
+workspaces:
+  - finance
+packs:
+  - finance-basic
+---
+
+# Spreadsheet Source Quality
+
+A financial figure is only as trustworthy as its source. A number typed into a
+cell from an aggregator, a news headline, or a social post — entered as if it
+were official — is a sourcing defect even when the number is right, because the
+next reader cannot tell provenance from precision.
+
+## The Iron Law
+
+```
+FINANCIAL DATA USES OFFICIAL SOURCES FIRST.
+AN AGGREGATOR / NEWS / SOCIAL FIGURE IS NEVER ENTERED AS OFFICIAL —
+IT NEEDS EXPLICIT USER PERMISSION AND A CELL-LEVEL "UNOFFICIAL" MARK.
+EVERY SOURCED CELL CARRIES ITS SOURCE.
+```
+
+## Source priority (highest first)
+
+1. **Company investor relations** — the company's own IR site / filings.
+2. **Regulatory filings** — SEC (10-K/10-Q/8-K), or the equivalent exchange /
+   regulator filing in the jurisdiction.
+3. **Official reports / transcripts / earnings decks** — first-party.
+4. **Exchange / regulator data** — the exchange or regulator's own feed.
+
+Aggregators, financial-news sites, analyst blogs, and social posts are **below
+the floor**: use them only with the user's explicit permission, and mark the
+cell unofficial (a cell comment: `unofficial — <source>, verify`).
+
+## When it fires
+
+Entering, updating, or charting **financial figures** in a spreadsheet / model.
+
+## When NOT to fire
+
+- Non-financial data (a product's own event counts, internal ops numbers the
+  user supplies) — no official-source obligation, but a source comment still helps.
+- The user explicitly supplied the figures — trust the user's input; note the
+  provenance they gave.
+
+## See also
+
+- [`spreadsheet-authoring`](../skills/spreadsheet-authoring/SKILL.md) — the spreadsheet surface floor this rule's sourcing discipline plugs into.
+- [`surface-agent-contracts`](../../docs/contracts/surface-agent-contracts.md) — the spreadsheet surface's invariants + truth source.
+- [`finance-safety-floor`](finance-safety-floor.md) — the finance-pack advisory floor (not-investment-advice, sensitivity) this complements.

package/dist/agent-src/skills/accessibility-auditor/evals/evals.json

@@ -0,0 +1,15 @@
+{
+  "skill": "accessibility-auditor",
+  "_calibration": "Behavioural fixtures (road-to-skill-eval-coverage Phase 2, rich set). Deterministic `contains` asserts a real WCAG audit property (the standard is cited); finding_floor n=2 is a conservative floor (an icon-button with no name + a placeholder-only input surface ≥2 issues), not a calibrated per-host number; the rubric names the specific missing control as a pinned-judge known-limit.",
+  "scenarios": [
+    {
+      "id": "audit-icon-button-and-placeholder-input",
+      "prompt": "Audit this UI for accessibility and list each issue as its own bullet point:\n```html\n<button onclick=\"save()\"><svg width=\"16\" height=\"16\"></svg></button>\n<input type=\"text\" placeholder=\"Email address\">\n```",
+      "assertions": [
+        { "kind": "finding_floor", "n": 2, "pattern": "(?m)^\\s*[-*+]\\s+" },
+        { "kind": "contains", "value": "WCAG" },
+        { "kind": "rubric", "criterion": "Names the icon-only button's missing accessible name (aria-label / visible label) AND the placeholder-not-a-label problem on the input." }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/analysis-skill-router/evals/evals.json

@@ -0,0 +1,13 @@
+{
+  "skill": "analysis-skill-router",
+  "_calibration": "Behavioural fixtures (road-to-skill-eval-coverage Phase 2, router set). Deterministic `contains` asserts the router picks the NARROWEST matching project-analysis-* skill (the whole routing contract) — a mis-route names the wrong or a generic skill.",
+  "scenarios": [
+    {
+      "id": "route-laravel-slow-queries",
+      "prompt": "Analyze why our Laravel app's database queries are slow. Which analysis skill should handle this?",
+      "assertions": [
+        { "kind": "contains", "value": "project-analysis-laravel" }
+      ]
+    }
+  ]
+}

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

@@ -20,7 +20,7 @@ contract validation, response structure checks, or external service mocking.
 
 1. **Understand the endpoint** — Read the controller, form request, and existing tests. Understand expected behavior, edge cases, and auth requirements before writing anything.
 2. **Set up test data** — Use seeders (preferred) or factories. Mock external services with `Http::fake()`.
-3. **Write test cases** — Cover success, validation errors, authorization failures, edge cases.
+3. **Enumerate test cases** — Run the [`test-case-discovery`](../test-case-discovery/SKILL.md) funnel first; cover success, validation errors, authorization failures, and edge cases — floor per behavior: 1 happy + 1 boundary + 1 error (+1 abuse case; on data-returning endpoints the three `broken-access-control` negative tests are mandatory).
 4. **Assert response** — Check status code, JSON structure, data values. Use `assertJsonStructure()`.
 5. **Verify** — Run the test. Must pass. Check no flaky assertions (no time-dependent, no random ordering).
 
@@ -155,6 +155,8 @@ expect($data['title'])->toBeString();
 expect($data['total'])->toBeString(); // Money as string, not float
 ```
 
+### Filter noisy responses
+
 When a failing test dumps the full JSON body, narrow the diagnosis with `jq` or `grep`
 instead of scrolling the whole payload:
 
@@ -193,6 +195,10 @@ it('handles external API failure gracefully', function () {
 | **Side effects** | Database changes, events dispatched, jobs queued |
 | **Edge cases** | Empty results, large payloads, concurrent access |
 
+## Bridge to UI verification
+
+API tests cover the contract layer. When an endpoint feeds a UI surface (Livewire component, Blade-rendered page, SPA route), complement the API test with a thin UI probe: a `livewire test` for wired components, or a Playwright spec / browser `screenshot` for the rendered shell. Never assume the UI works just because the API test is green.
+
 ## Output format
 
 1. Pest test file covering happy path, validation, auth, and edge cases
@@ -220,3 +226,11 @@ it('handles external API failure gracefully', function () {
 - Do not skip auth tests — always test both authenticated and unauthenticated.
 - Do not assert entire JSON responses — assert only meaningful fields.
 - Do not use `Http::fake()` without also testing the real integration path.
+
+## Anti-bruteforce — diagnose before retry
+
+When a test fails, do not retry blindly with tweaked assertions until something passes. Diagnose the root cause first: print the actual response shape once, compare it to the contract, then write a targeted fix. Trial-and-error retries hide real regressions.
+
+## Clarification guard — ambiguous contract → ask
+
+If the endpoint contract is ambiguous (unclear status code, optional fields, error envelope shape), do not assume. Ask the user or check the OpenAPI spec / route definition before writing assertions — never guess the response shape from the route name.

package/dist/agent-src/skills/character-consistency/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "character-consistency",
+  "_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": "keep-character-consistent",
+      "prompt": "Keep this recurring character consistent across a multi-scene story.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Pins a character bible (traits, voice, visual anchors) and checks each scene against it, flagging drift — not re-inventing per scene."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/command-routing/evals/evals.json

@@ -0,0 +1,14 @@
+{
+  "skill": "command-routing",
+  "_calibration": "Behavioural fixtures (road-to-skill-eval-coverage Phase 2, router set). Deterministic `contains` asserts the invocation routes to the matching command (its file/path) rather than improvising — a mis-route runs the wrong command or reinvents it.",
+  "scenarios": [
+    {
+      "id": "route-create-pr",
+      "prompt": "I typed /create-pr — what runs, and which command file governs it?",
+      "assertions": [
+        { "kind": "contains", "value": "create-pr" },
+        { "kind": "rubric", "criterion": "Routes to the create-pr command file (commands/pr/create) and follows it rather than improvising a PR-creation flow." }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/dashboard-design/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "dashboard-design",
+  "_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-metrics-dashboard",
+      "prompt": "Design a metrics dashboard for our SaaS ops team.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Leads with the decisions the viewer must make, groups metrics by that, uses the right chart per data shape, and avoids vanity metrics."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/dcf-modeling/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "dcf-modeling",
+  "_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": "dcf-terminal-value-and-sensitivity",
+      "prompt": "DCF this target: year-6 FCFF $108M, WACC 10%, terminal growth 2%, net debt $200M. Give enterprise + equity value and the discount-rate sensitivity.",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "WACC"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Computes Gordon terminal value = FCFF_{n+1}/(WACC−g) = 108/0.08 = 1350, bridges EV→equity via net debt, and includes a WACC/terminal-growth sensitivity grid — never a single point estimate."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/decision-record/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "decision-record",
+  "_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": "record-adr",
+      "prompt": "Record our decision to adopt Postgres over MySQL as an ADR.",
+      "assertions": [
+        {
+          "kind": "contains",
+          "value": "Consequences"
+        },
+        {
+          "kind": "rubric",
+          "criterion": "Uses the ADR shape — Status / Context / Decision / Consequences / Alternatives — and states the trade-off given up, not only the choice."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/design-intelligence/evals/evals.json

@@ -0,0 +1,14 @@
+{
+  "skill": "design-intelligence",
+  "_calibration": "Behavioural fixtures (road-to-skill-eval-coverage Phase 2, rich set). Deterministic `contains` asserts the WCAG-checked-token property the skill promises; the rubric (pinned-judge known-limit) checks the corpus-grounding — a grounded brief names a concrete style/palette/type decision, not arbitrary taste.",
+  "scenarios": [
+    {
+      "id": "grounded-brief-fintech-dashboard",
+      "prompt": "Give me a grounded design brief (style, color tokens, typography, layout pattern) for a serious fintech analytics dashboard. Justify the palette's contrast.",
+      "assertions": [
+        { "kind": "contains", "value": "WCAG" },
+        { "kind": "rubric", "criterion": "Selects a concrete named style/archetype + a specific palette and type pairing grounded in the design corpus (not arbitrary), and states at least one anti-pattern to avoid." }
+      ]
+    }
+  ]
+}

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

@@ -13,6 +13,12 @@ packs:
 
 ## When to use
 
+> **Render-verification gate.** A UI verdict is gated on the
+> [design-artifact verification checklist](../../../docs/contracts/design-artifact-verification.md#verification-checklist):
+> where render capability exists, do not pass a design task without render
+> evidence (checklist steps 1–5); where it is absent, scope the verdict to what
+> was statically checked and say so — never "looks good" without evidence.
+
 Use this skill when:
 - Reviewing pull requests with UI changes
 - Auditing frontend components for design quality

package/dist/agent-src/skills/design-system-capture/SKILL.md

@@ -276,6 +276,27 @@ Fidelity declaration is load-bearing: hi-fi vs lo-fi tells the dev whether to
 recreate the mockup pixel-for-pixel or apply the existing system — the single
 most common handoff ambiguity.
 
+## Design-system extraction floor
+
+When the goal is to extract this repo's design system as a **reusable package
+artifact** (not just DESIGN.md prose), the extraction meets this floor — the
+handoff shape emitted alongside `design-system.json`
+([import contract](reference/design-system-json.md)).
+
+- **Contract contents.** A complete extraction carries: a root guide / manifest;
+  token CSS (or the stack's equivalent); the typography / colour / spacing /
+  iconography foundations; component specimens; an asset inventory (logos, icons,
+  fonts); UI-kit screens; and starting-point templates where appropriate.
+- **Specimen granularity.** Many small foundation cards beat one dense dump —
+  each specimen demonstrates ONE reusable sub-concept (a single button state,
+  one spacing step, one elevation level), so a consumer lifts concepts
+  individually rather than parsing a monolith.
+- **Developer handoff bundle** (extends § Design→dev handoff README): a
+  high-fidelity reference, behaviour notes, the assets list, the component
+  mapping (design name → code component), responsive states, known caveats, and
+  — when the artifact is a mock — an explicit "prototype, not production code"
+  warning so a consumer never ships the reference verbatim.
+
 ## Gotcha
 
 - **Over-writing instead of diff-updating** — the most common failure.

package/dist/agent-src/skills/design-system-capture/evals/evals.json

@@ -0,0 +1,15 @@
+{
+  "skill": "design-system-capture",
+  "_calibration": "Behavioural fixtures (road-to-skill-eval-coverage Phase 2, rich set). Deterministic `contains` asserts the two artifacts the skill's contract maintains (DESIGN.md + PRODUCT.md); the rubric checks it captures decisions rather than re-describing generic guidance.",
+  "scenarios": [
+    {
+      "id": "capture-from-repo",
+      "prompt": "Capture this project's design system so future sessions stay consistent: it uses a 4px spacing grid, 8px radius, a spring motion strategy, and a blue primary. Where do these decisions go?",
+      "assertions": [
+        { "kind": "contains", "value": "DESIGN.md" },
+        { "kind": "contains", "value": "PRODUCT.md" },
+        { "kind": "rubric", "criterion": "Routes the visual decisions (spacing/radius/motion/color) into DESIGN.md and interaction patterns into PRODUCT.md, and flags any TBD rather than inventing values." }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/developer-like-execution/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "developer-like-execution",
+  "_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": "execute-like-dev",
+      "prompt": "Implement this small change end-to-end the way a senior would.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Reads before editing, keeps the diff minimal + scoped, updates downstream callers/tests, and verifies with a real run before claiming done."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/doc-coauthoring/SKILL.md

@@ -13,6 +13,12 @@ packs:
 
 ## When to use
 
+> **Cross-surface handoff.** When this document consumes upstream work (research
+> → document, spreadsheet → report), read the handoff envelope from
+> [`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md#cross-surface-handoff-envelope):
+> trust `verification_already_done`, honour source restrictions, and don't
+> re-fetch what the source already grounded.
+
 Use this skill when:
 
 * User starts a substantial writing task — PRD, RFC, design doc, decision doc, technical spec, proposal
@@ -40,6 +46,27 @@ Move from a fuzzy ask to a complete document the user owns, by:
 * `save-file` and `str-replace-editor` available
 * Target path and filename agreed up front
 
+## Document format & export floor
+
+The document surface's floor (per
+[`surface-agent-contracts`](../../../docs/contracts/surface-agent-contracts.md)):
+
+- **Choose the format by intent.** Markdown vs `.docx` vs PDF follows what the
+  user will DO with it — when a named format is requested, produce THAT format
+  via the document tooling; never silently substitute markdown for a `.docx`
+  request. (fixture: `ssac-docx-requested-markdown-only`.)
+- **Preserve edit scope.** On an edit, change only what was asked and preserve
+  the rest of the document (mirrors
+  [`minimal-safe-diff`](../../rules/minimal-safe-diff.md)).
+- **Print/PDF preserves selectable text.** Never rasterize a text-heavy document
+  to an image-only PDF when browser print or native export keeps the text
+  selectable. (fixture: `ssac-pdf-screenshot-rasterized`.)
+- **Verify the output opens/exports.** Confirm the generated file opens /
+  round-trips
+  ([`design-artifact-verification`](../../../docs/contracts/design-artifact-verification.md));
+  where the format's tooling is absent, ship the source + say what could not be
+  verified rather than claiming a produced file.
+
 ## Procedure
 
 ### 0. Inspect existing material

package/dist/agent-src/skills/doc-coauthoring/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "doc-coauthoring",
+  "_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": "coauthor-prd",
+      "prompt": "Help me write the PRD for our new onboarding flow.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Runs the 3-stage flow — context → section-by-section → reader-test — rather than dumping a full doc; asks for the missing context first."
+        }
+      ]
+    }
+  ]
+}

package/dist/agent-src/skills/editorial-calendar/evals/domain-truth.json

@@ -0,0 +1,16 @@
+{
+  "skill": "editorial-calendar",
+  "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-content-pillar-practice",
+      "scenario": "Plan a content calendar for next quarter for our developer-tools blog.",
+      "source": "The content-pillar + audience-goal-cadence editorial-planning practice (standard content strategy).",
+      "check": {
+        "kind": "rubric",
+        "criterion": "Matches the content-pillar practice: themes tied to a named audience + a stated goal, an explicit publishing cadence, and pieces sequenced with dependencies - not a random list of topics."
+      }
+    }
+  ]
+}

package/dist/agent-src/skills/editorial-calendar/evals/evals.json

@@ -0,0 +1,16 @@
+{
+  "skill": "editorial-calendar",
+  "_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": "plan-content-calendar",
+      "prompt": "Plan a content calendar for next quarter for our dev-tools blog.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Grounds cadence + themes in a named audience + goal, sequences pieces with dependencies, not a random topic list."
+        }
+      ]
+    }
+  ]
+}

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

@@ -0,0 +1,16 @@
+{
+  "skill": "estimate-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": "estimate-ticket",
+      "prompt": "Estimate this ticket: add CSV export to the reports page.",
+      "assertions": [
+        {
+          "kind": "rubric",
+          "criterion": "Estimates from decomposed work + named unknowns/risks; gives a range or points, and does NOT invent a wall-clock duration."
+        }
+      ]
+    }
+  ]
+}