@event4u/agent-config 9.8.0 → 9.10.0

package/dist/agent-src/skills/security-maturity-assessment/SKILL.md

@@ -11,7 +11,10 @@ packs:
 
 # security-maturity-assessment
 
-Rate how mature a module's security **posture** is — category by category, every rating backed by `file:line` evidence — instead of hunting individual vulnerabilities. Output is a scorecard a maintainer can re-run and diff, not a finding list.
+Rate how mature a module's security **posture** is — category by category,
+every rating backed by `file:line` evidence — instead of hunting individual
+vulnerabilities. The output is a scorecard a maintainer can re-run and diff,
+not a finding list.
 
 ## When to use
 
@@ -53,34 +56,53 @@ Do NOT use when:
 
 ## Procedure
 
-1. **Scope** — name the module/paths under assessment; list entry points (routes, jobs, commands, webhooks). Scorecard without stated scope is not reproducible.
-2. **Assess each category** — inspect the code the category names. Every rating cites evidence:
-   - Positive evidence: `file:line` of the control (`app/Http/Requests/…:12`).
-   - Absence evidence: the searches run that came back empty (name the grep patterns) — "not found" beats "probably missing".
-   - Multi-tenant N/A: single-tenant systems rate category 8 `N/A`; drops out of the roll-up.
-3. **Roll up deterministically** — overall rating is computed, not vibed:
+1. **Scope** — name the module/paths under assessment; list entry points
+   (routes, jobs, commands, webhooks). A scorecard without a stated scope is
+   not reproducible.
+2. **Assess each category** — inspect the code the category names. Every
+   rating cites evidence:
+   - Positive evidence: `file:line` of the control (`app/Http/Requests/…:12`, `src/guards/auth.guard.ts:12`).
+   - Absence evidence: the searches run that came back empty (name the grep
+     patterns) — "not found" beats "probably missing".
+   - Multi-tenant N/A: single-tenant systems rate category 8 `N/A`; it drops
+     out of the roll-up.
+3. **Roll up deterministically** — the overall rating is computed, not vibed:
    - `overall = min( median(all rated categories), one step above the lowest critical-category rating )`
-   - Consequences: any critical category **Missing** caps overall at **Weak**; any critical **Weak** caps overall at **Moderate**. Non-critical categories move the median but never lift the cap.
-4. **Recommend** — max 3 next steps, ordered by which would raise the overall rating (fix the lowest critical category first).
+   - Consequences: any critical category **Missing** caps overall at **Weak**;
+     any critical **Weak** caps overall at **Moderate**. Non-critical
+     categories move the median but can never lift the cap.
+4. **Recommend** — max 3 next steps, ordered by which would raise the overall
+   rating (i.e. fix the lowest critical category first).
 
 ## Output format
 
-1. **Scope block** — module/paths + entry-point list, so the scorecard is re-runnable.
-2. **Scorecard table** — one row per category: `Category | Rating | Evidence (file:line or named empty searches) | Gap`. Every row MUST carry evidence; a rating without a citation is invalid.
-3. **Overall rating** — with the roll-up shown (`median=…, lowest critical=…, cap=… → overall=…`), never a bare verdict.
+1. **Scope block** — module/paths + entry-point list, so the scorecard is
+   re-runnable.
+2. **Scorecard table** — one row per category:
+   `Category | Rating | Evidence (file:line or named empty searches) | Gap`.
+   Every row MUST carry evidence; a rating without a citation is invalid.
+3. **Overall rating** — with the roll-up shown (`median=…, lowest critical=…,
+   cap=… → overall=…`), never a bare verdict.
 4. **Top-3 next steps** — ordered by roll-up impact.
 
 ## Gotcha
 
-- The model tends to rate from vibes ("looks well-structured") — a rating row without `file:line` or named empty searches is invalid; redo it.
-- Don't let a Strong non-critical category mask a Weak critical one — the cap rule exists precisely because a polished logging setup does not offset missing authorization.
-- A vulnerability found mid-assessment is **out of scope** for the scorecard — note it and route to [`security-audit`](../security-audit/SKILL.md) (with its false-positive gate) instead of inlining findings here.
+- The model tends to rate from vibes ("looks well-structured") — a rating
+  row without `file:line` or named empty searches is invalid; redo it.
+- Don't let a Strong non-critical category mask a Weak critical one — the
+  cap rule exists precisely because a polished logging setup does not offset
+  missing authorization.
+- A vulnerability found mid-assessment is **out of scope** for the scorecard
+  — note it and route to [`security-audit`](../security-audit/SKILL.md)
+  (with its false-positive gate) instead of inlining findings here.
 
 ## Do NOT
 
