@event4u/agent-config 14.11.0 → 14.13.0

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

@@ -1,29 +0,0 @@
-{
-  "skill": "forecasting",
-  "domain": "finance",
-  "_note": "Deterministic domain-truth keys computed independently from cited standard forecast-construction formulas (NOT the skill's own output). Authored as maintainer-ratification candidates per road-to-domain-soundness Phase 2 (blocker: domain-competence-for-answer-keys); the Phase-3 run + --write-floor ratchet-pin remain the maintainer's gate.",
-  "cases": [
-    {
-      "id": "bottom-up-commit",
-      "scenario": "Bottom-up forecast. Commit-tagged pipeline total = $8.1M; in-window segment close rate = 78%. Compute the commit value = commit-tagged pipeline x in-window close rate. State the single figure in $M to three decimals.",
-      "source": "Bottom-up forecast construction: commit = sum(commit-tagged pipeline) x in-window close rate (standard finance/RevOps forecasting).",
-      "check": {
-        "kind": "deterministic",
-        "expected": 6.318,
-        "tolerance": 0.01,
-        "rationale": "8.1 x 0.78 = 6.318 ($M). Step 1 bottom-up: sum commit-tagged x in-window close-rate per segment."
-      }
-    },
-    {
-      "id": "top-down-arr",
-      "scenario": "Top-down forecast. Total addressable market (TAM) = $4.2B; expected penetration = 0.6%. Compute the top-down ARR = TAM x penetration. State the single figure in $M.",
-      "source": "Top-down forecast construction: ARR = TAM x penetration band (x motion band) (standard market-sizing).",
-      "check": {
-        "kind": "deterministic",
-        "expected": 25.2,
-        "tolerance": 0.05,
-        "rationale": "4,200,000,000 x 0.006 = 25,200,000 = $25.2M. Step 1 top-down: TAM x penetration band."
-      }
-    }
-  ]
-}

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

@@ -1,20 +0,0 @@
-{
-  "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/forensics-report/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-    "skill": "forensics-report",
-    "last_eval": "2026-08-09",
-    "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers DE+EN phrasings for git-history release forensics (hotspot risk, change-coupling, release-review evidence). Should-not-trigger covers near-miss neighbours: security incident forensics (incident-commander), plain git log, runtime performance hotspots (performance-analysis), line blame, security audit.",
-    "queries": [
-        { "q": "which files are the riskiest hotspots in this release", "trigger": true },
-        { "q": "what files always change together", "trigger": true },
-        { "q": "run the forensics report for the release review", "trigger": true },
-        { "q": "zeig mir hotspot und coupling evidenz für das release", "trigger": true },
-        { "q": "machine-derived evidence for the release review", "trigger": true },
-        { "q": "do a forensic analysis of the security incident from last night", "trigger": false },
-        { "q": "show me the git log for the last week", "trigger": false },
-        { "q": "find the performance hotspots in production at runtime", "trigger": false },
-        { "q": "who wrote this line — run git blame on it", "trigger": false },
-        { "q": "run a security audit on the auth module", "trigger": false }
-    ]
-}

package/dist/agent-src/skills/frontend-render-security/evals/triggers.json

