Update to Cav

{
  "description": "Build professional motion graphics in Cavalry (the 2D motion design app) from the shell with the `cav` CLI - logo stings, kinetic type, lower thirds, charts, UI walkthroughs, transitions, and animations synced to music beats. Use when the user asks to create, animate, edit, inspect or render anything in Cavalry, or mentions .cv scenes.",
  "included_files": [
    {
      "relative_path": "references/install.md",
      "size_in_bytes": 2755
    },
    {
      "relative_path": "scripts/install.ps1",
      "size_in_bytes": 2446
    },
    {
      "relative_path": "scripts/install.sh",
      "size_in_bytes": 3801
    }
  ],
  "name": "cavalry",
  "skill_md_contents": "---\nname: cavalry\ndescription: Build professional motion graphics in Cavalry (the 2D motion design app) from the shell with the `cav` CLI - logo stings, kinetic type, lower thirds, charts, UI walkthroughs, transitions, and animations synced to music beats. Use when the user asks to create, animate, edit, inspect or render anything in Cavalry, or mentions .cv scenes.\nlicense: MIT\ncompatibility: Needs Cavalry 2.4+ (tested on 2.7.2 and 2.8.0) on macOS or Windows, the `cav` CLI, and ffmpeg. Cavalry must be running with the cav-bridge script open.\nmetadata:\n  version: \"1.1.2\"\n---\n\n# Cav: motion graphics in Cavalry\n\nThe `cav` CLI does the work and carries its own guides. This skill only gets you started.\n\n1. Run `cav doctor`.\n   - `cav: command not found`: ask the user, then install it as `references/install.md` says.\n   - `FAIL bridge`: ask the user to open Cavalry and click **Scripts > cav-bridge**, and to\n     keep its window open. Wait, then run `cav doctor` again. Do not reach Cavalry any other\n     way.\n   - `blocked: a sandbox`: your sandbox stops `cav`. Show the user the fix that `cav doctor`\n     prints (allow `cav` to reach 127.0.0.1:8723, or run `cav relay` outside the sandbox).\n2. Run `cav guide` and follow it. It covers the workflow, script rules and a done checklist.\n   Read `cav guide design` before a creative task and `cav guide music` when there is music.\n   `cav helpers` lists the script library; `cav help <command>` explains each command.\n3. Work only in new scenes (`cav scene new`). Never use `--force` on the user's own work.\n4. You cannot see Cavalry: look at `cav sheet` images after every change, and run\n   `cav check` before you render.\n\n5. Start diagnostics with `cav check --quick --json`. Treat performance findings as\n   structural risks; add `--profile` for small measured samples. Inspect failed/skipped\n   coverage before calling the scene clean. A native call can exceed the CLI wait budget.\n6. After `run`, `check` or `render` times out, inspect the printed operation ID with\n   `cav operation status <id>` and continue with `cav operation resume <id> --timeout 30m`.\n   Do not retry the original command. Raw `cav job wait` completes only one bridge job,\n   including a render's preparatory metadata. Keep the original scene/session and inputs\n   unchanged during recovery; unknown outcomes require manual inspection.\n\n7. Use `cav render` for final video output; do not wait only for an MP4 to grow. On exit 4\n   (bridge disconnect or session change), stop automatic waiting, inspect the operation,\n   and preserve partial artifacts. File size/age is not completion or proof of a crash.\n   Reconcile an unknown outcome before abandoning and starting a new render; never\n   silently relaunch the app, retry or switch to chunk rendering.\n"
}