-- Do NOT emit a rating without evidence — every row cites `file:line` or the empty searches that prove absence.
+- Do NOT emit a rating without evidence — every row cites `file:line` or the
+  empty searches that prove absence.
 - Do NOT average away critical categories — the deterministic cap always wins.
-- Do NOT turn the scorecard into a finding list — posture assessment and vulnerability hunting are different deliverables.
+- Do NOT turn the scorecard into a finding list — posture assessment and
+  vulnerability hunting are different deliverables.
 - Do NOT assess unscoped ("the whole app") when the user named a module.
 
 ## See also

package/dist/agent-src/skills/skill-improvement-pipeline/SKILL.md

@@ -11,6 +11,8 @@ workspaces:
   - agent-config-maintainer
 packs:
   - meta
+requires_skills:
+  - learning-to-rule-or-skill
 ---
 
 # skill-improvement-pipeline
@@ -66,19 +68,21 @@ Show the user:
 
 #### Cross-project promotion signal (surfacing only — never an auto-writer)
 
-Same learning now seen in **≥ 2 distinct projects** → strong candidate for a
-*shared* surface (global rule/skill or a `src/patterns/` recipe), not a
-project-local note. **Surface** it; do **not** auto-write:
+If the **same learning** has now been observed in **≥ 2 distinct projects**, it
+is a strong promotion candidate for a *shared* surface (a global rule/skill or a
+`src/patterns/` recipe) rather than a project-local note. **Surface** that signal
+to the user — do **not** auto-write it:
 
 ```
-> Cross-project: also seen in {other-project}.
+> Cross-project: this learning was also seen in {other-project}.
 > ≥2 projects ⇒ candidate for a shared surface (global rule / skill / pattern).
 > → surface for promotion (human decides; no auto-write)
 ```
 
-A *signal*, not a store: no auto-write, no decay, no runtime (the writable
-per-project learning store stays rejected — [[council-agent-memory-sunset]]).
-The human decides whether the cross-project recurrence justifies promotion.
+This is a *signal*, not a store: there is no auto-write, no decay, no runtime
+(the writable per-project learning store stays rejected —
+[[council-agent-memory-sunset]]). The human decides whether the cross-project
+recurrence justifies promotion.
 
 ### Step 3: Classify
 
@@ -115,18 +119,17 @@ Decide what to create:
 > the exact wording is recoverable, and verify against it rather than trusting
 > the summary.
 
-- **New rule** → create in `.agent-src.uncondensed/rules/`, follow rule conventions
-- **New skill** → use `skill-writing` skill, create in `.agent-src.uncondensed/skills/`
+- **New rule** → create in `src/rules/`, follow rule conventions
+- **New skill** → use `skill-writing` skill, create in `src/skills/`
 - **Update existing** → use `skill-management` skill
 
 After creation:
 1. Run `./scripts-run src/scripts/skill_linter {path}` — must pass (0 fail)
 2. Copy to `.augment/`