@@ -1,52 +0,0 @@
-{
-    "skill": "frontend-render-security",
-    "last_eval": "2026-07-09",
-    "description": "5 should-trigger + 5 should-not-trigger queries. Should-trigger covers DE + EN phrasings for client-side insecure-render / client-trust patterns (XSS, client secrets, client-only auth, CORS, localStorage tokens). Should-not-trigger covers near-miss neighbours (server-side security, generic checklist, accessibility-only, dependency intake) whose vocabulary overlaps.",
-    "queries": [
-        {
-            "q": "is it safe to render this user content with dangerouslySetInnerHTML?",
-            "trigger": true
-        },
-        {
-            "q": "review this Vue component for XSS and any secrets in the bundle",
-            "trigger": true
-        },
-        {
-            "q": "I'm storing the JWT in localStorage — is that ok?",
-            "trigger": true
-        },
-        {
-            "q": "prüf mein Frontend auf unsichere Render-Muster und Client-Secrets",
-            "trigger": true
-        },
-        {
-            "q": "my CORS is set to origin '*' with credentials — problem?",
-            "trigger": true
-        },
-        {
-            "q": "review this API controller's authorization logic",
-            "trigger": false,
-            "note": "server-side authz → authz-review / security-sensitive-stop"
-        },
-        {
-            "q": "what invisible controls did I omit across this whole diff?",
-            "trigger": false,
-            "note": "cross-surface checklist → ai-code-blindspots"
-        },
-        {
-            "q": "make this form accessible — keyboard nav and contrast",
-            "trigger": false,
-            "note": "accessibility only → accessibility-auditor"
-        },
-        {
-            "q": "is this frontend npm dependency real and safe to install?",
-            "trigger": false,
-            "note": "dependency intake → supply-chain-intake"
-        },
-        {
-            "q": "help me center this div with flexbox",
-            "trigger": false,
-            "note": "layout/styling — no security surface"
-        }
-    ]
-}

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

