@event4u/agent-config 2.24.0 → 2.26.0

package/docs/contracts/kernel-membership.md

@@ -145,6 +145,23 @@ Future edits to any kernel rule must keep the Iron-Law SHA stable
 (or land a deliberate ADR-tracked SHA update). Cap re-raise requires
 a new ADR.
 
+### § 4.2 — Post-P2.2 kernel addition (`user-interrupt-priority`)
+
+After the P2.2 lock, `user-interrupt-priority` was admitted as the
+10th kernel rule. It satisfies criterion (1) (Iron Law: stop → ask
+→ resume on user-interrupt signals) and criterion (3a) (pre-send
+gate — must fire before continuing the current task). The smoke
+baseline is bumped accordingly:
+
+- `scripts/smoke/kernel.sh` — `EXPECTED_KERNEL_COUNT=10`,
+  `EXPECTED_FENCE_CARRIERS=9`.
+- `docs/contracts/smoke-contracts.md` § 3.1 — `10 kernel rules · 9
+  carry Iron-Law fences · 1 dispatch index · ≤ 2 budget breaches`.
+
+The § 4 / § 4.1 tables remain the locked P2.2 baseline (9-rule
+snapshot, 2026-05-06); the 10th rule is tracked separately here
+until the next kernel re-measurement.
+
 † **agent-authority swap candidate (P1.4 ADR).** Sonnet 4.5 argues
 this is a routing index (zero Iron Law fences, dispatches to other
 kernel rules) and should be `compress-and-keep` (auto-tier-3),

package/docs/contracts/provider-lifecycle.md