-3. Mark hash: `./scripts-run src/scripts/condense --mark-done "{relative_path}"`
-4. Regenerate tools: `./scripts-run src/scripts/condense --generate-tools`
-5. **If from a knowledge page** (`agents/knowledge/procedures/skill-candidates.md`
+3. Regenerate tools: `./scripts-run src/scripts/condense --generate-tools`
+4. **If the learning came from a knowledge page** (`agents/knowledge/procedures/skill-candidates.md`
    or any `agents/knowledge/` page) — degrade the source to a pointer;
-   promotion isn't complete otherwise (double-maintenance risk):
+   promotion is not complete otherwise (double-maintenance risk):
    `./scripts-run src/scripts/degrade_to_pointer --source "<knowledge-path>[#<anchor>]" --artifact "{relative_path}" --date "<YYYY-MM-DD>"`
 
 ### Step 5: Decide scope
@@ -175,7 +178,7 @@ Ask the user:
 - Do NOT skip the promotion gate — it prevents skill/rule bloat
 - Do NOT create both a rule AND a skill for the same learning
 - Do NOT auto-push without user permission
-- Do NOT create project-specific content in `.agent-src.uncondensed/`
+- Do NOT create project-specific content in `src/`
 - Do NOT run this pipeline for trivial learnings
 
 ## References

package/dist/agent-src/skills/skill-writing/SKILL.md

@@ -189,7 +189,7 @@ approval-gated propose / pick loop with at most two rounds.
 ### 1c. Propose a trigger-eval stub (new skills only)
 
 When creating a new skill, propose a stub
-`.agent-src.uncondensed/skills/{name}/evals/triggers.json` before writing
+`src/skills/{name}/evals/triggers.json` before writing
 the body. Draw the queries from Phase A of the drafting protocol (the
 user's "should trigger" and "must not trigger" answers).
 
@@ -454,14 +454,15 @@ to every skill you author.
 ## Read-only-by-default scripts
 
 A script shipped inside a skill (`scripts/**`) is **side-effect-free by
-default** — inspects, computes, prints; does not mutate. Mutation (write /
-delete / rename / copy) gates behind an explicit flag named in this SKILL.md —
-`--writable` / `--apply` / `--write` / `--output` / `--fix` — so the default
-invocation is safe. A generator whose *declared purpose* is to write (emits an
-artifact to a caller-supplied path) is allowlisted with a rationale in
-`src/scripts/lint_skill_scripts_readonly_allowlist.json` instead of a redundant
-flag. `lint_skill_scripts_readonly` enforces this: an ungated, non-allowlisted
-write fails the build.
+default** — it inspects, computes, and prints; it does not mutate the
+filesystem. Any mutation (writing a file, deleting, rename/copy) must be gated
+behind an explicit flag named in this SKILL.md — `--writable` / `--apply` /
+`--write` / `--output` / `--fix` — so the default invocation is safe to run
+blind. A generator whose *declared purpose* is to write (it emits an artifact
+to a caller-supplied path) is allowlisted with a rationale in
+`src/scripts/lint_skill_scripts_readonly_allowlist.json` rather than carrying a
+redundant flag. `lint_skill_scripts_readonly` enforces this: an ungated,
+non-allowlisted write fails the build.
 
 ## Description-optimizer loop (U1 — held-out, not vibes)
 
@@ -531,7 +532,7 @@ content).
 
 ## Do NOT
 
-* Write documentation-style, pointer-only, or too-broad skills ("Laravel skill")
+* Write documentation-style, pointer-only, or too-broad skills ("Laravel skill", "Django skill")
 * Skip Procedure or use vague validation
 * Exceed size limits (see `docs/guidelines/agent-infra/size-and-scope.md`)
 * Duplicate rules

package/dist/agent-src/skills/song-to-script/SKILL.md

@@ -19,14 +19,14 @@ install:
 
 # song-to-script
 
-> Turn a song into `<project>/script.md` — `## Scene N` blocks whose
-> `duration:` values sum to the track length and whose cut points land
-> on real section boundaries. Consumed by
+> Turn a song into `<project>/script.md` — a sequence of `## Scene N`
+> blocks whose `duration:` values sum to the track length and whose cut
+> points land on real section boundaries. Consumed by
 > [`/video:from-song`](../../commands/video/from-song.md), then handed
 > to [`scene-expander`](../scene-expander/SKILL.md) and
 > [`video-director`](../video-director/SKILL.md). Never invents timing —
-> every boundary comes from the audio analysis, and its source (adapter
-> vs. probe `method`) tells this skill how musical those boundaries are.
+> every boundary comes from the audio probe, and the probe's `method`
+> tells this skill how musical (or not) those boundaries actually are.
 
 ## When to use
 
@@ -49,25 +49,27 @@ Do NOT use when:
     configured — see
     [`audio-adapter-contract.md`](../../scripts/ai-video/lib/audio-adapter-contract.md)):
     `{bpm, beats, downbeats, sections:[{start,end,label,energy?}]}` —
