@event4u/agent-config 9.7.0 → 9.9.0

package/dist/agent-src/skills/gated-reach/evals/triggers.json

@@ -0,0 +1,72 @@
+{
+    "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/history-design/SKILL.md

@@ -0,0 +1,101 @@
+---
+model_tier: medium
+name: history-design
+description: "Use when choosing HOW to record change history / audit trails — walks the tier matrix (columns → audit log → temporal → event sourcing). Triggers on 'wer hat was wann', 'audit log'."
+domain: engineering
+workspaces:
+  - engineering
+packs:
+  - history-discipline
+trust:
+  level: professional
+install:
+  default: false
+  removable: true
+---
+
+# history-design
+
+## When to use
+
+- A model/table is declared audit-scoped ("we need to know who changed
+  what and when") and the mechanism must be chosen — NOT assumed.
+- The user asks for an audit trail, change history, activity log, or
+  proposes event sourcing.
+- NOT for reviewing an existing migration diff (route to
+  `schema-review`) and NOT for privacy/DSR policy design (route to
+  `privacy-review`; this skill only wires the interlock).
+
+## Procedure
+
+1. **Collect the requirement facts** (ask ONE question only if missing):
+   who edits the data (single editor vs multi-tenant), compliance need
+   (GDPR/SOC2/audit), point-in-time query need, replay/projection need,
+   expected mutation volume.
+2. **Walk the tier matrix — normative, cheapest-sufficient wins:**
+
+   | Tier | Mechanism | Use when | Growth control |
+   |---|---|---|---|
+   | 0 | `updated_at`/`updated_by` columns | single-editor, no compliance need | none needed |
+   | 1 | Row-level audit log (Laravel: spatie/activitylog or owen-it/laravel-auditing; TS: thin custom audit table) | admin panels, SaaS tenant data, "wer hat was wann geändert" | retention policy REQUIRED | <!-- md-language-check: ignore -->
+   | 2 | DB temporal/system-versioned tables | point-in-time queries needed, DB supports it | partition rotation |
+   | 3 | Event sourcing | domain genuinely event-driven, replay/projection needed | snapshotting + archive REQUIRED |
+
+   **Default tier: 1.** Tier 3 requires an explicit architecture waiver
+   from the user — never "upgrade" to event sourcing unprompted.
+3. **Apply the four interlocks to the chosen tier:**
+   - **Hygiene (R-B3):** audit storage indexed on
+     `(auditable_type, auditable_id, created_at)`; store JSON diffs, not
+     full-row copies, where a diff suffices.
+   - **Growth (R-A7):** the audit table itself declares retention (TTL,
+     pruning job, partition rotation, or archive path) — history must
+     not re-create the unbounded-growth problem it documents.
+   - **Privacy (R-B4):** audit records inherit the deletion/
+     anonymization obligations of the data they describe — a GDPR
+     Art. 17 path must exist before the mechanism ships.
+   - **Reliability (R-B5):** audit capture is same-transaction (Tier-1
+     default: observer + cheap single insert — allowed request-path
+     work) OR outbox/afterCommit with a durable queue when offloaded. A
+     lossy audit trail is worse than none.
+4. **Emit the decision artifact** (Output below) and, when the tier
+   lands, hand implementation to the stack-native path (Laravel package
+   install + config, or the thin custom audit-table pattern for TS — no
+   dependency needed there).
+
+## Output
+
+The decision artifact MUST contain:
+
+1. **Tier decision line** — `Tier N — <mechanism>` plus the one-sentence
+   cheapest-sufficient justification.
+2. **Interlock checklist** — the four interlocks (hygiene, growth,
+   privacy, reliability) each with its concrete answer for this model,
+   not a bare checkmark.
+3. **Rejected-tier note** — one line on the nearest rejected tier and
+   why (usually why NOT event sourcing, or why Tier 0 is insufficient).
+
+## Gotcha
+
+- Tier-1 reference per stack — Laravel: **spatie/laravel-activitylog**
+  (source-level comparison 2026-07-27: age-based `activitylog:clean`
+  retention command maps directly onto the R-A7 growth budget; JSON diff
+  columns match R-B3 hygiene) with **owen-it/laravel-auditing** as the
+  forensic alternative (ip/url/user-agent/tags; count-based pruning);
+  TS/Node: the thin custom audit-table pattern, no dependency. Re-verify
+  the package pick against the project's framework version at decision
+  time.
+- Tier 2 (temporal tables) depends on the database: MariaDB/SQL Server
+  have system-versioned tables, vanilla MySQL and SQLite do not, and
+  Postgres needs an extension or trigger pattern — verify the actual
+  connector before recommending Tier 2.
+
+## Do NOT
+
+- Do NOT recommend event sourcing without an explicit architecture
+  waiver from the user — Tier 3 is an architecture, not an audit
+  mechanism.
+- Do NOT ship any tier without its retention/growth answer — an
+  unbounded audit table is an F7 defect by definition.
+- Do NOT copy full row snapshots into audit records when a diff
+  suffices — that is the denormalized-duplication failure (F4) applied
+  to history.

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

@@ -0,0 +1,17 @@
+{
+    "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/humanizer/SKILL.md

@@ -67,9 +67,9 @@ human voice there; don't inject personality or restructure.
 4. **Final rewrite** addressing the audit. Keep em/en dashes at or under
    ~2 per 500 words (density cap, not zero — house precedent CP1).
 5. **Verify mechanically** when runtime available:
-   `npx tsx src/scripts/detect_ai_tells.ts --stdin --fail` on final
-   draft. No runtime → step-3 audit is the fallback (degrade, don't
-   skip audit).
+   `npx tsx node_modules/@event4u/agent-config/src/scripts/detect_ai_tells.ts --stdin --fail`
+   on final draft. No runtime → step-3 audit is the fallback (degrade,
+   don't skip audit).
 6. **Deterministic self-check + factual-integrity guard.** Re-scan the
    final draft against the [`anti-aiisms.md`](references/anti-aiisms.md)
    self-validation thresholds (dash density, consecutive-staccato cap,

package/dist/agent-src/skills/image-analyser/SKILL.md

@@ -21,16 +21,17 @@ install:
 
 > Read a character image, extract **every** feature (face marks, per-location
 > tattoos incl. lettered text, exact hair split, per-eye colour, jewelry,
-> asymmetry), diff against the character's canon so drift is caught **before** it
-> ships. Output feeds [`image-creator`](../image-creator/SKILL.md) + the fidelity
-> loop. Schema + rubric + loop: [`canon-spec.md`](canon-spec.md).
+> asymmetry), and diff it against the character's canon so drift is caught
+> **before** it ships. Output feeds [`image-creator`](../image-creator/SKILL.md)
+> and the fidelity loop. Schema + rubric + loop: [`canon-spec.md`](canon-spec.md).
 
 ## When to use
 
 - "Analyse this image / character", "does this match the canon", "check
   character accuracy", "find what's wrong with this render".
-- Verify step of the fidelity loop (after `image-creator` generates).
-- Bootstrap a Canon Spec from an authoritative portrait (*image wins over text*).
+- As the verify step of the fidelity loop (after `image-creator` generates).
+- To bootstrap a Canon Spec from an authoritative portrait (the *image wins
+  over the text*).
 
 NOT for: scene/motion review (→ `video-director`), non-character art
 (→ `canvas-design`), cross-scene token locking (→ `character-consistency`,
@@ -39,7 +40,7 @@ which consumes this skill's output).
 ## Input
 
 - Image **path or public URL** (per the `vision-analyze` shape).
-- Optional: reference Canon Spec / character id (e.g.
+- Optional: a reference Canon Spec / character id (e.g.
   `agents/reference/ai-video/<project>/characters/<id>.json`) to diff against.
 - **Input gate** (per the `image-ocr` contract): refuse blurry / sub-resolution
   / unreadable inputs with a clear reason rather than guessing.
@@ -64,16 +65,16 @@ which consumes this skill's output).
    lives here, **never** written back onto the canon (Layer 1).
 6. **If a reference is given — diff + score** per the rubric: per-feature
    `match|partial|miss`, the **canon-breaking hard gate**, per-section scores,
-   advisory roll-up, `low`-confidence misses flagged `needs-better-image`
+   advisory roll-up, and `low`-confidence misses flagged `needs-better-image`
    (not a hard fail). Emit concrete correction directives per miss.
 
 ## The one rule that overrides everything
 
-**The image wins over the text.** Extracting from an authoritative portrait and
-the canon text disagrees → record what is *visible*. Verifying a candidate
-against the canon → the canon's `identity` is the truth. Never invent a feature
-the image does not show (per `direct-answers` — no invented facts); mark it
-`unverifiable` instead.
+**The image wins over the text.** When extracting from an authoritative portrait
+and the canon text disagrees, record what is *visible*. When verifying a
+candidate against the canon, the canon's `identity` is the truth. Never invent a
+feature the image does not show (per `direct-answers` — no invented facts); mark
+it `unverifiable` instead.
 
 ## Output format
 
@@ -119,3 +120,4 @@ agent's, in-session.
 - [`image-creator`](../image-creator/SKILL.md) — consumes the diff; the loop partner.
 - [`character-consistency`](../character-consistency/SKILL.md) — consumes the load-bearing token subset of the `identity` layer.
 - [`canon-spec.md`](canon-spec.md) — schema, rubric, fidelity loop.
+- [`screenshot-hygiene`](../screenshot-hygiene/SKILL.md) — reuses this skill's OCR text-read to detect sensitive data in a documentation screenshot before it ships.

package/dist/agent-src/skills/image-editing/SKILL.md

@@ -45,7 +45,7 @@ with governance applied before delivery. All adapters are scaffold-tier (dry-run
    write the edit prompt in the target provider's grammar. For inpaint, describe what
    fills the masked region. For variation, carry the original seed/ref-image path forward.
 5. **Invoke the adapter (dry-run today)** — run
-   `src/scripts/ai-image/adapters/<provider>.sh` with the assembled params including
+   `node_modules/@event4u/agent-config/src/scripts/ai-image/adapters/<provider>.sh` with the assembled params including
    the source image path and, for inpaint, the mask path. Validate the returned
    artifact path or dry-run confirmation. All adapters are `experimental`
    (scaffold-tier); no live editing occurs until a maintainer promotes the adapter
@@ -98,3 +98,4 @@ with governance applied before delivery. All adapters are scaffold-tier (dry-run
 - [`image-provider-routing`](../image-provider-routing/SKILL.md) — select the right provider before writing the prompt.
 - [`prompt-engineering-image`](../prompt-engineering-image/SKILL.md) — translate the edit brief into provider-specific prompt grammar.
 - [`image-likeness-and-rights`](../../rules/image-likeness-and-rights.md) — rights check before editing real-person likenesses or brand marks.
+- [`screenshot-hygiene`](../screenshot-hygiene/SKILL.md) — for redacting a documentation screenshot, use a deterministic opaque box/blur (never the lossy inpaint here).

package/dist/agent-src/skills/image-generation/SKILL.md

@@ -41,7 +41,8 @@ governance. All adapters are scaffold-tier (dry-run) until promoted to `stable`.
 4. **Reuse ref-image / seed for consistency** — if the brief is part of a series, carry
    the seed value or ref-image path forward. Seed reuse is the primary consistency lever;
    re-describing the subject each time is not.
-5. **Invoke the adapter (dry-run today)** — run `src/scripts/ai-image/adapters/<provider>.sh`
+5. **Invoke the adapter (dry-run today)** — run
+   `node_modules/@event4u/agent-config/src/scripts/ai-image/adapters/<provider>.sh`
    with the assembled params. Validate the returned artifact path or dry-run confirmation.
    All adapters are `experimental` (scaffold-tier); no live generation occurs until a
    maintainer promotes the adapter via `provider-lifecycle-discipline`.

package/dist/agent-src/skills/image-provider-routing/SKILL.md

@@ -25,7 +25,7 @@ promotion per `provider-lifecycle-discipline`.
 ## When to use
 
 - Choosing which image model fits a brief (logo, banner, photo, icon, general art).
-- Before calling any `src/scripts/ai-image/adapters/*.sh` adapter.
+- Before calling any `node_modules/@event4u/agent-config/src/scripts/ai-image/adapters/*.sh` adapter.
 - When the user asks "which image model should I use?" or "route this image job."
 
 ## Provider decision table
@@ -92,5 +92,5 @@ photoreal jobs go to Flux.
 
 - [`prompt-engineering-image`](../prompt-engineering-image/SKILL.md) — translate the brief into provider-specific prompt grammar.
 - [`provider-lifecycle-discipline`](../../rules/provider-lifecycle-discipline.md) — read lifecycle tier before any run.
-- `src/scripts/ai-image/adapters/` — the four adapter files and their header comments.
+- `node_modules/@event4u/agent-config/src/scripts/ai-image/adapters/` — the four adapter files and their header comments.
 - [`media-governance-routing`](../../rules/media-governance-routing.md) — rights / likeness policies before generation.

package/dist/agent-src/skills/launch-readiness/SKILL.md

@@ -89,7 +89,7 @@ report per [`docs/contracts/prelaunch-diagnostics.md`](../../../docs/contracts/p
 - **Questions section** — list the questions that would change the
   diagnosis; the next run converts them into evidence or findings.
 - Validate + verdict via
-  `./scripts-run src/scripts/prelaunch_diagnostics validate <report.json>`;
+  `npx tsx node_modules/@event4u/agent-config/src/scripts/prelaunch_diagnostics.ts validate <report.json>`;
   regression-gate against the committed baseline via
   `… diff <baseline> <current> --ci` (contract § 4–6).
 

package/dist/agent-src/skills/license-compliance-audit/SKILL.md

@@ -0,0 +1,161 @@
+---
+model_tier: medium
+name: license-compliance-audit
+description: "Run the offline (jscpd) and online (scanoss-py) similarity scanners on demand against a diff or path — the ONLY home of this repo's detection capability; no CI gate exists or ever ran it automatically"
+domain: engineering
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+---
+
+# license-compliance-audit
+
+Gate G0 (`road-to-provenance-and-license-governance`, Phase 0) measured both
+candidate similarity detectors against a frozen golden corpus and neither
+met the pre-registered bar for a CI gate. Council resolved (2026-07-28,
+Option A): **no `lint_code_provenance.ts` in any form — not even
+advisory.** This skill is the result: the scan capability that used to be a
+planned CI gate now exists only as something a human invokes deliberately,
+so every hit gets investigated *because* a human asked for it — never as a
+silent pipeline signal nobody reads.
+
+## When to use
+
+- Before merging a diff that looks suspiciously similar to something you've
+  seen elsewhere, or that a reviewer flagged.
+- During a periodic self-audit (e.g. the Phase-4 "run the full pipeline on
+  this repo" dogfood exercise).
+- A reviewer or the `origin: uncertain` self-flag from
+  [`code-provenance`](../../rules/code-provenance.md) names a residual-class
+  file worth a closer look.
+
+Do NOT use when:
+
+- You expect this to run automatically in CI — it does not, by explicit
+  council decision; nothing here is wired into any pipeline.
+- You expect a clean result to prove the code was not copied — it cannot;
+  see the scope bound below.
+- You already have a specific, known source to check against a specific
+  license — that's [`license-compliance-borrow-check`](../license-compliance-borrow-check/SKILL.md),
+  a targeted one-source check, not a corpus-wide scan.
+
+## Procedure
+
+1. **Inspect available tooling.** The offline layer (L-1) is always
+   available via `npx`:
+   ```bash
+   npx jscpd --version
+   ```
+   The online layer (L0) is optional — check whether it's installed and
+   reachable:
+   ```bash
+   scanoss-py --version   # or: pip show scanoss
+   ```
+   Offline-only is expected and fine in most environments — report it
+   honestly, not as a failure.
+2. **Run the offline scan (L-1)** against the target path or diff:
+   ```bash
+   npx jscpd <path> --min-tokens 25
+   ```
+   `--min-tokens 25` is the pre-registered shipping value — the best
+   false-positive-clean point of the S0.3 sweep
+   (`internal/bench/provenance/reports/baseline-2026-07-28.md`). Read every
+   reported clone pair as a **candidate**, never a verdict.
+3. **If L0 is reachable, run the fingerprint scan:**
+   ```bash
+   scanoss-py scan <path>
+   ```
+   Only WFP fingerprints leave the machine, never raw source (privacy by
+   construction, principle 7). If L0 is unreachable, rate-limited, or not
+   installed, report the result as `partial (offline)` explicitly — never
+   claim a full two-layer scan ran.
+4. **Investigate every hit manually.** For each match: is the matched file
+   already in `provenance/borrows.jsonl` (cleared)? Does it read like
+   independent convergence on a common algorithm shape, or an unattributed
+   real copy? Open both files side by side before deciding — a match id is
+   a starting point, not a conclusion.
+5. **Route unresolved hits.** A hit with no existing ledger entry and no
+   independent-convergence explanation routes to
+   [`license-compliance-borrow-check`](../license-compliance-borrow-check/SKILL.md)
+   to classify and draft the entry. Never clear a hit yourself by simply
+   deciding it's fine.
+6. **Report the scope bound alongside every result** (see below) — a clean
+   run means "nothing matched this KB/corpus at this sensitivity", never
+   "no copying happened".
+
+## What the measured numbers mean — and don't
+
+On the frozen synthetic corpus (`internal/bench/provenance/`, 36 files,
+content-sha256 `dbbc84a7…34bb3`):
+
+| layer | verbatim+rename recall | rename-only recall | false positives |
+|---|---:|---:|---:|
+| L-1 jscpd `--min-tokens 25` | 10/16 | 4/8 | 0/12 |
+| L0 scanoss | 4/16 | 0/8 | 2/12 |
+| **union (both layers)** | **12/16** | **4/8** | **2/12** |
+
+Full source: `internal/bench/provenance/reports/baseline-2026-07-28.md`.
+
+- **Scope bound:** the corpus is `synthetic-canonical` — independently
+  authored implementations of well-known algorithm shapes, never fetched or
+  pasted from any upstream file. This measures **transformation-depth
+  sensitivity and false-positive rate on independent code** — it does
+  **not** measure recall against SCANOSS's real-OSS knowledge base. No
+  sample here is indexed anywhere, so a KB lookup returning zero hits says
+  nothing about the detector's real-world recall. Real-KB recall is
+  unmeasured and would need a second, real-snippet corpus.
+- **Rename-only laundering is not reliably caught** — 0/8 (SCANOSS), 4/8
+  (jscpd). The provenance ledger, not this scan, is the anti-launder
+  control (see [`code-provenance`](../../rules/code-provenance.md)).
+- **No tool sees model training data.** Unconscious reproduction from
+  training data is not addressed by this scan at all, regardless of
+  outcome.
+
+## Output format
+
+1. Per scan target: which layer(s) actually ran, hit or clean, and — if
+   the online layer was unreachable — the explicit `partial (offline)`
+   marker (never a silent green presented as a full scan).
+2. For every hit: the matched file/snippet, a manual same-shape-vs-real-copy
+   judgment, and the routing decision (already ledgered / route to
+   `license-compliance-borrow-check` / independent convergence, no action).
+3. The scope-bound paragraph from the section above, restated so the
+   requester never reads a clean result as a copying guarantee.
+
+## Gotcha
+
+- **A clean scan is not proof of originality.** It means "nothing matched
+  at this sensitivity, in this corpus/KB" — never "not copied from
+  training data".
+- **Rename-only copies routinely pass both layers.** Do not trust a clean
+  re-scan after a purely cosmetic rewrite as evidence of real
+  transformation.
+- **Both of SCANOSS's measured false positives came from independently
+  authored files** matching on convergent canonical-algorithm shape (MIT
+  snippet matches) — a hit is an investigation trigger, not an accusation.
+- **Nothing here is wired into CI.** A hit found by this skill never
+  blocked anything automatically; if you expected a pipeline signal, there
+  isn't one — that's the point of Gate G0's Option A resolution.
+
+## Do NOT
+
+- NEVER claim or imply this scan runs in CI — it explicitly does not, by
+  council decision (Gate G0, Option A).
+- NEVER report a scan as complete when the online layer was unreachable —
+  always say `partial (offline)`.
+- NEVER present a clean result as "provably not copied" — restate the
+  scope bound every time a result is shared.
+- NEVER clear a hit without either a ledger entry or a documented
+  independent-convergence judgment.
+
+## See also
+
+- [`code-provenance`](../../rules/code-provenance.md) — the rule that makes
+  the ledger, not this scan, the primary anti-launder control.
+- [`license-compliance-borrow-check`](../license-compliance-borrow-check/SKILL.md) —
+  where an unresolved hit routes for classification + ledger drafting.
+- `internal/bench/provenance/reports/baseline-2026-07-28.md` — the full
+  measured baseline this skill's numbers are drawn from.
+- `docs/CLAIMS.md` — claim `provenance-detector-transformation-sensitivity`
+  (unbacked, carries the same scope bound).

package/dist/agent-src/skills/license-compliance-audit/evals/triggers.json

@@ -0,0 +1,52 @@
+{
+    "skill": "license-compliance-audit",
+    "last_eval": "2026-07-28",
+    "description": "5 should-trigger + 5 should-not-trigger queries. Should-trigger covers running the on-demand jscpd/scanoss similarity scan on a diff or path, and asking whether a diff looks copied from known OSS. Should-not-trigger covers near-miss neighbours (a single named-source license check, notices regeneration, generic code review, dependency vetting) whose vocabulary overlaps.",
+    "queries": [
+        {
+            "q": "this diff looks suspiciously similar to something I've seen, run a similarity scan against known OSS",
+            "trigger": true
+        },
+        {
+            "q": "run jscpd and scanoss on this PR to check for copied code",
+            "trigger": true
+        },
+        {
+            "q": "do a self-audit of the whole repo for potential license violations",
+            "trigger": true
+        },
+        {
+            "q": "check whether this file matches anything in the SCANOSS knowledge base",
+            "trigger": true
+        },
+        {
+            "q": "the reviewer flagged this function as possibly lifted from elsewhere, scan for a match",
+            "trigger": true
+        },
+        {
+            "q": "I want to borrow this specific function from https://github.com/example/repo, check its license",
+            "trigger": false,
+            "note": "single named source, targeted license check → license-compliance-borrow-check"
+        },
+        {
+            "q": "regenerate the third-party notices file from the ledger",
+            "trigger": false,
+            "note": "notices regeneration → license-compliance-credits"
+        },
+        {
+            "q": "review this diff for null-safety and edge cases",
+            "trigger": false,
+            "note": "correctness review, not a similarity scan"
+        },
+        {
+            "q": "is this new npm package real or a hallucinated name?",
+            "trigger": false,
+            "note": "dependency existence check → supply-chain-intake"
+        },
+        {
+            "q": "set up a CI job that blocks merges on copied code",
+            "trigger": false,
+            "note": "no CI gate exists or is planned here — Gate G0 cancelled it; this skill is on-demand only"
+        }
+    ]
+}