@@ -1,16 +0,0 @@
-{
-  "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

@@ -1,16 +0,0 @@
-{
-  "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/gated-reach/evals/triggers.json

@@ -1,72 +0,0 @@
-{
-    "skill": "gated-reach",
-    "last_eval": "2026-07-25",
-    "description": "6 should-trigger + 8 should-not-trigger queries. Should-trigger covers DE + EN phrasings for the two ship-tier intents only: reading a Reddit thread (text, and ranking/structure) and reading a single named tweet. Should-not-trigger is deliberately larger than the positive set: the parent bench found the native web tools already win on ordinary research, so this skill's main failure mode is over-triggering. Negatives cover general research, plain web pages, the parked YouTube channel, unsupported Twitter surfaces (timelines/search), and an unsupported platform — a trigger that fires only to decline is worse than no trigger.",
-    "queries": [
-        {
-            "q": "what does this reddit thread say? https://www.reddit.com/r/rust/comments/abc123/",
-            "trigger": true
-        },
-        {
-            "q": "which comment did people actually upvote in this reddit discussion?",
-            "trigger": true,
-            "note": "ranking intent — tier 2, the credential-free capability this roadmap shipped"
-        },
-        {
-            "q": "reddit.com wird von deinem web-tool abgelehnt — lies mir den Thread trotzdem vor",
-            "trigger": true
-        },
-        {
-            "q": "summarise the top comments and their scores on this r/programming post",
-            "trigger": true
-        },
-        {
-            "q": "what does this tweet say? https://x.com/somesmallaccount/status/1964428927159382261",
-            "trigger": true
-        },
-        {
-            "q": "x.com gibt 402 zurück — was steht in diesem Tweet?",
-            "trigger": true
-        },
-        {
-            "q": "research the current best practice for database connection pooling",
-            "trigger": false,
-            "note": "ordinary dev research — native web tools win 12/12 (parent bench null)"
-        },
-        {
-            "q": "fetch this blog post and summarise it",
-            "trigger": false,
-            "note": "plain web page — the host's own fetch handles it"
-        },
-        {
-            "q": "get me the transcript of this YouTube video",
-            "trigger": false,
-            "note": "youtube-transcripts is PARKED — backend absent by design; reach:doctor states it"
-        },
-        {
-            "q": "pull this user's recent twitter timeline",
-            "trigger": false,
-            "note": "no credential-free path to timelines — not a shipped intent"
-        },
-        {
-            "q": "search twitter for mentions of our product",
-            "trigger": false,
-            "note": "no credential-free path to search — not a shipped intent"
-        },
-        {
-            "q": "read this Weibo thread for me",
-            "trigger": false,
-            "note": "no prescription exists for CN platforms — declining is not a trigger"
-        },
-        {
-            "q": "what are the open issues on this GitHub repo?",
-            "trigger": false,
-            "note": "the github channel is a separate, already-working surface"
-        },
-        {
-            "q": "install yt-dlp for me so the youtube channel works",
-            "trigger": false,
-            "note": "the package never auto-installs — missing-tool-handling, not this skill"
-        }
-    ]
-}

package/dist/agent-src/skills/github-ci/evals/evals.json

@@ -1,25 +0,0 @@
-{
-  "skill": "github-ci",
-  "_calibration": "Seed for eval-schema v2 (ecosystem-harvest skill-quality-gates Phase 2). The requires_human scenario is skipped in CI and reported manual-pending — never a silent pass.",
-  "scenarios": [
-    {
-      "id": "fetches-real-ci-logs-not-guess",
-      "prompt": "The PR's Node Tests check is red. Diagnose why.",
-      "environment": "an open PR with a failing CI check",
-      "assertions": [
-        { "kind": "tool-choice", "must_use": ["bash"], "must_not_use": [] },
-        { "kind": "contains", "value": "log" }
-      ]
-    },
-    {
-      "id": "operator-confirms-rerun",
-      "prompt": "Re-run the failed CI job after the fix is pushed.",
-      "environment": "an open PR whose fix was just pushed",
-      "requires_human": true,
-      "human_instructions": "Confirm the agent fetched the real run id and did not fabricate a green result; verify the re-run was triggered against the actual failing job.",
-      "assertions": [
-        { "kind": "contains", "value": "run" }
-      ]
-    }
-  ]
-}

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

@@ -1,17 +0,0 @@
-{
-    "skill": "history-design",
-    "last_eval": "2026-07-27",
-    "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers DE+EN phrasings for choosing an audit/history mechanism (tier matrix). Should-not-trigger covers near-miss neighbours: migration review (schema-review), privacy/DSR policy (privacy-review), retention floors (domain-safety-retention), git history.",
-    "queries": [
-        { "q": "we need to track who changed what and when on tenant data", "trigger": true },
-        { "q": "wir brauchen eine Änderungshistorie — wer hat was wann geändert?", "trigger": true },
-        { "q": "should we use event sourcing for the orders domain?", "trigger": true },
-        { "q": "add an audit trail to the admin panel models", "trigger": true },
-        { "q": "which activity log package fits our Laravel app?", "trigger": true },
-        { "q": "review this migration for missing indexes", "trigger": false },
-        { "q": "how long may we keep support tickets under GDPR?", "trigger": false },
-        { "q": "squash my last three git commits into one", "trigger": false },
-        { "q": "anonymize user data on account deletion", "trigger": false },
-        { "q": "profile the slow audit report query in production", "trigger": false }
-    ]
-}

package/dist/agent-src/skills/html-deck/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "html-deck",
-  "last_eval": "2026-07-06",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers deck/slides/presentation/pitch builds in HTML. Should-not-trigger covers near-miss neighbors: canvas-design (posters/static art), fe-design (responsive UI), design-variations (options), PowerPoint-file requests, and content-only outline asks.",
-  "queries": [
-    {"q": "make a 10-slide deck for the investor pitch", "trigger": true},
-    {"q": "build a presentation from this PRD for the engineering all-hands", "trigger": true},
-    {"q": "turn these notes into HTML slides I can present tomorrow", "trigger": true},
-    {"q": "create a pitch deck with our brand colors, 16:9", "trigger": true},
-    {"q": "I need a slide presentation that also prints to PDF", "trigger": true},
-    {"q": "design a poster for the conference booth", "trigger": false, "note": "static one-frame art → canvas-design"},
-    {"q": "build the landing page hero section", "trigger": false, "note": "responsive UI → fe-design / stack executor"},
-    {"q": "show me 3 design options for this dashboard", "trigger": false, "note": "options → design-variations"},
-    {"q": "write an outline for my talk", "trigger": false, "note": "content-only ask, no HTML deliverable"},
-    {"q": "export our Google Slides to PowerPoint", "trigger": false, "note": "file conversion, not an HTML deck build"}
-  ]
-}

package/dist/agent-src/skills/humanizer/evals/strip_fixtures.json

@@ -1,57 +0,0 @@
-{
-  "$comment": "Fixtures for stripCarrierUnicode (detect_ai_tells.ts). Six cases, reproduced offline against the real _classify export before the roadmap that added them was written. Every hidden codepoint is written as a JSON \\u escape and NEVER as a literal character: the first version of this file used literals, which (a) made the payloads invisible in review and (b) reddened lint_hidden_unicode with 20 blocking findings, since a tracked file carrying real carriers is exactly what that gate exists to refuse. JSON.parse decodes the escapes, so the test still receives the real characters at runtime.",
-  "recorded_limitation": {
-    "what": "The complex-script preservation cases are a CURATED BLOCK SET, not a Unicode Script-property lookup.",
-    "tested_blocks": [
-      "Arabic/Persian (U+0600-U+06FF)",
-      "emoji ZWJ sequences (U+1F400-U+1FAFF joined by U+200D)"
-    ],
-    "untested": "Indic (Devanagari, Bengali, Tamil, ...), Thai, Khmer, Myanmar, Mongolian, and every other script that uses a format character mid-word.",
-    "why_this_is_acceptable": "The predicate errs toward PRESERVATION: a carrier is removed only when both neighbours are ASCII, so a format character inside a non-ASCII word is preserved whatever its script. An untested script is therefore preserved rather than corrupted — the failure mode cannot occur in the unsafe direction. A full Script-property table would be a new data dependency guarding a failure that cannot happen.",
-    "what_would_change_this": "A script whose format characters legitimately appear between two ASCII characters. None is known; one would make the block set insufficient rather than merely untested."
-  },
-  "cases": [
-    {
-      "name": "ASCII-flanked zero-width space is removed",
-      "input": "the\u200bword",
-      "expect_out": "theword",
-      "expect_removed": 1,
-      "expect_preserved": 0
-    },
-    {
-      "name": "ASCII-flanked right-to-left override is removed",
-      "input": "safe\u202efile.txt",
-      "expect_out": "safefile.txt",
-      "expect_removed": 1,
-      "expect_preserved": 0
-    },
-    {
-      "name": "ASCII-flanked Unicode-tag codepoint is removed",
-      "input": "a\udb40\udc41b",
-      "expect_out": "ab",
-      "expect_removed": 1,
-      "expect_preserved": 0
-    },
-    {
-      "name": "emoji ZWJ sequence survives byte-identically",
-      "input": "👨\u200d💻 ships it",
-      "expect_out": "👨\u200d💻 ships it",
-      "expect_removed": 0,
-      "expect_preserved": 1
-    },
-    {
-      "name": "Persian ZWNJ survives byte-identically",
-      "input": "می\u200cخواهم",
-      "expect_out": "می\u200cخواهم",
-      "expect_removed": 0,
-      "expect_preserved": 1
-    },
-    {
-      "name": "clean prose is a no-op, and the strip is idempotent",
-      "input": "Nothing hidden here — just prose with an em dash.",
-      "expect_out": "Nothing hidden here — just prose with an em dash.",
-      "expect_removed": 0,
-      "expect_preserved": 0
-    }
-  ]
-}

package/dist/agent-src/skills/humanizer/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "humanizer",
-  "last_eval": "2026-07-11",
-  "description": "5 should-trigger + 5 should-not-trigger queries. Should-trigger covers de-slopping deliverable prose (EN + DE phrasings). Should-not-trigger covers the near-miss neighbors: brand-voice definition (voice-and-tone-design), chat-reply tone (direct-answers), voice-capture drafting (ghostwriter), translation, and plain shortening.",
-  "queries": [
-    {"q": "make this sound less like AI", "trigger": true},
-    {"q": "this post reads like ChatGPT wrote it, fix that", "trigger": true},
-    {"q": "humanize this draft", "trigger": true},
-    {"q": "remove the AI-isms from my article", "trigger": true},
-    {"q": "schreib das um, damit es nicht KI-generiert klingt", "trigger": true},
-    {"q": "define our brand voice", "trigger": false, "note": "routes to voice-and-tone-design (voice definition, not per-line editing)"},
-    {"q": "stop opening your replies with praise", "trigger": false, "note": "chat-reply tone — owned by direct-answers"},
-    {"q": "write a LinkedIn post in the style of a public figure", "trigger": false, "note": "routes to /ghostwriter:write (humanizer runs inside its step 4b, not standalone)"},
-    {"q": "translate this paragraph to German", "trigger": false, "note": "translation, not de-slopping"},
-    {"q": "shorten this paragraph to half the length", "trigger": false, "note": "compression, not tell removal"}
-  ]
-}

