@event4u/agent-config 5.10.0 → 6.0.0

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

@@ -0,0 +1,139 @@
+---
+model_tier: medium
+name: livewire
+description: "Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.py`. Covers reactive state, events, lifecycle hooks, and component/view separation."
+domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+trust:
+  level: professional
+install:
+  default: false
+  removable: true
+---
+
+# livewire
+
+> **Grounded stack guidance:** pull idiomatic Blade/UI Do/Don't + docs URLs
+> via `ground.py search --manifest <skills-root>/design-intelligence/data/manifest.json
+> --stack laravel "<topic>"` (UI-scoped corpus). See
+> [`design-intelligence`](../design-intelligence/SKILL.md).
+
+## Positioning — dispatched, not standalone
+
+`livewire` is the **apply-step executor** for the Livewire stack. It is
+invoked by [`directives/ui/apply.py`](../../templates/scripts/work_engine/directives/ui/apply.py)
+once the design brief is locked, and revisited by `review.py` /
+`polish.py` during the design-review loop. It does **not** own the
+flow, does **not** drive the audit, and does **not** lock the design.
+
+| Concern | Owner |
+|---|---|
+| Audit + token inventory (mandatory pre-step) | [`existing-ui-audit`](../existing-ui-audit/SKILL.md) |
+| Design brief (layout / states / microcopy) | [`directives/ui/design.py`](../../templates/scripts/work_engine/directives/ui/design.py) |
+| Universal design heuristics | [`fe-design`](../fe-design/SKILL.md) |
+| Static Blade partials inside the view | [`blade-ui`](../blade-ui/SKILL.md) |
+| Flux primitives inside the view | [`flux`](../flux/SKILL.md) |
+
+## When to use
+
+Cite this skill when:
+
+- `state.stack.frontend == "livewire"` and `directives/ui/apply.py` dispatches to this skill
+- Editing or creating Livewire components — reactive state, forms, tables, real-time updates
+
+Do NOT use when:
+
+- Static Blade views with no interactivity (use `blade-ui` skill)
+- Flux UI primitives (use `flux` skill — `livewire` composes Flux internally)
+- Driving the full UI flow yourself — that is the `directives/ui/` orchestrator
+
+## Procedure: Create a Livewire component
+
+### Step 0: Inspect
+
+1. Detect Livewire version — `composer.json` for `livewire/livewire`.
+   - v3: `#[Layout]`, `#[Title]`, property attributes.
+   - v2: `$layout`, `$listeners`, method-based hooks.
+2. Check existing components — `app/Livewire/` or `app/Http/Livewire/`.
+3. Check views — `resources/views/livewire/`.
+
+### Step 1: Create component class
+
+1. `declare(strict_types=1)`, `final` class.
+2. Typed public properties for state — keep minimal.
+3. `#[Locked]` for tamper-proof properties.
+4. `#[Url]` for URL-synced properties.
+
+### Step 2: Implement actions
+
+1. Public methods callable from frontend.
+2. Validate before processing: `$this->validate()`.
+3. `$this->dispatch()` for cross-component communication (v3).
+
+### Step 3: Create view
+
+1. One root element (`<div>`).
+2. `wire:key` on dynamic lists.
+3. `wire:loading` for user feedback.
+4. `wire:model.live` for real-time updates (v3 default is deferred).
+
+### Step 4: Test
+
+- `Livewire::test(ComponentClass::class)`
+- `->set()`, `->call()`, `->assertSee()`, `->assertHasNoErrors()`
+
+## Conventions
+
+→ See guideline `php/livewire.md` for state management, forms, performance, Alpine.js, templates.
+
+## Output format
+
+1. Livewire component class with typed properties and actions
+2. Blade view with wire: bindings and Flux components
+
+### Review pass — a11y findings + preview envelope
+
+When this skill is dispatched by `directives/ui/review.py` (test slot)
+or `directives/ui/polish.py` (verify slot) — i.e. a review/polish run,
+not the initial apply — it also emits:
+
+- `state.ui_review.a11y` — `{violations: [{rule, selector, severity}, ...],
+  severity_floor?, accepted_violations?}`. Use the same `(rule, selector)`
+  shape as `state.ui_audit.a11y_baseline` so the engine's de-dup matches
+  pre-existing entries on replay. Omit the envelope on apply passes; the
+  engine's `_apply_a11y_gate` only fires when a baseline is present.
+- `state.ui_review.preview` — `{render_ok: bool, screenshot_path?,
+  dom_dump_path?, error?, skipped?}`. `render_ok: false` with `error`
+  populated triggers the `preview_render_failed` halt; `render_ok: true`
+  with `screenshot_path` threads the screenshot into the delivery
+  report's `artifacts` list. Browser tooling (Playwright/Cypress/…) is
+  a consumer-project dependency — this package does not ship one.
+
+Polish dispatch: when the dispatcher skips `review` because a previous
+review pass already returned `SUCCESS`, this skill MUST itself
+synthesise the updated `state.ui_review.findings` (including any
+remaining `a11y_violation` entries) so the engine's gate sees the
+current state on the next polish round.
+
+## Gotcha
+
+- Public properties serialize between requests — don't put large objects in state.
+- `wire:model` is deferred by default in v3 — use `wire:model.live` for real-time.
+- `$this->redirect()` + `$this->dispatch()` in same method — only redirect executes.
+
+## Do NOT
+
+- Do NOT put heavy computation in `render()` — it runs on every update.
+- Do NOT nest Livewire components deeply — keep the tree shallow.
+- Do NOT expose sensitive data as public properties.
+
+## Auto-trigger keywords
+
+- Livewire
+- reactive component
+- wire:model
+- lifecycle
+- real-time UI

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