@@ -0,0 +1,122 @@
+---
+stability: beta
+keep-beta-until: 2026-08-15
+---
+
+# Provider Lifecycle — AI Video / Image / Audio Adapter Tiers
+
+> **Status:** active · **Stability:** beta · **Owner:** universal-platform-refinement Phase 3
+> · **Linter:** none (declarative contract; enforced agent-in-the-loop via [`provider-lifecycle-discipline`](../../.agent-src/rules/provider-lifecycle-discipline.md))
+> · **Source-of-truth template:** [`agents/.ai-video.xml.example`](../../agents/.ai-video.xml.example)
+
+Locks the lifecycle tagging used on every adapter under
+`scripts/ai-video/adapters/` (and future `scripts/ai-image/`,
+`scripts/ai-audio/` peers). The tag is declarative — it tells the
+agent what the maintainer's confidence in the adapter is, so the
+agent can refuse to *default* to an under-validated provider without
+the human noticing.
+
+## § 1 — Tiers
+
+| Tier | Meaning | Default-eligibility |
+|---|---|---|
+| `stable` | Maintainer-validated against a real API run at least once; dry-run output matches the documented contract; secret-redaction confirmed on a live response | **Yes** — `/video:*` / `/image:*` / `/audio:*` commands may default to a `stable` adapter |
+| `experimental` | Adapter shipped; structural shape matches the contract; **no real-API smoke run by a maintainer yet** | **No** — must be invoked explicitly (`--provider <id>`), never silently the default |
+| `deprecated` | Replaced by a successor; kept for one release window so consumer scripts can migrate | **No** — refusal-and-surface: the agent names the successor before running |
+| `community` | Contributed externally; maintained on a best-effort basis; behaviour outside the maintainer's smoke-test matrix | **No** — explicit opt-in only; the agent surfaces "community-tier provider" in the run summary |
+
+## § 2 — Promotion path
+
+`experimental → stable` requires three checkmarks on the same commit
+(or on a tightly-scoped follow-up commit referencing the original):
+
+1. **Real-API smoke run** — at least one live `submit / poll / fetch`
+   cycle (or `run` for sync adapters) against the documented
+   `default-model`, captured under
+   `agents/ai-video/smoke-traces/<provider>.md` with timestamp,
+   model id, and **redacted** response shape.
+2. **Secret-redaction confirmation** — the captured trace, re-read
+   through `scripts/ai-video/lib/redact.sh`, shows zero residual
+   key fragments.
+3. **Contract conformance** — the adapter's four-method shell
+   surface (`submit / poll / fetch / dry-run` *or* `run / dry-run`)
+   matches `scripts/ai-video/lib/adapter-contract.md` verbatim.
+
+A maintainer flipping the tier in `agents/.ai-video.xml.example`
+**and** the adapter header comment is the promotion event. There is
+no separate registry — the example file is the registry.
+
+## § 3 — Demotion criteria
+
+`stable → experimental` (or `stable → deprecated`) on any of:
+
+- **Provider API contract drift** that breaks the adapter against
+  the documented `default-model` for ≥ 7 calendar days without a
+  maintainer fix.
+- **Auth-flow change** that invalidates the redaction matchers in
+  `lib/redact.sh` until the matchers are extended.
+- **Successor adapter declared** (use `deprecated`, not
+  `experimental`, and record the successor in the header comment).
+
+Demotion is the maintainer's call; the rule does not auto-demote.
+
+## § 4 — Agent obligations
+
+When the agent picks a provider for a `/video:*` / `/image:*` /
+`/audio:*` run, it MUST:
+
+1. **Read** the `provider_lifecycle` tag from the adapter's header
+   comment **and** the matching `<provider id="…">` block in
+   `agents/.ai-video.xml.example` (or the operator's
+   `agents/.ai-video.xml`).
+2. **Refuse-and-surface** if the operator's resolved default is a
+   non-`stable` tier — name the tier and the path to this contract
+   document, then emit one clarifying question (per
+   [`ask-when-uncertain`](../../.augment/rules/ask-when-uncertain.md)):
+   either pick a `stable` provider, or confirm the non-stable run.
+3. **Record** in the run summary which tier the chosen adapter
+   carries — this is the audit log entry the agent-in-the-loop
+   model rests on.
+
+The agent never picks `deprecated` silently. If a successor is
+declared, the agent surfaces "X is deprecated; successor: Y" before
+running.
+
+## § 5 — Day-one assignment
+
+The five shipped adapters carry the following tiers on the day
+this contract lands (PR `universal-platform-refinement`):
+
+| Adapter | Kind | Tier | Rationale |
+|---|---|---|---|
+| `openai-images` | image | `experimental` | Structural shape conformant; no maintainer real-API smoke captured yet |
+| `gemini-veo` | video | `experimental` | Default video provider; no real-API smoke captured yet |
+| `kling` | video | `experimental` | Async contract conformant; no maintainer real-API smoke captured yet |
+| `higgsfield` | image+video | `experimental` | Capability-discovery path conformant; no real-API smoke captured yet |
+| `sora` | video | `experimental` | Structural-prompt path conformant; no real-API smoke captured yet |
+
+**All five start as `experimental` on day one.** The promotion to
+`stable` happens per-adapter, on the commit that records the first
+real-API smoke trace. This is conservative by construction: a
+`/video:*` run today resolves to a default that is `experimental`,
+so the agent surfaces the tier and asks before proceeding — the
+human is the policy decision point.
+
+The `<default-image-provider>` and `<default-video-provider>`
+entries in `agents/.ai-video.xml.example` remain unchanged
+(`openai-images` and `gemini-veo`). The tier tag does not change
+defaults; it changes whether the agent silently honours them.
+
+## § 6 — Versioning
+
+Tier rename or new tier is breaking (linter and adapter headers
+both flip); promotion / demotion of an individual adapter is not
+breaking. The Day-One Assignment table above is the per-release
+snapshot — older snapshots live in git history, not in this file.
+
+## See also
+
+- [`provider-lifecycle-discipline`](../../.agent-src/rules/provider-lifecycle-discipline.md) — the tier-2 routing rule that surfaces this contract when a provider is touched.
+- [`scripts/ai-video/lib/adapter-contract.md`](../../scripts/ai-video/lib/adapter-contract.md) — the four-method shell contract every adapter implements.
+- [`agents/.ai-video.xml.example`](../../agents/.ai-video.xml.example) — operator-facing provider configuration template (carries the tier tag inline).
+- [`agents/policies/media/README.md`](../../agents/policies/media/README.md) — the agent-in-the-loop enforcement model this contract participates in.

package/docs/contracts/smoke-contracts.md

@@ -51,11 +51,11 @@ constant in the script body and the row below.
 ### § 3.1 — Kernel (`scripts/smoke/kernel.sh`)
 
 ```
-9 kernel rules · 8 carry Iron-Law fences · 1 dispatch index · ≤ 2 budget breaches
+10 kernel rules · 9 carry Iron-Law fences · 1 dispatch index · ≤ 2 budget breaches
 ```
 
-- **9 kernel rules** — fixed by [`kernel-membership.md`](kernel-membership.md).
-- **8 carry Iron-Law fences** — measured 2026-05-16. `agent-authority`
+- **10 kernel rules** — fixed by [`kernel-membership.md`](kernel-membership.md).
+- **9 carry Iron-Law fences** — measured 2026-05-16. `agent-authority`
   is the **dispatch index** (priority table pointing at the other four
   authority rules); it is structurally exempt from the Iron-Law-fence
   requirement and listed in the script's `EXEMPT_FROM_FENCE` set.