package/dist/agent-src/skills/iconography/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "iconography",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers icon resolution, set selection, and embedding tasks. Should-not-trigger covers near-miss neighbors: typography-system (font/type choices), design-tokens (CSS variable authoring), image-provider-routing (AI-generated images), and a generic draw-an-icon image-gen request.",
-  "queries": [
-    {"q": "which icon should I use for a download action in Lucide?", "trigger": true},
-    {"q": "add a warning icon to this component — we use Heroicons", "trigger": true},
-    {"q": "pick an icon set for our new React app", "trigger": true},
-    {"q": "wire Phosphor icons into our Blade templates", "trigger": true},
-    {"q": "resolve the Iconify name for a user-profile icon in Tabler", "trigger": true},
-    {"q": "pick a font pairing for our marketing page", "trigger": false, "note": "font/type selection → typography-system"},
-    {"q": "author CSS variables for our color palette", "trigger": false, "note": "token authoring → design-tokens"},
-    {"q": "which AI image model should I use for a product icon illustration?", "trigger": false, "note": "AI image generation routing → image-provider-routing"},
-    {"q": "draw me an icon for a mobile app in Midjourney", "trigger": false, "note": "image-gen request, not Iconify/UI icon resolution"},
-    {"q": "set up dark mode token overrides for our design system", "trigger": false, "note": "dark-mode token authoring → design-tokens"}
-  ]
-}

