@event4u/agent-config 6.0.0 → 7.0.0

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

@@ -0,0 +1,95 @@
+---
+model_tier: inherit
+name: image-generation
+description: "Generate an image from a brief — provider-agnostic blueprint then provider-specific translation, with ref-image/seed reuse for consistency. Use when generating/creating an image."
+domain: product
+personas: []
+workspaces:
+  - small-business
+packs:
+  - ai-image
+trust:
+  level: experimental
+install:
+  removable: true
+execution:
+  type: manual
+---
+
+# image-generation
+
+Generate an image end-to-end: capture the brief, route to the right provider, author
+a provider-specific prompt, reuse seeds for consistency, invoke the adapter, and apply
+governance. All adapters are scaffold-tier (dry-run) until promoted to `stable`.
+
+## When to use
+
+- User asks to generate, create, or produce an image from a brief.
+- End-to-end image production (routing + prompting + adapter invocation + governance).
+- When a consistent series of images needs seed/ref-image reuse across renders.
+
+## Procedure
+
+1. **Capture the brief** — extract: subject, output format (raster/vector/banner/icon),
+   style intent, any existing ref images or seed values for consistency.
+2. **Route the provider** via [`image-provider-routing`](../image-provider-routing/SKILL.md) —
+   match job shape (text-in-image → Ideogram, photoreal → Flux, vector → Recraft,
+   general → Gemini/GPT Image 2).
+3. **Author the prompt** via [`prompt-engineering-image`](../prompt-engineering-image/SKILL.md) —
+   apply provider-specific grammar (text-literal first for Ideogram, noun-phrase for Flux,
+   `style:` param for Recraft, natural language for Gemini/GPT).
+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`
+   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`.
+6. **Apply governance** — run the rights check (`image-likeness-and-rights`) when the
+   brief names a real person, brand mark, or living artist's style. Attach the AI-disclosure
+   footer per `media-governance-routing` before delivering the output.
+
+## Output format
+
+1. **Blueprint** — provider choice + routing rationale + prompt string ready to copy.
+2. **Provider + prompt** — adapter file reference, key params (aspect ratio, style,
+   negative prompts), and any seed/ref-image value carried forward.
+3. **Artifact path / dry-run note** — the path returned by the adapter, or an explicit
+   note: "adapter is experimental (scaffold-tier) — dry-run plan only; no rendered
+   asset until promotion per `provider-lifecycle-discipline`."
+
+## Gotcha
+
+- **Scaffold-tier adapters produce plans, not pixels** — all four adapters (`ideogram.sh`,
+  `flux.sh`, `recraft.sh`, `gemini-image.sh`) are **scaffold-tier** (dry-run only). This
+  skill produces the blueprint + dry-run confirmation; actual renders require a maintainer
+  to capture a smoke trace and promote the adapter to `stable`. Claiming a rendered asset
+  exists when no adapter is stable misleads the caller.
+- **Seed reuse is the consistency lever** — re-describing the subject more precisely
+  in each prompt does not lock character or style; carrying the seed value or ref-image
+  path forward does. Drop the seed and character drift is inevitable across a series.
+
+**Good example:** Brief for a product-shot series → route to Flux (photoreal), author
+noun-phrase prompt, carry `seed: 42` across all five renders, invoke adapter, note
+"experimental — dry-run plan only."
+
+**Bad example:** Invoking the adapter and telling the user "here is your rendered image"
+while all adapters are still scaffold-tier.
+
+## Do NOT
+
+- Do NOT claim a rendered asset is produced while adapters are scaffold-tier — surface
+  the dry-run caveat explicitly every time.
+- Do NOT skip `image-likeness-and-rights` when the brief names a real person, a brand
+  mark, or a named living artist's style.
+- Do NOT bypass `image-provider-routing` — selecting the wrong provider for the job
+  shape (e.g. Flux for a text-in-image logo) produces garbled output.
+- Do NOT ignore seed/ref-image values when consistency across a series is required —
+  seed reuse is the only reliable consistency mechanism.
+
+## See also
+
+- [`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 brief into provider-specific prompt grammar.
+- [`image-likeness-and-rights`](../../rules/image-likeness-and-rights.md) — rights check before generating real-person likenesses or brand marks.
+- [`provider-lifecycle-discipline`](../../rules/provider-lifecycle-discipline.md) — lifecycle tier gates; read before any adapter invocation.

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

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

@@ -0,0 +1,96 @@
+---
+model_tier: inherit
+name: image-provider-routing
+description: "Select the right image-generation provider from job shape — text-in-image to Ideogram, photoreal to Flux, vector/logo to Recraft, general to Gemini/GPT."
+domain: product
+personas: []
+workspaces:
+  - small-business
+packs:
+  - ai-image
+trust:
+  level: experimental
+install:
+  removable: true
+execution:
+  type: manual
+---
+
+# image-provider-routing
+
+Route an image generation job to the right provider based on job shape. Adapters
+are scaffold-tier (dry-run only) — selection produces a plan; execution waits on
+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.
+- When the user asks "which image model should I use?" or "route this image job."
+
+## Provider decision table
+
+| Job shape | Provider | Why |
+|---|---|---|
+| Text-in-image (logo, banner, typographic art) | **Ideogram** | Best glyph rendering; raster models garble text |
+| Photoreal (product shot, portrait, scene) | **Flux** | Photorealism specialist; routed via fal/Replicate |
+| Vector / SVG logo or icon | **Recraft** | Produces genuine `<path>` SVG; raster cannot |
+| General art / edit / multimodal | **Gemini-image** or **GPT Image 2** | Broad capability; natural-language prompts |
+| Budget-conscious 4K upscale | Flux via Replicate | Cost-competitive at high resolution |
+
+Decision order: text-in-image → Ideogram; must-be-vector → Recraft; photoreal → Flux;
+everything else → Gemini-image (default) or GPT Image 2 (when OpenAI key available
+and editing an existing image).
+
+## Procedure
+
+1. **Extract job shape** from the brief: does it need embedded text? vector output?
+   photorealistic rendering? or general illustration?
+2. **Apply table** — match the dominant shape to the provider row above.
+3. **Check lifecycle tier** — all adapters are `experimental` (scaffold). Surface
+   this before any live invocation.
+4. **Confirm with the user** when shape is ambiguous (e.g., logo that could be
+   vector OR raster typographic art → ask once).
+5. **Emit the routing decision** in the Output format below.
+
+## Output format
+
+1. **Chosen provider** — name + one-line rationale citing the job-shape match.
+2. **Lifecycle-tier caveat** — "adapter is experimental (scaffold tier); dry-run
+   only until a smoke trace is captured per `provider-lifecycle-discipline`."
+3. **Fallback** — if the primary adapter is unavailable or the smoke trace is
+   missing, name the next best provider and what changes.
+
+## Gotcha
+
+- **Routing a text-in-image job to a photoreal model is the #1 failure** — send a
+  logo/banner with embedded text to Flux and the text renders as garbled glyphs;
+  it must go to Ideogram. Likewise a vector logo sent to Ideogram/Flux returns a
+  raster PNG, not the editable `<path>` SVG a brand mark needs (→ Recraft).
+- All four adapters (`ideogram.sh`, `flux.sh`, `recraft.sh`, `gemini-image.sh`) are
+  **scaffold-tier** — dry-run plumbing only, no live generation yet. Routing
+  produces a selection + plan; actual API calls require promotion to `stable`
+  first (maintainer-captured smoke trace under `agents/reference/ai-image/smoke-traces/`).
+  Surfacing a provider without its `experimental` tier caveat misleads the caller
+  into expecting a rendered asset that won't come.
+
+**Good example:** "Text logo for a bakery → Ideogram (text-in-image); lifecycle:
+experimental — dry-run plan only."
+
+**Bad example:** "Use Recraft for the product photo" — Recraft is the vector path;
+photoreal jobs go to Flux.
+
+## Do NOT
+
+- Do NOT invoke an adapter without surfacing its lifecycle tier (all are `experimental`).
+- Do NOT route a text-in-image job to Flux — Flux has no glyph renderer; text garbles.
+- Do NOT route a vector/SVG job to Ideogram or Flux — neither outputs genuine `<path>` SVG.
+- Do NOT skip `image-likeness-and-rights` when the brief names a real person or brand mark.
+- Do NOT promote an adapter from `experimental` to `stable` — that is maintainer-only via smoke trace.
+
+## See also
+
+- [`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.
+- [`media-governance-routing`](../../rules/media-governance-routing.md) — rights / likeness policies before generation.

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

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

@@ -91,6 +91,27 @@ For each stage:
 Pre-mortem rule: every trip wire must answer *"what would have
 caused this in six hours?"* If you cannot, the trip wire is wrong.
 
+### 4b. Post-deploy verification fragments (manual checks, not an auto-canary)
+
+Right after deploy, the on-call runs these by hand — **checklist items, not an
+automated canary loop** (a real canary is a runtime, out of scope). Cheap "did
+the deploy silently break a thing that doesn't page" probes; include only those
+that apply:
+
+- **SSE / streaming heartbeat** — if the app serves SSE / a long-lived stream,
+  confirm a connection stays open + emits a heartbeat past the proxy's idle
+  timeout (a proxy/buffering config change silently kills streaming while every
+  other endpoint looks fine).
+- **Static-asset content-type drift** — fetch a built asset, assert its
+  `Content-Type` (JS as `*/javascript`, CSS as `text/css`); a CDN/build change
+  serving assets as `text/plain` breaks the browser but returns 200.
+- **LCP delta** — spot-check Largest-Contentful-Paint on the top route vs the
+  pre-deploy baseline; a regression past the agreed delta is a trip wire even
+  when no error fires.
+
+Each is a one-shot pass/fail an on-call can eyeball; failures feed the § 4 trip
+wires. Do not build a standing canary service for them.
+
 ### 5. Ops handoff
 
 - Who is paged on which alert (from **team** spine slot).

package/dist/agent-src/skills/learning-to-rule-or-skill/SKILL.md

@@ -58,6 +58,7 @@ Do not use this skill when:
 | An always-true constraint ("never X", "always Y") | **Rule** | Create/update rule |
 | A repeatable workflow with steps and validation | **Skill** | Create/update skill |
 | A coding convention or reference material | **Guideline** | Create/update guideline |
+| A reusable **fix/refactor recipe** for a specific problem (problem → before → after → verification) | **Pattern** | Create/update `src/patterns/<slug>.md` (see [`src/patterns/README.md`](../../patterns/README.md)) |
 | Baseline model knowledge or standard tool usage | **Nothing** | Do not create anything |
 | A refinement of existing guidance | **Update** | Extend the existing file |
 
@@ -67,6 +68,8 @@ Do not use this skill when:
 * One-off or too narrow → do not create anything yet
 * Standard tool knowledge (jq, docker, git basics) → **Nothing** — the model knows this
 * If unsure between skill and guideline: does it need step-by-step decisions? → Skill. Just conventions? → Guideline
+* If unsure between guideline and pattern: prose convention ("how to write code in X")? → Guideline. Keyed recipe ("problem P → recipe + verification + reliability")? → **Pattern**
+* When a related workflow fires, **surface** a matching `src/patterns/` recipe (never auto-apply) — the human decides
 
 ## Procedure
 
@@ -129,17 +132,18 @@ Choose one:
 ### 4. Check for overlap — search protocol (mandatory)
 
 A grep that returns zero hits is **not** proof of no overlap. Knowledge in
-this package is distributed across **four surfaces** — `skills/`, `rules/`,
-`docs/guidelines/`, `commands/`. Skip any of them and recall drops to ~25 %.
-Run all four steps before declaring "no overlap":
+this package is distributed across **five surfaces** — `skills/`, `rules/`,
+`docs/guidelines/`, `commands/`, `src/patterns/`. Skip any of them and recall
+drops. Run all the steps before declaring "no overlap":
 
-**Step 1 — list all four surfaces.** Directory taxonomy is free evidence:
+**Step 1 — list all five surfaces.** Directory taxonomy is free evidence:
 
 ```bash
-ls .agent-src.uncondensed/skills/ \
-   .agent-src.uncondensed/rules/ \
+ls src/skills/ \
+   src/rules/ \
    docs/guidelines/ \
-   .agent-src.uncondensed/commands/
+   dist/agent-src/commands/ \
+   src/patterns/
 ```
 
 Sub-directories matter — `docs/guidelines/php/patterns/`, `docs/guidelines/agent-infra/`,
@@ -155,7 +159,7 @@ artifact may name the *symptom*, not the cure.
 | Problem-words | `discriminator`, `enum.*match`, `switch.*on`, `if.*else.*chain` |
 
 ```bash
-grep -rl -E "<solution-words>|<problem-words>" .agent-src.uncondensed/
+grep -rl -E "<solution-words>|<problem-words>" src/ docs/guidelines/
 ```
 
 **Step 3 — taxonomy scan.** For any topic with a likely sub-folder

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

@@ -10,7 +10,7 @@ execution:
   allowed_tools: []
   command:
     - python3
-    - src/scripts/skill_linter.py
+    - src/scripts/skill_linter.ts
     - "--all"
 workspaces:
   - agent-config-maintainer
@@ -31,7 +31,7 @@ Use this skill when:
 
 Do NOT use when:
 
-- Linting only one file — call `python3 src/scripts/skill_linter.py <path>` directly
+- Linting only one file — call `./scripts-run src/scripts/skill_linter <path>` directly
 - Checking cross-references between files — use `check-refs` instead
 - Checking condensation freshness — use `bash scripts/condense.sh --check` instead
 
@@ -49,11 +49,11 @@ Invoke the skill through the runtime dispatcher so the `execution:` block in
 this skill's frontmatter governs the call:
 
 ```bash
-python3 scripts/runtime_dispatcher.py run --skill lint-skills
+./scripts-run src/scripts/runtime_dispatcher run --skill lint-skills
 ```
 
 The dispatcher resolves the request, the shell handler runs
-`python3 src/scripts/skill_linter.py --all`, captures stdout/stderr, and returns
+`python3 src/scripts/skill_linter.ts --all`, captures stdout/stderr, and returns
 a typed `ExecutionResult`.
 
 ### 3. Verify the result
@@ -86,7 +86,7 @@ Check the returned `ExecutionResult`:
 
 ## Do NOT
 
-- Do NOT invoke `src/scripts/skill_linter.py` directly when the intent is to test
+- Do NOT invoke `src/scripts/skill_linter.ts` directly when the intent is to test
   the runtime path — use the dispatcher so the handler and result object are
   exercised
 - Do NOT raise `timeout_seconds` to hide a genuinely slow linter pass —

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

@@ -0,0 +1,98 @@
+---
+model_tier: inherit
+name: logo-generation
+description: "Generate a logo or brand mark — structured prompt + provider routing, with a true-vector path via a vector-native provider or LLM-authored SVG for simple marks. Use for logo or brand mark generation."
+domain: product
+personas:
+  - design-director
+workspaces:
+  - small-business
+packs:
+  - ai-image
+trust:
+  level: experimental
+install:
+  removable: true
+execution:
+  type: manual
+---
+
+# logo-generation
+
+Generate a logo or brand mark end-to-end: capture the brand brief, choose raster
+vs. true-vector path, inject brand tokens when available, route to the right
+provider, author a provider-specific prompt, dry-run the adapter, and apply rights
+governance. All adapters are scaffold-tier (dry-run) until promoted to `stable`.
+
+## When to use
+
+- User asks to generate, create, or design a logo or brand mark.
+- End-to-end logo production (path selection + routing + prompting + governance).
+- When a simple geometric mark can be authored directly as SVG without a raster
+  model.
+
+## Procedure
+
+1. **Capture the brand brief** — extract: business name, style intent (wordmark /
+   icon mark / combination), colour palette, do/don't constraints (e.g. "no gradients",
+   "must be legible at 16 px").
+2. **Choose the path** — raster concept (text-in-mark → Ideogram for legible type)
+   vs. **true vector** (vector-native provider emitting `<path>` SVG for editable
+   marks, or LLM-authored SVG for simple geometric marks). Raster output is a
+   concept only — not a shippable logo asset.
+3. **Inject brand tokens when a brand layer is present** (`pack-brand`) — pull the
+   registered palette, typeface, and spacing tokens. When no brand layer exists,
+   use the brief's palette and type choices directly.
+4. **Route + prompt** via [`image-provider-routing`](../image-provider-routing/SKILL.md)
+   and [`prompt-engineering-image`](../prompt-engineering-image/SKILL.md) — apply
+   provider-specific grammar (text-literal first for Ideogram, `style: vector` param
+   for a vector-native provider, direct SVG authoring for simple geometric shapes).
+5. **Dry-run + validate** — invoke the adapter (scaffold-tier; returns a dry-run
+   plan). If the vector path is taken, validate that the output contains `<path>`
+   elements before treating it as an editable mark.
+6. **Rights check** — never reproduce a mark that resembles an existing trademarked
+   logo. Run [`image-likeness-and-rights`](../../rules/image-likeness-and-rights.md)
+   when the brief names a brand, references a known mark style, or targets a
+   regulated sector.
+
+## Output format
+
+1. **Chosen path** — raster concept or true vector, with rationale.
+2. **Prompt or SVG** — the prompt string ready to copy (raster/vector provider), or
+   the authored SVG markup (LLM-authored geometric mark path).
+3. **Governance note** — rights check outcome and the adapter dry-run caveat:
+   "adapter is experimental (scaffold-tier) — dry-run plan only; no rendered asset
+   until promotion per `provider-lifecycle-discipline`."
+
+## Gotcha
+
+- **Raster models cannot emit usable editable logos** — general-purpose image
+  models garble text and produce no `<path>` geometry. A PNG concept is useful
+  for direction-setting, but it is not a logo asset. Use the vector path for any
+  mark that must scale, be modified, or be handed to a designer.
+- **Scaffold-tier adapters produce plans, not pixels** — all adapters are
+  `experimental` (dry-run only). Claiming a rendered asset exists while no adapter
+  is `stable` misleads the caller.
+
+**Good example:** Brief for a wordmark → route to a vector-native provider with
+`style: vector`, validate `<path>` elements in output, note "experimental —
+dry-run plan only."
+
+**Bad example:** Routing a logo brief to a photoreal raster model and delivering the
+PNG as the final logo file.
+
+## Do NOT
+
+- Do NOT ship a raster PNG as a "logo" when an editable vector mark is needed —
+  surface the vector path and the raster-model limitation explicitly.
+- Do NOT generate a mark resembling an existing trademarked logo — run
+  `image-likeness-and-rights` when the brief references a known brand or mark.
+- Do NOT claim a live render at scaffold tier — the dry-run caveat is mandatory
+  every time.
+
+## See also
+
+- [`image-generation`](../image-generation/SKILL.md) — general-purpose image generation (non-logo briefs).
+- [`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 brief into provider-specific prompt grammar.
+- [`image-likeness-and-rights`](../../rules/image-likeness-and-rights.md) — rights check before generating brand marks or likenesses.

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

@@ -0,0 +1,17 @@
+{
+  "skill": "logo-generation",
+  "last_eval": "2026-06-16",
+  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers end-to-end logo / brand mark generation requests. Should-not-trigger covers near-miss neighbors: general image generation (image-generation), banner/social asset production (brand-asset-generation), routing-only questions (image-provider-routing), prompt-authoring-only (prompt-engineering-image), and rights checks (image-likeness-and-rights).",
+  "queries": [
+    {"q": "generate a logo for my bakery called Golden Crust", "trigger": true},
+    {"q": "create a brand mark for our SaaS startup — minimalist, dark blue, no text", "trigger": true},
+    {"q": "I need a vector SVG logo for our coffee shop", "trigger": true},
+    {"q": "design a wordmark logo for our law firm with clean sans-serif type", "trigger": true},
+    {"q": "produce a combination mark logo — icon plus company name — for our fitness app", "trigger": true},
+    {"q": "generate a hero image for our homepage", "trigger": false, "note": "general image generation → image-generation"},
+    {"q": "create a banner for our bakery's Instagram with the seasonal offer", "trigger": false, "note": "social/banner asset → brand-asset-generation"},
+    {"q": "which provider should I use for a logo with text inside?", "trigger": false, "note": "routing-only question → image-provider-routing"},
+    {"q": "write me a Recraft prompt for a minimalist geometric logo mark", "trigger": false, "note": "prompt authoring only → prompt-engineering-image"},
+    {"q": "can I use a design that looks like the Apple logo as inspiration for my mark?", "trigger": false, "note": "rights / trademark check → image-likeness-and-rights"}
+  ]
+}

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

@@ -37,7 +37,7 @@ Do NOT use when:
 - **1.5-2× token reduction** on plain-text-heavy PDFs.
 - **Negative** ratio on DOCX with revision history ON or PPTX with verbose presenter notes — see § Step 3 mitigations.
 
-Measure on your own corpus before quoting numbers. The bundled measurement corpus at `tests/fixtures/markitdown-corpus/` plus `python3 scripts/measure_markitdown_lift.py` lets the consumer ground the claim locally — the script lists each fixture, computes the raw-bytes baseline, and (if `markitdown-mcp` is reachable peer-side) prints the converted-Markdown token count + ratio per format.
+Measure on your own corpus before quoting numbers. The bundled measurement corpus at `tests/fixtures/markitdown-corpus/` plus `./scripts-run src/scripts/measure_markitdown_lift` lets the consumer ground the claim locally — the script lists each fixture, computes the raw-bytes baseline, and (if `markitdown-mcp` is reachable peer-side) prints the converted-Markdown token count + ratio per format.
 
 ## Procedure: markitdown
 

package/dist/agent-src/skills/mcp-builder/SKILL.md

@@ -107,7 +107,7 @@ Process: enumerate the tools, explore READ-ONLY data, draft 10 questions, **solv
 
 - Upstream protocol: https://modelcontextprotocol.io
 - Upstream SDKs: https://github.com/modelcontextprotocol/python-sdk · https://github.com/modelcontextprotocol/typescript-sdk
-- Adopted from: `Microck/ordinary-claude-skills@8f5c83174f7aa683b4ddc7433150471983b93131:skills_all/mcp-builder/SKILL.md` (MIT, © 2025 Microck) — external `./reference/*.md` file links replaced with inline guidance + upstream URLs.
+- Adopted from: an external reference (MIT, © 2025 an external reference) — external `./reference/*.md` file links replaced with inline guidance + upstream URLs.
 - Cross-linked: [`mcp`](../mcp/SKILL.md), [`testing-anti-patterns`](../testing-anti-patterns/SKILL.md), [`api-design`](../api-design/SKILL.md).
 - Provenance registry: `agents/settings/contexts/skills-provenance.yml` (entry: `mcp-builder`).
 - Iron-Law floor: `verify-before-complete`, `tool-safety`, `skill-quality`.

package/dist/agent-src/skills/md-language-check/SKILL.md

@@ -51,7 +51,7 @@ one turn → pass them all to a single invocation.
 ### 2. Run the checker
 
 ```bash
-python3 scripts/check_md_language.py <path> [<path> …] [--format json]
+./scripts-run src/scripts/check_md_language <path> [<path> …] [--format json]
 ```
 
 Exit codes:

package/dist/agent-src/skills/memory-consolidation/SKILL.md

@@ -90,13 +90,15 @@ miner is too loose; tighten patterns and re-run before promoting.
 
    A fact may carry **two** tags; the promoter resolves via tag
    intersection, not by file extension. See
-   [`docs/contracts/agent-memory-contract.md`](../../../docs/contracts/agent-memory-contract.md)
-   for the curated YAML schemas.
+   [`memory-access`](../../../docs/guidelines/agent-infra/memory-access.md)
+   for the file-backed retrieval contract over the curated YAML.
 
 2. Append each fact as one JSONL line to
    `agents/memory/intake/<primary-tag>.jsonl` with required fields
    per the contract: `ts`, `type`, `key`, `observation`, `source:
    agent`, `session_id`, plus the new optional `tags: [<one>, <two>]`.
+   Intake is **gitignored, local scratch** — only entries promoted to
+   curated YAML (next phase) become team-shared (committed).
 3. Default to `--preview` mode: render the JSONL block to stdout and
    stop. Only `--commit-intake` writes the file.
 
@@ -109,13 +111,45 @@ validates against the contract.
    archive the consumed JSONL lines into
    `agents/memory/intake/.archive/YYYY-Www.jsonl` — week-bucketed,
    not day-bucketed (defeats session-context inference attacks).
-2. If a curated entry's `last_validated` field is older than 90 days
-   AND no signal in the last 30 days touched its `key`, mark it
-   stale in the consolidation report — but do **not** auto-delete.
-   Pruning is a human-confirmed action.
-
-**Exit gate:** report cites ≥ 0 promotions, ≥ 0 stale flags, 0
-auto-deletes.
+2. **Delete `status: archived` curated entries.** Once an entry is
+   marked `archived` (by review or supersession), remove it from the hot
+   file — **git history is the cold archive** (`git log -- <file>`
+   recovers it). This keeps the committed memory small without a decay
+   engine. Do not keep an `agents/memory/archive/` directory.
+3. If an *active* curated entry's `last_validated` is older than 90 days
+   AND no signal in the last 30 days touched its `key`, mark it stale in
+   the consolidation report — but do **not** auto-delete a still-active
+   entry. Only `archived` entries are deleted; staleness is a flag, not a
+   delete trigger.
+
+**Exit gate:** report cites ≥ 0 promotions, ≥ 0 stale flags, and the
+count of `archived` entries deleted (git history retains them).
+
+## Write-time curation discipline
+
+Memory quality comes from what you write, not from a heavy store. Apply
+these at GATHER + CONSOLIDATE (adapted from MemSkill's memory-operation
+skills — github.com/ViktorAxelsen/MemSkill, Apache-2.0, commit `9907c35f8cc7`):
+
+- **Dedupe before insert.** Compare against retrieved entries; never add a
+  fact already covered. Split distinct facts into separate entries.
+- **Merge on refresh, preserve what still holds.** When a fact updates an
+  existing entry, merge into one item and keep the details that remain true.
+- **Delete only on explicit contradiction.** Remove a curated entry only when
+  evidence directly contradicts or cancels it. If uncertain, keep it.
+- **Prefer no-op under uncertainty.** A chunk with no new, corrective, or
+  actionable information records nothing — silence beats speculation.
+- **Skip trivial / fleeting / speculative content.** Capture durable,
+  reusable facts, not transcripts or one-off chatter.
+- **One durable fact per entry.** No narrative blobs — each entry is a single
+  PATTERN / CONVENTION / INVARIANT / GOTCHA the next agent can act on.
+
+This is **meta-memory**: the skill of *how to remember* (what to extract,
+keep, forget) — distinct from the remembered content. The store stays simple
+and file-backed; the discipline lives here. Do **not** add
+INSERT/UPDATE/DELETE/NOOP operation machinery (append-only JSONL + curated
+YAML need no such ops) and do **not** import any retrieval / decay / trust
+engine.
 
 ## TranscriptAdapter contract
 
@@ -134,11 +168,24 @@ The miner is host-agnostic by design. A `TranscriptAdapter` for host
   identifier the consumer project lists in
   `.agent-settings.yml` under `memory.redact_patterns`.
 
-Phase 1 implementation lives in
-`/memory:mine-session` (single host: Claude Code,
-`~/.claude/projects/*/sessions/*.jsonl`). Phase 3 of the
-adoption roadmap adds a second host adapter; the contract above is
-documented now so the second implementation is not a vacuum design.
+The GATHER implementation lives in the single mining command
+`/memory:mine-session` (`scripts/mine_session.py`). It reads the
+**cross-host** chat-history JSONL log (`agents/runtime/.agent-chat-history`,
+written by platform hooks on every host), falling back to the per-host
+Claude-Code transcript when the log is absent. `--mode=[signals|proposals|both]`
+selects intake signals and/or rule/skill proposal seeds — the latter folds in
+the former `/chat-history learn`.
+
+## In-task notes → cross-run lessons (RDP)
+
+The Reasoning Discipline Protocol writes an **in-task** session-notes file
+(hypotheses, killed beliefs, predictions, decisions, uncertainty — structure in
+[`notes-first-reasoning`](../../rules/notes-first-reasoning.md)). That file is
+ephemeral working state, not curated memory. This skill is the **promotion path**:
+when an in-task killed-belief, calibrated prediction, or decision *generalises*
+beyond the task, consolidate it here as a durable cross-run lesson (one lesson per
+file, with why it mattered). Apply the same signal-vs-noise discipline — most
+in-task notes stay in-task and are discarded with the task.
 
 ## Related Skills
 
@@ -196,9 +243,8 @@ documented now so the second implementation is not a vacuum design.
 
 - Do NOT auto-trigger this skill on session end. The flow is manual,
   per-invocation, and confirmed.
-- Do NOT vendor patterns or text from `grandamenium/dream-skill` —
-  the upstream lacks a `LICENSE`. Concept and procedure structure are
-  the only adoption surface.
+- Do NOT vendor patterns or text from any external source. Concept and
+  procedure structure are the only adoption surface.
 - Do NOT promote a normalised fact whose `key` falls outside the
   repo root or names another consumer project.
 - Do NOT delete a stale curated entry without explicit user

package/dist/agent-src/skills/motion-choreographer/SKILL.md

@@ -25,7 +25,7 @@ install:
 > environment motion, physics constraints, and — when the adapter
 > declares `audio: native` — a synchronized audio direction block.
 > Reads adapter capabilities from
-> [`adapter-contract.md`](../../../scripts/ai-video/lib/adapter-contract.md);
+> [`adapter-contract.md`](../../../scripts/media/lib/adapter-contract.md);
 > never speaks to a network API.
 
 ## When to use

package/dist/agent-src/skills/php-coder/evals/triggers.json

@@ -1,5 +1,6 @@
 {
   "skill": "php-coder",
+  "last_eval": "2026-06-16",
   "description": "5 should-trigger + 5 should-not-trigger queries. Multi-skill co-activation (e.g. php-coder alongside pest-testing on a test query) is accepted as TP where writing PHP code is a legitimate sub-task. Near-misses share PHP/Laravel vocabulary without being code-generation tasks.",
   "queries": [
     {"q": "my UserController is getting huge, split it into a service", "trigger": true},

package/dist/agent-src/skills/prediction-pool-optimizer/evals/triggers.json

@@ -1,5 +1,6 @@
 {
   "skill": "prediction-pool-optimizer",
+  "last_eval": "2026-06-16",
   "description": "9 should-trigger + 5 should-not-trigger queries. Should-trigger covers DE + EN phrasings and the core intent (pool tips, kicktipp, expected-points optimization across sports, plus answering the bonus / award questions and using bookmaker-consensus odds). Should-not-trigger covers near-miss neighbours: regulated financial advice (finance pack), plain match-result prediction with no pool, generic web research, AI video, and real-money sportsbook betting (out of scope / refuse).",
   "queries": [
     {"q": "optimize my kicktipp tips for the football WM 2026", "trigger": true},