@@ -70,13 +70,13 @@ constant in the script body and the row below.
 ### § 3.2 — Router (`scripts/smoke/router.sh`)
 
 ```
-75 router ids · 0 broken rule pointers · 35 routes_to refs · 2 missing contracts
+68 router ids · 0 broken rule pointers · 36 routes_to refs · 2 missing contracts
 ```
 
-- **75 ids** — 9 kernel + 24 tier_1 + 42 tier_2; every id resolves to
+- **68 ids** — 10 kernel + 23 tier_1 + 35 tier_2; every id resolves to
   `.agent-src/rules/<id>.md`.
 - **0 broken rule pointers** — hard assertion; smoke fails on any miss.
-- **35 routes_to refs** across tier_1 + tier_2; resolver honours the
+- **36 routes_to refs** across tier_1 + tier_2; resolver honours the
   four prefixes (`skill:`, `command:`, `guideline:`, `contract:`).
 - **2 missing contracts** — measured 2026-05-16:
   `contract:artifact-engagement-flow`,
@@ -130,7 +130,7 @@ the final baseline line) for CI summary parsing.
 
 | Symptom | Likely cause | Fix |
 |---|---|---|
-| `kernel.sh` reports > 8 missing fences | Kernel rule lost its Iron Law block during edit | Restore the fence; update `EXEMPT_FROM_FENCE` only for new dispatch indexes |
+| `kernel.sh` reports > 9 missing fences | Kernel rule lost its Iron Law block during edit | Restore the fence; update `EXEMPT_FROM_FENCE` only for new dispatch indexes |
 | `router.sh` reports > 0 broken pointers | `router.json` references an id without a rule file | Add the rule or remove the route — never edit the smoke baseline up |
 | `schema.sh` reports FAILs | A skill / rule lost a required field | Restore via [`scripts/schemas/skill.schema.json`](../../scripts/schemas/skill.schema.json) |
 | `skills.sh` 5/5 random sample fails | Hand-edit broke frontmatter or renamed directory without updating `name:` | Restore filename ↔ slug coupling |
@@ -139,6 +139,6 @@ the final baseline line) for CI summary parsing.
 
 - [`measurement-baseline.md`](measurement-baseline.md) — measurement substrate.
 - [`cost-enforcement.md`](cost-enforcement.md) — cost ladder, sibling smoke surface.
-- [`kernel-membership.md`](kernel-membership.md) — the 9-rule kernel set.
+- [`kernel-membership.md`](kernel-membership.md) — the 10-rule kernel set.
 - [`rule-router.md`](rule-router.md) — router contract.
 - `road-to-kernel-and-router.md` — kernel budget reduction path.

package/docs/decisions/ADR-011-domain-pack-readiness.md