package/dist/agent-src/skills/image-analyser/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "image-analyser",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers the analyse / canon-diff / accuracy-check / drift-find / bootstrap-from-portrait paths (DE + EN). Should-not covers the near-miss neighbours whose vocabulary overlaps: scene/motion review (video-director), non-character art (canvas-design), cross-scene token lock (character-consistency), generation (image-creator), and document OCR (generic).",
-  "queries": [
-    {"q": "analyse this character image down to the last detail", "trigger": true},
-    {"q": "does img_2.png match the Charakterbuch canon?", "trigger": true},
-    {"q": "check this render for character accuracy — what drifted?", "trigger": true},
-    {"q": "vergleiche das Bild mit der Charakterbeschreibung, jedes Merkmal", "trigger": true},
-    {"q": "build a canon spec from this authoritative portrait", "trigger": true},
-    {"q": "turn this scene idea into a cinematic video prompt", "trigger": false, "note": "scene/motion → video-director"},
-    {"q": "design a poster for the band", "trigger": false, "note": "static non-character art → canvas-design"},
-    {"q": "lock this character's tokens so every scene reuses them", "trigger": false, "note": "cross-scene token lock → character-consistency"},
-    {"q": "generate Veikko in the forge scene to spec", "trigger": false, "note": "generation → image-creator"},
-    {"q": "extract the text from this scanned invoice", "trigger": false, "note": "plain document OCR, not character analysis"}
-  ]
-}