-    real musical structure. Beats/downbeats = candidate cut grid;
-    section labels musical (`verse`, `chorus`, …).
+    real musical structure. Beats/downbeats become the candidate cut
+    grid; section labels are musical (`verse`, `chorus`, …).
   - **Audio probe** — JSON from
     [`scripts/ai-video/lib/probe-audio.sh`](../../scripts/ai-video/lib/probe-audio.sh):
     `{duration, method, warning?, sections:[{start,end,energy,label}]}`.
-    - `method: silence` — boundaries are real quiet gaps; trust as cuts.
-    - `method: rms` — energy-delta inflections; usable but coarse.
-    - `method: interval` — **track is structurally flat** (brick-walled
-      / sustained); sections fixed-interval, NOT musical. `method:
-      interval` (or `warning` set) → script header states timing is
-      interval-based; operator should pass `--scene-durations` for
-      musical sync. Never present interval cuts as beat-synced.
-- **Model capabilities** — chosen video model's renderable envelope from
-  the multiplexer manifest:
+    - `method: silence` — boundaries are real quiet gaps; trust them as cuts.
+    - `method: rms` — boundaries are energy-delta inflections; usable but
+      coarse.
+    - `method: interval` — **the track is structurally flat** (brick-walled
+      / sustained); sections are fixed-interval, NOT musical. When `method`
+      is `interval` (or `warning` is set), the emitted script header states
+      that timing is interval-based and the operator should pass
+      `--scene-durations` for musical sync. Never present interval cuts as
+      beat-synced.
+- **Model capabilities** — the chosen video model's renderable envelope
+  from the multiplexer manifest:
   `scripts/ai-video/adapters/<provider>.sh capability --model <id>` →
   `{min_duration, max_duration, audio_sync, aspect, verified}`. Scene
-  durations MUST land inside `[min_duration, max_duration]`;
-  `verified: false` entries surfaced in the report, never trusted
-  silently.
+  durations MUST land inside `[min_duration, max_duration]`; a
+  `verified: false` manifest entry is surfaced in the report, never
+  trusted silently.
 - **Mode** — `brief` (operator text is the creative source) or `auto`
   (infer mood + action from energy).
 - **Brief** (brief mode only) — free text: story, settings, look.
@@ -80,26 +82,28 @@ Do NOT use when:
 ### Step 1: Map sections → scenes (capability-clamped, beat-aligned)
 
 One `## Scene N` per analysis section. `duration:` = `end - start`
-(rounded to 0.5 s). Then **clamp the plan to the model's renderable
-envelope** — `min_duration` / `max_duration` from the manifest
-(`<provider>.sh capability --model <id>`), provider tuning as fallback
-for single-model adapters:
-
-- **Section < `min_duration`** → merge into neighbour. With beat data,
-  merge toward the neighbour keeping the joined cut on a **downbeat**
-  (else any beat); without, merge into the shorter neighbour.
-- **Section > `max_duration`** → split into sub-scenes. With beat data,
-  every split point on the **nearest downbeat** (else beat) to the
-  equal-division point — never mid-beat; without, split equally.
-- **No valid plan** (song shorter than `min_duration`; section cannot
-  split onto any beat inside the envelope) → **halt and surface the
-  conflict** with model id + violated bound — an unbuildable plan never
-  reaches the renderer.
+(rounded to 0.5 s). Then **clamp the plan to the chosen model's
+renderable envelope** — read `min_duration` / `max_duration` from the
+model-capabilities manifest (`<provider>.sh capability --model <id>`),
+falling back to the provider tuning for single-model adapters:
+
+- **Section shorter than `min_duration`** → merge into its neighbour.
+  With beat data, merge toward the neighbour that keeps the joined cut
+  on a **downbeat** (else any beat); without beat data, merge into the
+  shorter neighbour.
+- **Section longer than `max_duration`** → split into sub-scenes. With
+  beat data, place every split point on the **nearest downbeat** (else
+  beat) to the equal-division point — never mid-beat; without beat
+  data, split equally.
+- **No valid plan exists** (e.g. the whole song is shorter than
+  `min_duration`, or a section cannot be split onto any beat inside the
+  envelope) → **halt and surface the conflict** with the model id and
+  the violated bound — an unbuildable plan never reaches the renderer.
 
 Every emitted scene satisfies
