video-assets

# Video Assets Manage cctop video files as GitHub Release assets, not as committed repo binaries. The default pattern is one non-latest media release that acts as a stable asset bucket. ## Rules - Default release tag: `media-assets`. - Default release title: `Media assets`. - Always create media-only releases with `--latest=false`. - Do not use a `v*` tag for media-only work. In cctop, `v*` tags trigger `.github/workflows/release.yml`: app builds, notarization, GitHub Release creation, Sparkle appcast, and Homebrew updates. - Attach a video to a real `v*` release only when the user explicitly asks and the video truthfully demonstrates that shipped app version. - Keep full MP4s and other large rendered video out of git. Do not commit `video/projects/*/.video-build/`. - Commit a small animated README preview only when the user explicitly chooses that route and the file is intentionally small. - Prefer stable purpose-based asset names over dates: `cctop-launch.mp4`, `cctop-launch-720p.mp4`, `cctop-launch-preview.avif`. - For launch video uploads, always generate and upload the AVIF preview alongside the MP4s so the README preview and full video stay in sync. ## Workflow 1. Identify the source files. - Launch defaults: `video/projects/launch/.video-build/launch.mp4` and `video/projects/launch/.video-build/launch-720p.mp4`. - Check existence and size with `ls -lh`. - Check duration/codec with `ffprobe` when available. 2. Pick the release target. - Use `media-asse...