@@ -0,0 +1,213 @@
+---
+adr: 011
+status: accepted
+date: 2026-05-17
+decision: domain-pack-readiness
+supersedes: —
+superseded_by: —
+phase: v2.x · universal-platform-refinement Phase 6
+type: prospective
+---
+
+# ADR-011 — Domain-Pack Readiness
+
+## Status
+
+**Accepted** · 2026-05-17 · one-round council pass complete
+(`agents/council-responses/adr-011-domain-pack-readiness.json/debate-round-1.json`, actual spend $0.0300). <!-- council-ref-allowed: ADR decision trace; convergence summary inline in §Council-debate-trace -->
+Split verdict — Anthropic accepted *with* tightened trigger; OpenAI
+accepted as written. The host folded Anthropic's structural critique
+into the trigger and added the escape clause both members' reasoning
+implied. Trace under §Council-debate-trace.
+
+## Context
+
+`event4u/agent-config` shipped its first heavyweight domain capability
+in PR #176 (AI Video Pipeline, merged at `2.24.0`): 5 provider
+adapters, 3 personas, 5 skills, the `/video:*` command cluster, a
+Banana-Arc pixel-similarity regression harness, secret redaction at
+every adapter boundary, and 50 roadmap steps clean. The strategic
+review that followed gave the work `8.9 / 10` overall (engineering
+`9.7`, governance `9.2`, UX `10`) but flagged scope discipline at
+`6.8 / 10` and named a `8.9 → 9.6` target delta. The named gap is
+*not* engineering — it is the positioning / role-guide / rule-layer
+surface that did not catch up to the new capability. The current
+roadmap (`universal-platform-refinement`) closes that gap in Phases
+1–5; Phase 6 records the *non-extraction* decision so the deferral is
+auditable.
+
+The pressure to extract video into a separately-installable
+"domain pack" comes from three places:
+
+1. The strategic review's `8.9 → 9.6` argument — "make the future
+   audio / image / docs / exports domains land cheaply". Cited at
+   `agents/roadmaps/universal-platform-refinement.md` lines 19 and 132.
+2. PR #176's scope-discipline score (`6.8 / 10`) — the load-bearing
+   data point against premature extraction. Cited at line 19, 117.
+3. The predecessor council's explicit rejection of milestone-split
+   shipping of the video pipeline. Trace:
+   [`archive/ai-video-pipeline.md` § Divergences (no consensus)](../../agents/roadmaps/archive/ai-video-pipeline.md#L162-L164):
+   *"Single-PR vs. milestone split — Reviewer B recommended splitting
+   into milestone PRs; Sonnet R3 and GPT-4o final pass both reject
+   this, citing the roadmap's explicit single-PR iron constraint and
+   the dead-code risk of partial states. Host: the iron constraint
+   stands."* Same reasoning applies one level up: extracting video
+   today creates a domain-pack abstraction with no peer to share with
+   and a dead-code risk in the not-yet-built domains.
+
+The repository currently has exactly **one** heavyweight domain
+(video). Audio, image, docs, and exports are named future concerns —
+none is built. An abstraction whose only consumer is the abstraction
+itself is a structural liability, not an asset.
+
+## Decision
+
+> **The platform stays thin-root and ships future domains (audio,
+> image, docs, exports) as in-repo capability bundles, not as
+> separately-installable packs, until at least two independent
+> domains exist with overlapping execution surfaces.**
+
+"Overlapping execution surfaces" means shared code beyond the kernel
++ router — e.g. two adapters that both implement the four-method
+shell contract, two skill clusters that both consume the
+`media-governance-routing` rule, two domains that both need
+provider-lifecycle tiering. The video adapters alone do not satisfy
+this — they are a single execution surface.
+
+## Consequences
+
+### (i) What stays under `.agent-src.uncompressed/` today
+
+The complete video capability stays in the existing flat layout —
+no path changes, no symlink relocation, no namespace prefix:
+
+- `.agent-src.uncompressed/skills/{character-consistency,motion-choreographer,pixar-storyteller,scene-expander,video-director}/`
+- `.agent-src.uncompressed/personas/{ai-video-technical-director,hollywood-director}.md`
+  (the third video persona, `pixar-storyboard-artist`, was folded
+  into `skills/pixar-storyteller/` per the persona-cap council pass
+  recorded in `persona-governance`)
+- `.agent-src.uncompressed/commands/video/{from-script,scene,storyboard,stitch}.md`
+- `scripts/ai-video/` (the 5 adapter scripts + `lib/`)
+- `agents/policies/media/` (Phase 2 output — already structured as
+  a project-local policy directory, *not* a pack)
+
+### (ii) The trigger that flips this decision
+
+The non-extraction stance is **falsifiable**. The trigger is split
+into a *design gate* (fires before domain 2 is built) and two
+*confirmation gates* (fire after domain 2 ships) — sequenced this way
+to avoid the "two-domain monolith" trap the council flagged in
+round 1 (Anthropic, Option 2): if condition 1 only fires *after*
+domain 2 is built, the shared infrastructure is already entangled
+and extraction is materially harder than predicting overlap in
+advance.
+
+**Design gate (fires BEFORE domain 2 implementation starts):**
+
+1. **Overlap-prediction document.** Before the first commit on a
+   second heavyweight domain (audio, image, docs, exports, or other),
+   write `docs/contracts/domain-pack-overlap-inventory.md` listing
+   ≥ 3 structural patterns *predicted* to be shared between video
+   and the new domain (e.g. shared adapter contract, shared
+   governance routing, shared provider-lifecycle declaration, shared
+   persona-cap policy). Each prediction includes a falsifiable test
+   that confirms or refutes it after domain 2 ships. If ≥ 3 testable
+   predictions cannot be written, the domain is not yet a candidate
+   for shared abstraction — build it in-repo, revisit when patterns
+   emerge.
+
+**Confirmation gates (fire AFTER domain 2 ships):**
+
+2. **Heavyweight-domain landing.** A second domain has landed in
+   `main` matching the PR #176 shape: adapter cluster + skill
+   cluster + command cluster + governance rule + policy directory.
+   One-skill additions do not count.
+3. **Shared-abstraction stability.** The patterns named in the
+   prediction document have shipped without breaking changes for at
+   least one minor release. Stability proves the predictions were
+   real, not refactoring churn.
+
+**Escape clause (Anthropic round-1 critique, folded back):** if all
+three gates fire and extraction is then judged "too expensive" by
+the team, **this decision was wrong**. Re-open the ADR and record
+the failure mode — the trigger structure is one-way unless this
+clause is honoured. Without it, the ADR becomes a one-way door
+disguised as a two-way door.
+
+The placeholder roadmap
+[`agents/roadmaps/domain-pack-extraction-when-triggered.md`](../../agents/roadmaps/domain-pack-extraction-when-triggered.md)
+holds the marker; status `draft` keeps it dashboard-suppressed until
+the design gate fires.
+
+### (iii) What is **not** extracted today
+
+Explicitly enumerated so a future reader does not mistake silence
+for ambiguity:
+
+- The five video adapters (`gemini-veo`, `kling`, `openai-images`,
+  `higgsfield`, `sora`) — stay in `scripts/ai-video/`.
+- The two remaining video personas — stay in `.agent-src.uncompressed/personas/`.
+- The `/video:*` command cluster — stays in `.agent-src.uncompressed/commands/video/`.
+- The `media-governance-routing` rule + `agents/policies/media/`
+  policy files — stay where Phase 2 placed them.
+- The provider-lifecycle contract + the `provider-lifecycle-discipline`
+  rule — stay where Phase 3 placed them.
+- The three Phase 4 test files (`tests/test_ai_video_blueprint_schema.py`,
+  `test_prompt_optimization.py`, `test_ai_video_adapter_contract.py`)
+  — stay in the root `tests/` tree.
+
+## Alternatives Considered
+
+### A) Extract video into `agents/domain-packs/ai-video/` today
+
+Rejected. The extraction creates an abstraction with no peer, so the
+shape of the pack interface is determined by exactly one consumer.
+When the second domain arrives, the interface is likely wrong (cited
+predecessor council reasoning on milestone-split: dead-code risk of
+partial states). The strategic review's `8.9 → 9.6` argument is
+**real** but **not unlocked by extracting today** — see roadmap §Notes
+line 132.
+
+### B) Ship the placeholder roadmap as `proposed` instead of `draft`
+
+Rejected. A `proposed` roadmap appears in the dashboard and creates
+implicit pressure to schedule it. A `draft` marker keeps the trigger
+visible to future maintainers without scheduling work that depends
+on conditions that do not yet hold.
+
+### C) Pin a date for re-evaluation
+
+Rejected. The trigger is structural (two domains + overlap inventory),
+not temporal. Pinning a date (e.g. "review 2027-Q1") replaces a
+condition-based gate with a calendar-based one, which `no-roadmap-references`
+treats as a smell.
+
+## Council-debate trace
+
+One round · 2 members · actual spend $0.0300 · raw responses at
+[`agents/council-responses/adr-011-domain-pack-readiness.json/debate-round-1.json`](../../agents/council-responses/adr-011-domain-pack-readiness.json/debate-round-1.json). <!-- council-ref-allowed: ADR decision-trace to originating council response -->
+
+| Member | Pick | Core argument | Folded back? |
+|---|---|---|---|
+| `anthropic/claude-sonnet-4-5` | **Option 2** (accept with tightened trigger) | Trigger as originally written is waterfall-sequenced (build → discover → stabilise) — condition 1 only fires *after* domain 2 is built, creating the "two-domain monolith" trap. Fix: move overlap-prediction to a *design gate* before domain 2 implementation, plus add an escape clause naming the failure mode when extraction is later judged too expensive. | **Yes** — Consequences §(ii) split into design gate + confirmation gates; escape clause added verbatim. |
+| `openai/gpt-4o` | **Option 1** (accept as written) | Triggers are structural, not temporal — appropriate guard against premature abstraction. Secondary signal worth tracking: developer-sentiment / community feedback on perceived lack of shared infrastructure. | **Partial** — host did not promote qualitative signals to gates (would conflict with the "structural, not temporal" principle both members affirmed), but the escape clause covers the team-cost case Anthropic named and OpenAI implied. |
+
+### Host verdict
+
+Anthropic's structural critique is load-bearing: the original trigger
+was sequenced as a waterfall where the gating condition could not be
+checked until after the gate had implicitly been passed. The fix —
+moving overlap-prediction to a design-stage document — is a strict
+improvement that costs nothing today (no domain 2 exists; no design
+gate to clear). Folding the escape clause closes the one-way-door
+risk both members' reasoning pointed at, even though only Anthropic
+named it explicitly.
+
+OpenAI's qualitative-signal point is noted but not promoted to a
+gate: every "is the lack of shared infrastructure slowing us down?"
+question is answerable by writing the overlap-prediction document
+and seeing whether ≥ 3 testable predictions emerge. The design gate
+absorbs the qualitative signal into a structural check.
+
+Status: `proposed → accepted` with the council-driven trigger
+revision and escape clause in place.

package/docs/decisions/INDEX.md

@@ -14,6 +14,7 @@ _Auto-generated by `scripts/adr/regenerate_index.py`. Do not edit._
 | [ADR-008](ADR-008-installed-tools-manifest.md) | Committed Installed Tools Manifest Separate From Settings | proposed | 2026-05-12 | — |
 | [ADR-009](ADR-009-event4u-namespace.md) | Event4U Namespace And Claude Desktop Zip Bundles | accepted | 2026-05-13 | — |
 | [ADR-010](ADR-010-profile-pack-preset-boundary.md) | Profile Pack Preset Boundary | proposed | 2026-05-16 | — |
+| [ADR-011](ADR-011-domain-pack-readiness.md) | Domain Pack Readiness | accepted | 2026-05-17 | — |
 
 ## Unnumbered (legacy)
 

package/docs/getting-started-by-role.md

@@ -16,6 +16,16 @@
 - [`messaging-architecture`](../.agent-src/skills/messaging-architecture/SKILL.md) — primary message + supporting proofs + audience-by-message matrix.
 - [`editorial-calendar`](../.agent-src/skills/editorial-calendar/SKILL.md) — evergreen vs campaign vs reactive cadence across channels.
 
+### Video
+
+- [`/video:from-script`](../.agent-src/commands/video/from-script.md) — end-to-end pipeline: script → character-locked image → motion+audio prompt → provider render → stitched clip.
+- [`/video:storyboard`](../.agent-src/commands/video/storyboard.md) — expand a one-line idea into the 12-block Cinematic Scene Blueprint (provider-agnostic).
+- [`/video:scene`](../.agent-src/commands/video/scene.md) — render a single scene from an existing blueprint against the configured provider adapter.
+- [`/video:stitch`](../.agent-src/commands/video/stitch.md) — assemble rendered scenes into the final clip via ffmpeg.
+- [`character-consistency`](../.agent-src/skills/character-consistency/SKILL.md) — lock identity tokens (silhouette, palette, wardrobe, prop) so a character stays visually identical across scenes.
+
+`AIV_DRYRUN=true` is the mandatory default — no provider call, no spend until you opt in.
+
 **Install path:** **MCP recommended.** Claude Desktop is the lowest-friction entry; no terminal required. See [`docs/mcp.md`](mcp.md). CLI install works too if you already use a code editor.
 
 ---

package/docs/getting-started.md

@@ -106,7 +106,7 @@ Your agent is now:
 - **Respecting your codebase** — no conflicting patterns
 - **Following standards** — consistent code quality
 
-This is enforced automatically by 79 rules. No configuration needed.
+This is enforced automatically by 72 rules. No configuration needed.
 
 ---
 

package/docs/guidelines/php/api-design.md

@@ -2,7 +2,7 @@
 
 > API conventions — response format, status codes, pagination, error handling, rate limiting, route naming.
 
-**Related Skills:** `api-design`, `api-endpoint`, `api-testing`
+**Related Skills:** `api-design`, `laravel-api-endpoint`, `api-testing`
 **Related Guidelines:** [controllers.md](controllers.md), [resources.md](resources.md)
 
 ## Response Format

package/docs/guidelines/php/controllers.md

@@ -2,7 +2,7 @@
 
 > Project-specific controller conventions. Thin controllers, single-action pattern, OpenAPI annotations.
 
-**Related Skills:** `api-endpoint`, `laravel`, `openapi`
+**Related Skills:** `laravel-api-endpoint`, `laravel`, `openapi`
 **Related Guidelines:** [validations.md](validations.md), [resources.md](resources.md)
 
 ## Core Rules

package/docs/guidelines/php/resources.md

@@ -2,7 +2,7 @@
 
 > Project-specific API Resource conventions. Base class, versioning (v1/v2), OpenAPI schemas.
 
-**Related Skills:** `api-endpoint`, `api-design`, `openapi`
+**Related Skills:** `laravel-api-endpoint`, `api-design`, `openapi`
 **Related Guidelines:** [controllers.md](controllers.md)
 
 ## Core Rule

package/docs/guidelines/php/validations.md

@@ -2,7 +2,7 @@
 
 > Project-specific FormRequest conventions. Array syntax, route params, property mapping.
 
-**Related Skills:** `laravel-validation`, `api-endpoint`
+**Related Skills:** `laravel-validation`, `laravel-api-endpoint`
 **Related Guidelines:** [controllers.md](controllers.md)
 
 ## Core Rules

package/docs/personas.md

@@ -5,32 +5,79 @@ skill — not sub-agents, not execution modes. Each persona shapes
 *what* the agent looks for in a diff, plan, or artifact; the host
 identity, tools, and workflow stay the same.
 
-This page catalogs the 11 personas shipped with `event4u/agent-config`
-and explains how `personas:` (lens axis) interacts with `/mode`
-(role-mode axis).
-
-## Catalog
-
-| ID | Role | Tier | Lens summary |
-|---|---|---|---|
-| `developer` | Developer | core | Pragmatic implementer voice — what's the smallest correct change? |
-| `senior-engineer` | Senior Engineer | core | Long-horizon impact — what does this look like in 6 months? |
-| `product-owner` | Product Owner | core | Outcome over output — does this move the user metric? |
-| `stakeholder` | Stakeholder | core | Risk and politics — who owns the rollback if this fails? |
-| `critical-challenger` | Critical Challenger | core | Devil's-advocate voice — what assumption is load-bearing here? |
-| `ai-agent` | AI Agent | core | Tool-economy voice — token cost, prompt clarity, automation seam. |
-| `qa` | QA | specialist | Test coverage and regression gates. |
-| `backend-architect` | Backend Architect | specialist | Service-layer boundaries, transaction scope, contract changes. |
-| `eloquent-tamer` | Eloquent Tamer | specialist | N+1, query shape, ORM idioms that melt the database. |
-| `security-engineer` | Security Engineer | specialist | OWASP-shaped failure modes, secret leakage, trust boundaries. |
-| `frontend-engineer` | Frontend Engineer | specialist | Component lifecycle, reactive state, hydration boundaries. |
-
-Tier rules:
-
-- **Core (6)** — always-loaded cast. 5 sections (Focus · Mindset · Unique Questions · Output Expectations · Anti-Patterns), ≤ 120 lines.
-- **Specialist (5)** — opt-in lenses. 7 sections (Core-5 + Critical Rules + Workflows), ≤ 100 lines.
-
-Schema contract: [`docs/contracts/persona-schema.md`](contracts/persona-schema.md).
+This page catalogs the **24 active personas** shipped with
+`event4u/agent-config` (6 core + 18 specialists), plus the 5
+**advisor** personas in `personas/advisors/`. It also explains how
+`personas:` (lens axis) interacts with `/mode` (role-mode axis).
+Removed personas are deleted in-commit (no soak window) — see
+[`persona-governance § Deprecation path`](../.agent-src/rules/persona-governance.md).
+
+## Catalog — Core (always-loaded, 6)
+
+| ID | Role | Wing | Owner | Lens summary |
+|---|---|---|---|---|
+| `developer` | Developer | — | package | Pragmatic implementer voice — what's the smallest correct change? |
+| `senior-engineer` | Senior Engineer | — | package | Long-horizon impact — what does this look like in 6 months? |
+| `stakeholder` | Stakeholder | — | package | Risk and politics — who owns the rollback if this fails? |
+| `critical-challenger` | Critical Challenger | — | package | Devil's-advocate voice — what assumption is load-bearing here? |
+| `ai-agent` | AI Agent | — | package | Tool-economy voice — token cost, prompt clarity, automation seam. |
+
+Note: `product-owner` was reclassified to **specialist** at v2.0 — see below.
+
+## Catalog — Specialists (opt-in, 18 active)
+
+| ID | Role | Wing | Owner | Lens summary |
+|---|---|---|---|---|
+| `qa` | QA | — | package | Test coverage and regression gates. |
+| `backend-architect` | Backend Architect | — | package | Service-layer boundaries, transaction scope, contract changes. |
+| `eloquent-tamer` | Eloquent Tamer | — | package | N+1, query shape, ORM idioms that melt the database. |
+| `security-engineer` | Security Engineer | — | package | OWASP-shaped failure modes, secret leakage, trust boundaries. |
+| `frontend-engineer` | Frontend Engineer | — | package | Component lifecycle, reactive state, hydration boundaries. |
+| `product-owner` | Product Owner | — | package | Outcomes named, AC unfalsifiable, scope on record. |
+| `tech-writer` | Tech Writer | — | package | Release narratives, READMEs, AGENTS.md thin. |
+| `revops-maintainer` | RevOps Maintainer | — | package | Contributor lifecycle, package adoption funnel, release readiness. |
+| `discovery-lead` | Discovery Lead | — | package | Switch events, falsifiable hypotheses, theme ranking. |
+| `hollywood-director` | Hollywood Director (`ai-video`) | — | package | Live-action lens, lighting, blocking, negative constraints. |
+| `ai-video-technical-director` | AI Video Technical Director (`ai-video`) | — | package | Provider tuning — Veo / Kling / Sora / Higgsfield / OpenAI grammar. |
+| `cmo` | CMO | 3 | package | Positioning anchored, messaging stacked, launches sequenced. |
+| `growth-pm` | Growth PM | 3 | package | Leaky-bucket vs growth-loop classified, activation correlated. |
+| `customer-success-lead` | Customer Success Lead | 3 | package | TTFV falsifiable, churn cause split, expansion pulled, NRR. |
+| `revops` | RevOps | 3 | package | Stage exit criteria, MEDDIC slots, forecast falsifiable. |
+| `engineering-manager` | Engineering Manager | 4 | package | 1:1 cadence, hiring loop, throughput-vs-morale tradeoff. |
+| `people-strategist` | People Strategist | 4 | package | Team shape, comp bands, ramp definitions, feedback craft. |
+| `finance-partner` | Finance Partner | 4 | package | Unit economics, runway, scenarios, the next 18 months. |
+| `strategist` | Strategist | 4 | package | Build-vs-buy, market entry, moat, vision, contracts, privacy. |
+
+## Per-domain count (persona-governance cap: max 2 specialists per domain)
+
+| Domain | Active specialists | Within cap |
+|---|---|---|
+| `ai-video` | `hollywood-director`, `ai-video-technical-director` | ✅ 2/2 |
+| GTM (Wing 3) | `cmo`, `growth-pm`, `customer-success-lead`, `revops` | ✅ (wing, not domain) |
+| Ops / Money (Wing 4) | `engineering-manager`, `people-strategist`, `finance-partner`, `strategist` | ✅ (wing, not domain) |
+| Backend | `backend-architect`, `eloquent-tamer` | ✅ 2/2 |
+
+Per-domain count is enforced by `scripts/lint_persona_governance.py` (wired into `task ci`).
+
+## Advisors (`personas/advisors/`, 5)
+
+Adversarial / second-opinion voices invoked by `ai-council` debates,
+not cited by skills directly:
+
+| ID | Lens |
+|---|---|
+| `contrarian` | Opposing the consensus position |
+| `executor` | Shipping bias — what's the minimum to land it? |
+| `expansionist` | Scope-widening — what else does this unlock? |
+| `first-principles` | Refuses analogy — derive from physics of the problem |
+| `outsider` | Naive reader — does this hold without prior context? |
+
+## Tier rules
+
+- **Core (≤ 6)** — always-loaded cast. 5 sections (Focus · Mindset · Unique Questions · Output Expectations · Anti-Patterns), ≤ 120 lines.
+- **Specialist** — opt-in lenses. 7 sections (Core-5 + Critical Rules + Workflows). Line cap is wing-scoped: ≤ 100 (no wing / Wings 1–2), ≤ 140 (Wings 3–4) per [`persona-schema § 4`](contracts/persona-schema.md).
+
+Schema contract: [`docs/contracts/persona-schema.md`](contracts/persona-schema.md). Governance rule: [`persona-governance`](../.agent-src/rules/persona-governance.md).
 
 ## When to invoke a persona
 

package/docs/profiles.md

@@ -25,10 +25,15 @@ Next.js · React · Node. **Preset default: `balanced`.**
 ## ✍️ `content_creator` — writers, ghostwriters, marketers
 
 Draft in someone else's voice, plan a quarter of content, ship a
-launch announcement. `/ghostwriter` fetches and writes against a
-public-figure voice profile; `/post-as` is the same primitive for
-your own voice (`.agent-user.md`); `voice-and-tone-design` and
-`messaging-architecture` lock the brand frame before any copy ships.
+launch announcement, render a cinematic AI video. `/ghostwriter`
+fetches and writes against a public-figure voice profile; `/post-as`
+is the same primitive for your own voice (`.agent-user.md`);
+`voice-and-tone-design` and `messaging-architecture` lock the brand
+frame before any copy ships; `/video:from-script` and `/video:storyboard`
+drive the AI video pipeline (script → character-locked image →
+motion+audio prompt → provider render → stitched clip), with
+`character-consistency` locking identity tokens across scenes and
+`AIV_DRYRUN=true` as the cost-safety default.
 **Preset default: `balanced`.**
 [Profile YAML](../.agent-src.uncompressed/profiles/content_creator.yml) ·
 [Role guide](getting-started-by-role.md#creator-writer-marketer-indie-content-shop).

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@event4u/agent-config",
-    "version": "2.24.0",
+    "version": "2.26.0",
     "description": "Shared agent configuration \u2014 skills, rules, commands, guidelines, and templates for AI coding tools",
     "license": "MIT",
     "private": false,