-`min_duration ≤ duration ≤ max_duration`. Manifest entry
-`verified: false` → say so in the report — documented-best-effort, not
-a smoke-traced fact.
+`min_duration ≤ duration ≤ max_duration`. When the manifest entry is
+`verified: false`, say so in the report — the envelope is
+documented-best-effort, not a smoke-traced fact.
 
 ### Step 2: Assign mood + action
 
@@ -108,29 +112,31 @@ First decide the **subject mode**:
 - **Character mode** — `character.json` exists: every scene's `action:`
   names the locked subject, never a fresh description.
 - **Style mode** — no `character.json`: scenes describe setting, palette,
-  motion continuity (the recurring *look*), not a person. Valid abstract
-  / landscape / visualiser path — do not invent a human subject.
+  and motion continuity (the recurring *look*), not a person. This is the
+  valid abstract / landscape / visualiser path — do not invent a human
+  subject to fill the slot.
 
 Then pick the **prompt source per segment — the modality switch**:
 
-- **Lyric segment** (vocal map places ≥1 transcribed line inside it) →
-  scene prompt derives from the **lyric line itself**: its imagery,
-  subjects, verbs seed `mood:` + `action:` (character mode: acted by the
-  locked subject; style mode: rendered as setting / weather / palette —
-  never an invented human). Line lands in `dialogue:` per Step 3.
-- **Instrumental segment** (no vocal-map line) → prompt derives from the
-  **audio features**: section `label` + `energy` via the intent table
-  below. Never recycle a lyric from another segment into an
-  instrumental one.
+- **Lyric segment** (the vocal map places ≥1 transcribed line inside
+  it) → the scene prompt derives from the **lyric line itself**: its
+  imagery, subjects, and verbs seed `mood:` + `action:` (in character
+  mode, acted by the locked subject; in style mode, rendered as
+  setting / weather / palette — never an invented human). The line
+  lands in `dialogue:` per Step 3.
+- **Instrumental segment** (no vocal-map line) → the scene prompt
+  derives from the **audio features**: section `label` + `energy` via
+  the intent table below. Never recycle a lyric from another segment
+  into an instrumental one.
 
 Then assign per scene:
 
 - **Brief mode** — distribute the brief's beats across scenes in order;