@@ -0,0 +1,130 @@
+---
+model_tier: lite
+name: md-language-check
+description: "Use BEFORE saving any .md under .augment/, dist/agent-src*/, or agents/ — scans umlauts, German function words, and German phrases outside DE:/EN: anchor blocks. Hard gate per language-and-tone."
+domain: process
+execution:
+  type: assisted
+  handler: shell
+  timeout_seconds: 30
+  allowed_tools: []
+  command:
+    - python3
+    - scripts/check_md_language.py
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+---
+
+# md-language-check
+
+## When to use
+
+Fire this skill **before** writing or saving any `.md` file under:
+
+- `.agent-src.uncondensed/` (source of truth — skills, rules, commands, guidelines, templates, contexts)
+- `dist/agent-src/` (condensed projection)
+- `.augment/` (local agent projection)
+- `agents/` (project-specific roadmaps, contexts, sessions)
+
+Per [`language-and-tone`](../../rules/language-and-tone.md) § "`.md` files
+are ALWAYS English" and § Detection heuristic, every `.md` file in those
+trees must be English. Bilingual content lives only in labeled
+`DE: … · EN: …` anchor blocks.
+
+Do NOT use when:
+
+- Editing project content outside the trees listed above (READMEs of
+  consumer projects, application docs that follow a different policy)
+- Reviewing chat history files (`agents/runtime/.agent-chat-history` is JSONL, not `.md`)
+- Inspecting non-`.md` files — the checker rejects them with a warning
+
+## Procedure
+
+### 1. Identify the file(s) about to be saved
+
+Collect the absolute or repo-relative path of every `.md` file the
+agent is about to create or modify in this turn. Multiple files in
+one turn → pass them all to a single invocation.
+
+### 2. Run the checker
+
+```bash
+python3 scripts/check_md_language.py <path> [<path> …] [--format json]
+```
+
+Exit codes:
+
+- `0` → no German content detected, save proceeds
+- `1` → violations found, save is **blocked** until they are resolved
+  or explicitly suppressed
+- `3` → internal error (unreadable file, decode failure)
+
+### 3. Resolve findings
+
+For every violation:
+
+| Kind | Likely cause | Fix |
+|---|---|---|
+| `umlaut` | German prose leaked into body text | Translate the sentence to English |
+| `de_word` | German function word in unquoted prose | Translate; or move into a `DE: … · EN: …` block if intentional bilingual anchor |
+
+If the line is meta-documentation that **must** quote German tokens
+(e.g. the detection heuristic in `language-and-tone.md` itself),
+append `<!-- md-language-check: ignore -->` at the end of that single
+line — never as a wholesale silencer.
+
+### 4. Re-run and confirm
+
+After every fix, re-run the checker on the same paths. Save only
+proceeds on exit `0`.
+
+## Allowed escape hatches
+
+- **Labeled anchor block** — lines starting with `DE:` / `- DE:` /
+  `* DE:` (and the same for `EN:`) are skipped automatically. Use this
+  for intent-based opt-in / opt-out anchors.
+- **Fenced code blocks** — `\`\`\` … \`\`\`` content is exempt, so
+  shell snippets, JSON fixtures, and quoted user input in code
+  blocks pass through untouched.
+- **Inline code** — backtick spans are stripped before scanning;
+  identifiers like `für_test` inside backticks do not flag.
+- **Per-line marker** — append `<!-- md-language-check: ignore -->`
+  to a line that genuinely needs to quote a German token in body
+  prose (rare; reserved for the rules that document the heuristic).
+
+## Output format
+
+1. One-line summary: `clean` or `N violation(s) found`
+2. Per violation: `file:line — kind \`match\`` plus the offending line
+3. Next action: translate, move into a `DE:`/`EN:` block, add the
+   per-line ignore marker, or revert the change
+
+## Gotchas
+
+- The checker scans `.md` files only; passing a non-`.md` path emits a
+  warning and skips it
+- The detection word list is intentionally short and conservative —
+  a clean run is **necessary but not sufficient**; the agent still
+  owns the final language judgement
+- Frontmatter (`--- … ---` at file head) is exempt; descriptions and
+  YAML keys can use international characters where the schema allows
+
+## Do NOT
+
+- Do NOT silence the checker by deleting trigger words from
+  `scripts/check_md_language.py`; extend the allow-list (anchor
+  blocks, ignore marker) instead
+- Do NOT add the ignore marker to body prose just to push a save
+  through; the marker is for meta-documentation that quotes tokens,
+  not a generic mute
+- Do NOT skip the gate "because the file is small" — `language-and-tone`
+  § Detection heuristic applies to every save under the four trees
+
+## Cloud Behavior
+
+On cloud surfaces (Claude.ai Web, Skills API) the checker script is
+not shipped, so this skill is **inert** — the agent applies the
+heuristic from [`language-and-tone`](../../rules/language-and-tone.md)
+manually before emitting the file.