package/dist/agent-src/skills/image-creator/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "image-creator",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers generate/render/to-spec/loop-fix paths (DE + EN). Should-not covers near-miss neighbours: analysis (image-analyser), scene/motion (video-director, motion-choreographer), non-character art (canvas-design), and token-lock (character-consistency).",
-  "queries": [
-    {"q": "generate Veikko in the forge scene, matched to the canon", "trigger": true},
-    {"q": "render this character to spec, max detail", "trigger": true},
-    {"q": "create the image and make every tattoo placement exact", "trigger": true},
-    {"q": "erzeuge das Bild so detailgenau wie möglich nach der Vorlage", "trigger": true},
-    {"q": "regenerate with the heterochromia and hair-split fixed", "trigger": true},
-    {"q": "analyse this image and tell me what drifted", "trigger": false, "note": "analysis → image-analyser"},
-    {"q": "turn this still into a cinematic motion prompt for Veo", "trigger": false, "note": "motion → motion-choreographer"},
-    {"q": "expand this one-line idea into a scene blueprint", "trigger": false, "note": "scene → scene-expander/video-director"},
-    {"q": "design a tour poster", "trigger": false, "note": "static non-character art → canvas-design"},
-    {"q": "lock the character tokens so all scenes reuse them", "trigger": false, "note": "token lock → character-consistency"}
-  ]
-}

package/dist/agent-src/skills/image-editing/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "image-editing",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers inpainting, background replacement, colour variation, object removal, and targeted render modification. Should-not covers near-miss neighbours: greenfield image generation (image-creator/image-generation), provider selection (image-provider-routing), prompt writing (image-creator), rights/licence check (media governance).",
-  "queries": [
-    { "q": "edit the background of this product shot to a white studio setting", "trigger": true },
-    { "q": "inpaint the logo out of the upper-right corner of this image", "trigger": true },
-    { "q": "make a variation of this hero image in a warmer colour palette", "trigger": true },
-    { "q": "remove the person standing on the left side of the photo", "trigger": true },
-    { "q": "modify this existing render — I want the sky replaced with a sunset", "trigger": true },
-    { "q": "generate a new product shot from scratch — I have no existing image", "trigger": false, "note": "greenfield generation → image-creator / image-generation" },
-    { "q": "which image provider should I use for this job?", "trigger": false, "note": "provider routing → image-provider-routing" },
-    { "q": "create a logo for my company", "trigger": false, "note": "logo creation → logo-generation" },
-    { "q": "how do I write a good prompt for Ideogram?", "trigger": false, "note": "prompt engineering → image-creator" },
-    { "q": "do I need a rights check before using a celebrity's likeness in my image?", "trigger": false, "note": "likeness / rights → media governance rules" }
-  ]
-}

package/dist/agent-src/skills/image-generation/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "image-generation",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers end-to-end image generation requests (brief → render). Should-not-trigger covers near-miss neighbors: routing-only questions (image-provider-routing), prompt-writing-only (prompt-engineering-image), image editing (image-editing), logo-specific flows (logo-generation), and rights checks (image-likeness-and-rights).",
-  "queries": [
-    {"q": "generate an image of a product shot for our new coffee mug", "trigger": true},
-    {"q": "create a banner image for our bakery with the name on it", "trigger": true},
-    {"q": "I need an image generated for our website hero section", "trigger": true},
-    {"q": "produce a series of consistent character illustrations for our app onboarding", "trigger": true},
-    {"q": "generate a square social media image of a smiling barista", "trigger": true},
-    {"q": "which image model should I use for a logo with text?", "trigger": false, "note": "routing-only question → image-provider-routing"},
-    {"q": "write me an Ideogram prompt for this bakery banner brief", "trigger": false, "note": "prompt authoring only → prompt-engineering-image"},
-    {"q": "edit this photo to remove the background and add a sunset", "trigger": false, "note": "editing an existing image → image-editing"},
-    {"q": "create a vector SVG logo for our brand", "trigger": false, "note": "logo-specific flow → logo-generation"},
-    {"q": "can I use this celebrity's photo as a reference for my image prompt?", "trigger": false, "note": "rights / likeness check → image-likeness-and-rights"}
-  ]
-}