-  modality switch still applies (lyric segments quote the brief's
-  matching beat through the lyric's lens); energy modulates pacing. Do
-  not add story the brief did not state.
-- **Auto mode** — derive mood per section from `energy` + `label`
-  (probe labels and musical adapter labels both map):
+  the modality switch still applies (lyric segments quote the brief's
+  matching beat through the lyric's lens), and energy modulates pacing.
+  Do not add story the brief did not state.
+- **Auto mode** — derive mood per section from `energy` and `label`
+  (probe labels and musical labels from the analysis adapter both map):
 
   | label / energy | default scene intent |
   |---|---|
@@ -142,8 +148,8 @@ Then assign per scene:
   | outro / fade | pull-back, resolve, hold |
 
 **Energy → cut frequency + motion intensity.** Section energy (0..1,
-relative to track mean) drives cut rate AND camera intensity — chorus =
-faster cuts / more motion:
+relative to the track mean) drives both how often the edit cuts and how
+hard the camera moves — chorus = faster cuts / more motion:
 
 | energy vs. track mean | cut length target | `camera:` motion intensity |
 |---|---|---|
@@ -151,9 +157,10 @@ faster cuts / more motion:
 | within ±0.10 of mean (verse / build) | medium — one scene per section or per 4-bar phrase | steady dolly, slow tighten |
 | ≤ mean − 0.10 (breakdown / outro) | long — merge toward `max_duration`, hold shots | locked-off or slow drift |
 
-High-energy splitting and low-energy merging stay inside the Step 1
-envelope and land on downbeats — the energy table picks *where inside
-the envelope* a length falls, never outside it.
+High-energy splitting and low-energy merging both stay inside the
+Step 1 capability envelope and land on downbeats — the energy table
+chooses *where inside the envelope* a scene length falls, never
+outside it.
 
 ### Step 3: Vocal map — transcribe, never guess (vocal tracks)
 
@@ -163,10 +170,10 @@ BRIEF / STORY SKELETON OR A GUESSED STRETCH. NEVER PUT ONE SINGER'S
 LINE ON ANOTHER SINGER'S SCENE.
 ```
 
-Track has vocals and the run intends lip-sync → build a **vocal map**
-from the real audio before assigning any `dialogue:`:
+When the track has vocals and the run intends lip-sync, build a
+**vocal map** from the real audio before assigning any `dialogue:`:
 
-1. **Transcribe** audio to timestamped lines. Adapter-first: a
+1. **Transcribe** the audio to timestamped lines. Adapter-first: a
    configured `lyrics` provider (e.g.
    [`audio-adapters/whisperx.sh`](../../scripts/ai-video/audio-adapters/whisperx.sh))
    returns word-level timestamps **plus per-line diarization labels**
@@ -175,34 +182,35 @@ from the real audio before assigning any `dialogue:`:
    echo '{"audio_path":"<vocal-stem-or-song>"}' \
      | scripts/ai-video/audio-adapters/whisperx.sh analyze
    ```
-   No lyrics provider → OpenAI `/v1/audio/transcriptions`
+   No lyrics provider configured → OpenAI `/v1/audio/transcriptions`
    (`response_format=verbose_json` → `segments[].{start,end,text}`) or
-   local whisper (no speaker labels — every line starts as `"?"`).
-   Either way the transcript is the only source of lyric timing.
+   local whisper as before (no speaker labels — every line starts as
+   `"?"`). Either way the transcript is the only source of lyric timing.
 2. **Label the singer** per line — map diarization labels (or unlabeled
-   lines) to cast names via the operator's who-sings reference (roster,
-   brief naming who sings which line, or character cast): one label ↦
-   one cast name, consistently. Genuinely ambiguous (label `"?"`,
-   mixed-speaker line, no roster match) → keep `singer: "?"`, surface
-   it — never guess a singer to fill the slot.
-3. **Emit** `<project>/vocal-map.json`: `[{start, end, text, singer}]`,
-   timing verbatim from the transcript.
-4. **Validate** — run the ground-truth enforcer before the sign-off
-   gate:
+   lines) to cast names via the operator's who-sings reference (a
+   roster, a brief that names who sings which line, or a character
+   cast): one diarization label ↦ one cast name, consistently. If a
+   line's singer is genuinely ambiguous (label `"?"`, mixed-speaker
+   line, or no roster match), keep `singer: "?"` and surface it —
+   never guess a singer to fill the slot.
+3. **Emit** `<project>/vocal-map.json`:
+   `[{start, end, text, singer}]`, timing verbatim from the transcript.
+4. **Validate** — run the ground-truth enforcer before handing the map
+   to the sign-off gate:
    ```bash
    scripts/ai-video/lib/validate-vocal-map.sh <project>/vocal-map.json \
      <project>/transcript.json --roster "<cast names>"
    ```
-   Rejects re-timed lines, lyrics not in the transcript, missing singers
-   (exit 7, specific line named). Red validator = halt — fix the map,
-   never bypass.
-5. **Place lines into the matching scene's** `dialogue:` block using
+   It rejects re-timed lines, lyrics not in the transcript, and missing
+   singers (exit 7, specific line named). A red validator is a halt —
+   fix the map, never bypass.
+5. **Place lines into the matching scene's** `dialogue:` block using the
    transcript timing, tagged with the singer (`singer: "<line>"`). A
-   scene's lip-sync subject MUST be the line's labelled singer; a `"?"`
-   line gets NO lip-sync scene until the operator resolves it.
+   scene's lip-sync subject MUST be the line's labelled singer; a
+   `"?"` line gets NO lip-sync scene until the operator resolves it.
 
 No vocals / no transcript / no lip-sync intent → leave `dialogue:` empty;
-scene is performance / B-roll. **Never fabricate lyrics**, **never
+the scene is performance / B-roll. **Never fabricate lyrics**, **never
 re-time a line off the brief**, and in style mode `dialogue:` stays empty
 (lip-sync needs a character subject). The `/video:from-song` sign-off
 gate (its Step 6) shows this map for approval before any render.
@@ -211,11 +219,11 @@ gate (its Step 6) shows this map for approval before any render.
 
 Write `<project>/script.md` (and `<project>/vocal-map.json` when the
 track has vocals). Report the delta, the section→scene map, **the probe