package/dist/agent-src/skills/merge-conflicts/SKILL.md

@@ -0,0 +1,195 @@
+---
+model_tier: inherit
+name: merge-conflicts
+description: "Use when the user has merge conflicts or says \"resolve conflicts\". Understands conflict markers, resolution strategies, and verification workflow."
+domain: process
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+---
+
+# merge-conflicts
+
+## When to use
+
+Use this skill when:
+- A merge or rebase produces conflicts
+- The user asks to "resolve conflicts", "fix merge", or "update branch"
+- CI fails because the branch is behind main
+- The `prepare-for-review` command encounters conflicts
+
+## Procedure: Resolve merge conflicts
+
+### 1. Understand the situation
+
+Before touching any conflict:
+
+```bash
+# What files have conflicts?
+git diff --name-only --diff-filter=U
+
+# What branch are we merging from/into?
+git log --oneline -1 HEAD
+git log --oneline -1 MERGE_HEAD   # or REBASE_HEAD for rebase
+```
+
+### 2. Read both sides
+
+For each conflicted file:
+
+1. **Read the full conflict** — not just the markers, but the surrounding context.
+2. **Understand "ours"** — what does the current branch intend?
+3. **Understand "theirs"** — what does the incoming branch intend?
+4. **Check if both changes are needed** — often both sides added different things.
+
+### 3. Resolution strategies
+
+| Situation | Strategy |
+|---|---|
+| Both sides changed the same line differently | **Ask the user** — this is a semantic conflict |
+| Both sides added different code in the same area | **Keep both** — combine the additions in logical order |
+| One side deleted, other side modified | **Ask the user** — deletion intent vs modification intent |
+| Lock file conflicts (`composer.lock`, `package-lock.json`) | **Regenerate** — accept theirs, then run `composer install` / `npm install` |
+| Migration conflicts (same timestamp) | **Rename** — adjust timestamp to avoid collision |
+| Auto-generated files (OpenAPI spec, baselines) | **Regenerate** — resolve source, then regenerate the output |
+| Formatting-only conflicts | **Accept either** — then run quality tools to normalize |
+
+### 4. File-type specific rules (stack-aware)
+
+#### Source files (any language)
+
+- After resolving, check that import statements are correct (no duplicates, no missing imports). Applies to PHP `use`, JS/TS `import`, Python `import`, Go `import`, Rust `use`.
+- Verify the resolved file parses with the project's type-checker / linter on just the touched file:
+  - PHP: `php -l filename.php` then `vendor/bin/phpstan analyse path/to/file.php`
+  - TypeScript: `tsc --noEmit` (full project) or `eslint path/to/file.ts`
+  - Python: `python -m py_compile path/to/file.py` then `mypy path/to/file.py`
+  - Go: `go vet ./path/to/pkg/...`
+  - Rust: `cargo check`
+
+#### Database migrations
+
+- Never merge two migrations that modify the same table into one.
+- If both branches added migrations, keep both — adjust timestamps / ordering to avoid collision.
+- After resolving, run migrations against a disposable database to verify:
+  - Laravel: `php artisan migrate --env=testing`
+  - Symfony / Doctrine: `php bin/console doctrine:migrations:migrate --env=test --no-interaction`
+  - Node / Prisma: `pnpm prisma migrate dev --schema=...`
+  - Node / Knex: `pnpm knex migrate:latest --env test`
+  - Python / Alembic: `alembic upgrade head` (against a test DB URL)
+  - Go / golang-migrate: `migrate -path ./migrations -database "$TEST_DATABASE_URL" up`
+
+#### Config files
+
+- `composer.json` — resolve, then run `composer update --lock` to regenerate `composer.lock`.
+- `package.json` — resolve, then run `npm install` to regenerate `package-lock.json`.
+- `.env.example` — keep all new entries from both sides.
+
+#### Test files
+
+- If both sides added tests to the same file, keep all tests.
+- If both sides modified the same test, understand what each test is verifying and combine.
+
+### 5. When to ask the user
+
+**Always ask** when:
+- Both sides changed the **same business logic** differently (semantic conflict)
+- A deletion conflicts with a modification (intent is unclear)
+- The conflict involves **authorization or security** logic
+- You're unsure which side is "correct"
+
+**Resolve without asking** when:
+- Both sides added different, non-overlapping code
+- Lock file / auto-generated file conflicts
+- Import statement ordering
+- Formatting-only differences
+
+### 6. Verify after resolution
+
+After resolving ALL conflicts:
+
+```bash
+# 1. Check no conflict markers remain (stack-agnostic — no --include filter)
+grep -rn "<<<<<<< \|======= \|>>>>>>> " . \
+  --exclude-dir=node_modules --exclude-dir=vendor --exclude-dir=.git
+```
+
+```bash
+# 2. Syntax-check changed files (stack-dependent — pick the row that matches the project)
+# PHP:    find . -name "*.php" -newer .git/MERGE_HEAD -exec php -l {} \;
+# TS:     tsc --noEmit
+# Python: python -m compileall -q .
+# Go:     go build ./...
+# Rust:   cargo check
+```
+
+```bash
+# 3. Run the project's quality tools — resolve via the quality-tools skill, Taskfile,
+#    package.json scripts, composer.json scripts, or Makefile. Examples per stack:
+# PHP:    vendor/bin/phpstan analyse
+# TS:     pnpm lint
+# Python: ruff check && mypy
+# Go:     golangci-lint run
+# Rust:   cargo clippy
+```
+
+```bash
+# 4. Run tests — full suite, not just the touched files
+# PHP:    php artisan test    (or vendor/bin/pest)
+# TS:     pnpm test
+# Python: pytest
+# Go:     go test ./...
+# Rust:   cargo test
+```
+
+```bash
+# 5. Complete the merge/rebase
+git add .
+# Don't commit — let the user decide when to commit
+```
+
+## Common pitfalls
+
+| Pitfall | Prevention |
+|---|---|
+| Accepting "ours" blindly | Always read both sides first |
+| Missing a conflict marker | Run `grep -rn "<<<<<<< "` after resolving |
+| Breaking imports | Check `use` statements after merge |
+| Losing new code | Compare the resolved file with both original versions |
+| Forgetting to regenerate lock files | Always run package manager after resolving `*.json` |
+
+## Rebase vs Merge
+
+| Approach | When to use |
+|---|---|
+| `git merge main` | Default — preserves history, safer for shared branches |
+| `git rebase main` | Only when explicitly asked — rewrites history, cleaner log |
+
+**Never rebase without explicit permission** (per `no-commit` rule).
+
+## Output format
+
+1. Resolved conflict with both sides' intent preserved
+2. Summary of resolution strategy per file
+
+## Auto-trigger keywords
+
+- merge conflict
+- resolve conflict
+- rebase conflict
+- conflict markers
+- branch behind main
+- update branch
+
+## Gotcha
+
+- Never resolve conflicts by deleting code you don't understand — ask the user.
+- The model tends to accept "ours" or "theirs" wholesale instead of merging logic from both sides.
+- Always run tests after resolving conflicts — successful merge != correct merge.
+- Lock file conflicts (composer.lock, package-lock.json) should be resolved by re-running the package manager.
+
+## Do NOT
+
+- Do NOT rebase or force-push without explicit permission.
+- Do NOT leave conflict markers (`<<<<<<<`) in any file.
+- Do NOT skip verification (project type-checker + tests) after resolving.

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