package/dist/agent-src/skills/image-provider-routing/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "image-provider-routing",
-  "last_eval": "2026-06-16",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers job-shape to provider matching. Should-not-trigger covers near-miss neighbors: writing the actual prompt (prompt-engineering-image), invoking the adapter directly, media policy checks (media-governance-routing), and general image editing without a routing question.",
-  "queries": [
-    {"q": "which image model should I use for a logo with text?", "trigger": true},
-    {"q": "route this image generation job — it needs a photorealistic product shot", "trigger": true},
-    {"q": "I need a vector SVG icon, what provider handles that?", "trigger": true},
-    {"q": "pick the right AI image provider for a bakery banner with the name on it", "trigger": true},
-    {"q": "should I use Ideogram or Flux for this image brief?", "trigger": true},
-    {"q": "write me an Ideogram prompt for this logo brief", "trigger": false, "note": "writing provider-specific prompt grammar → prompt-engineering-image"},
-    {"q": "run the recraft adapter with this prompt", "trigger": false, "note": "direct adapter invocation, not routing selection"},
-    {"q": "can I use a celebrity's face in this image?", "trigger": false, "note": "likeness / rights question → media-governance-routing / image-likeness-and-rights"},
-    {"q": "edit this existing photo to remove the background", "trigger": false, "note": "editing task, not a provider routing decision"},
-    {"q": "what lifecycle tier is the Flux adapter?", "trigger": false, "note": "lifecycle tier lookup → provider-lifecycle-discipline"}
-  ]
-}

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

@@ -1,16 +0,0 @@
-{
-  "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

@@ -1,20 +0,0 @@
-{
-  "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/js-library-packaging/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-    "skill": "js-library-packaging",
-    "last_eval": "2026-08-23",
-    "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers the publish ask, the runtime symptom whose cause is packaging (invalid hook call), the exports-map question, the workspace-range install failure, and a DE phrasing. Should-not-trigger covers the near-miss neighbours this skill is one word away from: authoring the component itself (ui-component-architect), the PHP twin (composer-packages), a commit-message question (conventional-commits-writing), a monorepo task-graph question, and a bundler performance question — none of which are package-surface work.",
-    "queries": [
-        { "q": "publish our ui package", "trigger": true },
-        { "q": "why does my hook say invalid hook call", "trigger": true },
-        { "q": "what should the exports map for this library look like?", "trigger": true },
-        { "q": "the install fails on a workspace: range after publishing", "trigger": true },
-        { "q": "wie veröffentliche ich unser Komponenten-Paket richtig?", "trigger": true },
-        { "q": "build me a Button component with a loading state", "trigger": false },
-        { "q": "how do I publish a composer package?", "trigger": false },
-        { "q": "write the commit message for this breaking change", "trigger": false },
-        { "q": "why is turbo rebuilding everything on every commit?", "trigger": false },
-        { "q": "our bundle is 400kb, what should I lazy-load?", "trigger": false }
-    ]
-}

package/dist/agent-src/skills/judge-artifact-completeness/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "judge-artifact-completeness",
-  "last_eval": "2026-06-27",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers scoring roadmaps, PR reviews, ADRs, and tickets for completeness (risk, tests, migration, AC, DoR). Should-not covers near-miss neighbours: code-quality review (judge-code-quality), bug hunting (judge-bug-hunter), test-file coverage (judge-test-coverage), security audit (judge-security-auditor), and creating an ADR from scratch (adr-create).",
-  "queries": [
-    { "q": "score this roadmap for completeness — does it cover risk, tests, and migration?", "trigger": true },
-    { "q": "does this PR review have enough evidence? is each finding traceable to a diff line?", "trigger": true },
-    { "q": "check if this ticket meets DoR — are the acceptance criteria verifiable?", "trigger": true },
-    { "q": "is this ADR complete? does it name alternatives and state consequences?", "trigger": true },
-    { "q": "what dimensions are missing from this roadmap — risk, maintainability, migration?", "trigger": true },
-    { "q": "review the naming and DRY violations in this diff", "trigger": false, "note": "code quality → judge-code-quality" },
-    { "q": "find the bugs introduced by this change", "trigger": false, "note": "bug hunting → judge-bug-hunter" },
-    { "q": "does this PR add enough test coverage for the new behaviour?", "trigger": false, "note": "test-file coverage → judge-test-coverage" },
-    { "q": "are there security issues in this authentication middleware?", "trigger": false, "note": "security → judge-security-auditor" },
-    { "q": "create an ADR for switching from REST to GraphQL", "trigger": false, "note": "ADR creation → adr-create, not scoring" }
-  ]
-}