-`method`** (silence-derived, energy-derived, or interval-fallback), **and
-whether lyric timing is transcript-derived** (it must be — never
-brief-derived). Sum cannot be reconciled (e.g. provider max-duration
-forces more time than the song has) → **halt and surface the
-conflict** — do not pad silently.
+`method`** (so the operator sees whether cuts are silence-derived,
+energy-derived, or interval-fallback), **and whether lyric timing is
+transcript-derived** (it must be — never brief-derived). If the sum
+cannot be reconciled (e.g. provider max-duration forces more time than
+the song has), **halt and surface the conflict** — do not pad silently.
 
 ### Step 5: Validate before handoff
 

package/dist/agent-src/skills/source-discovery/SKILL.md

@@ -38,9 +38,9 @@ discover the real source  →  Evidence Report (Verified / Assumed / Gaps)  →
 Scaffold the report cheaply so it never gets skipped:
 
 ```bash
-./scripts-run src/scripts/evidence_report git-state            # fail-fast: abort if a rebase/merge/cherry-pick is in progress
-./scripts-run src/scripts/evidence_report init --task "<task>" # writes the gitignored session report
-./scripts-run src/scripts/evidence_report add --bucket verified --claim "users.email is unique" --source "db/schema/users.sql:23"
+npx tsx node_modules/@event4u/agent-config/src/scripts/evidence_report.ts git-state            # fail-fast: abort if a rebase/merge/cherry-pick is in progress
+npx tsx node_modules/@event4u/agent-config/src/scripts/evidence_report.ts init --task "<task>" # writes the gitignored session report
+npx tsx node_modules/@event4u/agent-config/src/scripts/evidence_report.ts add --bucket verified --claim "users.email is unique" --source "db/schema/users.sql:23"
 ```
 
 **Provenance on every item** (`observed_at` / `source` / `version`). Within a
@@ -175,10 +175,10 @@ the per-session Evidence Report above. Append to the knowledge intake —
 never write a tracked page mid-task:
 
 ```bash
-./scripts-run src/scripts/emit_knowledge_event --type api_shape_learned \
+npx tsx node_modules/@event4u/agent-config/src/scripts/emit_knowledge_event.ts --type api_shape_learned \
     --endpoint "<path>" --method "<verb>" --request-schema '<json>' --response-schema '<json>'
 
-./scripts-run src/scripts/emit_knowledge_event --type convention_detected \
+npx tsx node_modules/@event4u/agent-config/src/scripts/emit_knowledge_event.ts --type convention_detected \
     --pattern "<pattern>" --evidence "file:line" --sample-size <N> --scope project
 ```
 

package/dist/agent-src/skills/sql-writing/SKILL.md

@@ -12,8 +12,8 @@ packs:
 # sql
 
 
-> **Grounded corpus:** tuning decisions (indexes, keyset pagination, N+1,
-> trigram search, lock contention) ground via the
+> **Grounded corpus:** tuning decisions (indexes, keyset pagination,
+> N+1, trigram search, lock contention) ground via the
 > [`database`](../database/SKILL.md) corpus — `./scripts-run
 > <skills-root>/corpus-grounding/scripts/ground search
 > --manifest <skills-root>/database/data/manifest.json "<symptom>"`.

package/dist/agent-src/skills/stakeholder-tradeoff/SKILL.md

@@ -147,9 +147,10 @@ column is missing.
   becomes input to this skill for escalation. Boundary prose lives
   in [`docs/guidelines/cross-role-handoff.md`](../../../docs/guidelines/cross-role-handoff.md).
 - The trade-off is purely technical (perf vs storage, sync vs async)
-  — route to [`decision-record`](../decision-record/SKILL.md); one costly
-  choice on ≥ 3 options with user-weighted criteria → its § Weighted-matrix
-  mode (this skill answers WHO pays; that mode answers WHICH option wins).
+  — route to [`decision-record`](../decision-record/SKILL.md); if it is
+  one costly choice on ≥ 3 options with user-weighted criteria, its
+  § Weighted-matrix mode scores it (this skill answers WHO pays; that
+  mode answers WHICH option wins).
 - The dominant axis is risk, not stakeholder cost — route to
   [`risk-officer`](../risk-officer/SKILL.md).
 - The output is the locked decision artifact — hand off to