@@ -0,0 +1,197 @@
+---
+model_tier: inherit
+name: motion-choreographer
+description: "Use when turning a locked still + blueprint into a provider-tuned motion prompt — camera, primary + secondary motion, physics, native-audio sync. Triggers 'motion prompt for Veo/Kling/Sora'."
+personas:
+  - ai-video-technical-director
+domain: product
+workspaces:
+  - small-business
+packs:
+  - ai-video
+lifecycle: experimental
+trust:
+  level: experimental
+install:
+  default: false
+  removable: true
+---
+
+# motion-choreographer
+
+> Turn an approved still + the 12-block scene blueprint into a
+> provider-tuned **motion prompt** that the target video adapter
+> consumes. Camera choreography, primary subject motion, secondary
+> 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);
+> never speaks to a network API.
+
+## When to use
+
+- An image is locked (operator picked one candidate via
+  `operator-pick.sh`) and the next step is motion + audio direction
+  for the video adapter.
+- The blueprint exists in `scenes/<id>/blueprint.json` but the
+  motion prompt has not been emitted yet.
+- A provider switch (Veo → Kling, Sora → Higgsfield) requires the
+  same scene retuned for the new adapter's capability profile.
+
+Do NOT use when:
+
+- The blueprint is still prose only — run
+  [`scene-expander`](../scene-expander/SKILL.md) → `parse-blueprint.sh`
+  first.
+- No still has been locked — the operator-selection checkpoint
+  must complete first.
+- The output is a still graphic — `canvas-design`.
+
+## Procedure
+
+### Step 0: Inspect
+
+1. Read `scenes/<id>/blueprint.json` — fail loud if missing.
+2. Read `scenes/<id>/selection.json` — fail loud if missing; the
+   locked image path is required as the motion anchor.
+3. Read the target adapter's capability via
+   `scripts/ai-video/adapters/<id>.sh capability`. Cache `audio=*`
+   for Step 3.
+4. If a `character.json` lock exists, load it verbatim — identity
+   tokens are immutable.
+
+### Step 1: Camera choreography
+
+Emit a `CAMERA MOTION` block with the move type, distance, speed
+in seconds, and start-end framing.
+
+- Move types: lock-off, pan, tilt, dolly-in, dolly-out, truck,
+  pedestal, push, pull, handheld, gimbal-glide, crane, whip.
+- Speed in seconds per beat (`0.4s push, hold 1.6s, 0.4s pull`).
+- Start and end framing named (`MS → CU`, `WS → MS`).
+
+Blueprint intent-class decoding — the blueprint CAMERA block names
+one of six provider-agnostic intent classes; map it to the move types
+above before encoding:
+
+| Intent class | Move-type mapping |
+|---|---|
+| static hold | lock-off |
+| push-in | push / dolly-in |
+| pull-back | pull / dolly-out |
+| lateral track | truck / pan |
+| handheld drift | handheld / gimbal-glide |
+| orbit | crane / arc via truck+pan |
+
+Adapter quirks (per-provider encoding of the mapped move):
+
+- **Veo** — accepts named moves; prefers ≤ 8s clips.
+- **Kling** — motion intensity 0–1 token; map our speed to that.
+- **Sora** — natural-language move + duration; no token.
+- **Higgsfield** — preset-driven; pick the preset that matches the
+  move; record the preset id in the motion prompt.
+- **LENS handling** — blueprint mm + aperture translate to the
+  provider's nearest lens / FOV idiom; never forward raw mm to a
+  provider that lacks lens grammar.
+- **DURATION handling** — the blueprint value is free; clamp to the
+  provider ceiling here and record the clamp in `review.md` (a
+  silent clamp is a drift bug).
+
+### Step 2: Primary + secondary motion
+
+Two blocks:
+
+1. **PRIMARY MOTION** — what the subject does, beat-counted, with
+   physics anchors (mass, contact points, momentum). Reuse `ACTION`
+   from the blueprint; refine for the adapter's preferred verb
+   density.
+2. **SECONDARY MOTION** — what the world does (hair, fabric,
+   foliage, water, dust, particles, breath). One layer per line.
+
+### Step 3: Audio direction (conditional)
+
+If adapter capability is `audio: native` AND the blueprint's
+`audio.enable_native_audio` is `true`:
+
+Emit an `AUDIO DIRECTION` block with:
+
+- `DIALOGUE TIMING` — `speaker @ 0.4s: "line"` per dialogue entry.
+- `AMBIENT LAYERS` — copy from blueprint; one layer per line.
+- `SYNC CUES` — which action beat maps to which audio cue
+  (`footstep @ 1.2s`, `door close @ 2.1s`).
+
+If adapter capability is `audio: none`:
+
+- Emit a `# AUDIO: ffmpeg-mux fallback` comment with the
+  blueprint's audio paths queued for stitch-time mux.
+- Set `enable_native_audio: false` in the motion-prompt JSON.
+- Blueprint carries DIALOGUE → the mux fallback cannot speak text
+  lines. Emit a mandatory `AUDIO DOWNGRADE` warning block in
+  `motion-prompt.txt` AND `adapter-notes.md` listing every dialogue
+  line that will not render. The decision whether that is acceptable
+  belongs to the orchestrator gate (adapter-contract § Audio
+  ownership) — this skill translates, it never validates, and it
+  NEVER silently strips dialogue.
+
+### Step 4: Physics constraints
+
+Emit `PHYSICS` — a short list of what the model must respect:
+gravity direction, contact friction, fluid behavior, hair / cloth
+inertia, lens parallax. Single line per constraint.
+
+### Step 5: Emit motion-prompt JSON
+
+Write `scenes/<id>/motion-prompt.json` with the adapter-contract
+stdin shape. The orchestrator pipes this into the video adapter's
+`submit` subcommand.
+
+### Step 6: Validate
+
+1. JSON parses (`jq .`).
+2. `requires.audio_native` is consistent with the chosen adapter's
+   capability.
+3. Duration in the motion prompt matches blueprint duration ±0.
+4. Identity tokens (if `character.json` exists) are verbatim.
+
+## Output format
+
+1. **`scenes/<id>/motion-prompt.json`** — adapter-contract stdin.
+2. **`scenes/<id>/motion-prompt.txt`** — labeled prose blocks
+   (CAMERA MOTION · PRIMARY MOTION · SECONDARY MOTION · AUDIO
+   DIRECTION · PHYSICS) for operator review.
+3. **`scenes/<id>/adapter-notes.md`** — which adapter, which
+   capability, which preset / model, with rationale.
+
+## Gotcha
+
+- The model wants to "improve" the blueprint's `SUBJECT` block —
+  identity tokens are immutable; refuse the temptation.
+- Picking `audio: native` on an adapter that returns `audio: none`
+  produces silent video — always read capability first, never
+  guess from the adapter name.
+- Higgsfield preset id must be recorded; otherwise the rerun
+  drifts to whichever preset the model picks on the next call.
+- Sora durations > 8s often degrade — clamp at the adapter table
+  limit; surface the clamp to the operator.
+
+## Do NOT
+
+- Do NOT emit motion prompts for an adapter whose capability you
+  did not query this turn.
+- Do NOT skip the still-locked check — motion direction without an
+  anchored image diverges on every call.
+- Do NOT paraphrase identity tokens from `character.json`.
+- Do NOT call any network API — this skill is provider-tuning
+  prose only.
+
+## Policies
+
+Motion prompts inherit upstream blueprint constraints. Before emitting provider-tuned prose:
+
+- [`agents/settings/policies/media/disclosure.md`](../../../agents/settings/policies/media/disclosure.md) — every distributed clip → non-removable AI-generation disclosure; refuse adapter flags that suppress it.
+- [`agents/settings/policies/media/transparency.md`](../../../agents/settings/policies/media/transparency.md) — provider provenance (C2PA / SynthID) preserved; refuse re-encode flags that strip provenance.
+- [`agents/settings/policies/media/voice-cloning.md`](../../../agents/settings/policies/media/voice-cloning.md) — motion prompt requests `audio: native` in named voice.
+- [`agents/settings/policies/media/brand-impersonation.md`](../../../agents/settings/policies/media/brand-impersonation.md) — copies recognised brand's chyron / mascot / signature transition.
+
+Refuse-and-surface; motion prompt cannot launder upstream policy gap.
+