package/dist/agent-src/skills/judge-injection-defense/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "judge-injection-defense",
-  "last_eval": "2026-06-27",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers scoring an agent's response to an injection / role-takeover / fake-boundary / obfuscated-instruction attempt on the defence axis. Should-not covers near-miss neighbours: artifact completeness (judge-artifact-completeness), code security-of-the-diff (judge-security-auditor), code correctness (judge-bug-hunter), authoring an injection-defense rule (rule-writing), and generic helpfulness scoring.",
-  "queries": [
-    { "q": "did the agent correctly refuse this role-takeover injection, or did it comply?", "trigger": true },
-    { "q": "score whether this response treated the untrusted block as data and ignored the fake boundary token", "trigger": true },
-    { "q": "the prompt tried to suppress the refusal — did the agent still emit the correct refusal?", "trigger": true },
-    { "q": "check if AC's defence held against this leetspeak-obfuscated instruction — data, not command?", "trigger": true },
-    { "q": "judge this response on injection defence: was any channel breached?", "trigger": true },
-    { "q": "is this roadmap complete — does it cover risk and tests?", "trigger": false, "note": "artifact completeness → judge-artifact-completeness" },
-    { "q": "are there injection vulnerabilities in this PR's input-handling code?", "trigger": false, "note": "code security-of-the-diff → judge-security-auditor" },
-    { "q": "find the null-safety bugs in this diff", "trigger": false, "note": "code correctness → judge-bug-hunter" },
-    { "q": "write a rule that defends against prompt injection", "trigger": false, "note": "authoring a rule → rule-writing" },
-    { "q": "how helpful and complete was this assistant's answer?", "trigger": false, "note": "helpfulness scoring — explicitly NOT this judge's axis" }
-  ]
-}

package/dist/agent-src/skills/judge-synthesis/evals/triggers.json

@@ -1,17 +0,0 @@
-{
-  "skill": "judge-synthesis",
-  "last_eval": "2026-06-28",
-  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers consolidating multiple already-run judge verdicts into one report (consensus, conflicts, must-fix). Should-not covers near-misses: producing a single judge verdict (the individual judges), dispatching judges (review-changes), code-only review, asking for a quality number, and running one judge.",
-  "queries": [
-    { "q": "consolidate these judge verdicts into one report — where do they agree and disagree?", "trigger": true },
-    { "q": "I ran the bug, security and artifact-completeness judges — synthesize the findings", "trigger": true },
-    { "q": "which findings did multiple judges flag, and what are the conflicts?", "trigger": true },
-    { "q": "merge the judge outputs into a must-fix / should-fix / advisory split with provenance", "trigger": true },
-    { "q": "give me one decision-ready report across all the judges that ran on this PR", "trigger": true },
-    { "q": "judge this diff for bugs", "trigger": false, "note": "single verdict → judge-bug-hunter" },
-    { "q": "self-review my changes before the PR", "trigger": false, "note": "dispatches the code judges → /review-changes" },
-    { "q": "score this roadmap for completeness", "trigger": false, "note": "single artifact verdict → judge-artifact-completeness" },
-    { "q": "give me one overall quality score for this PR", "trigger": false, "note": "opaque single number — explicitly forbidden by this skill" },
-    { "q": "run the security auditor on this code", "trigger": false, "note": "runs one judge → judge-security-auditor" }
-  ]
-}