@vosjs/cli 0.67.6 → 0.69.0

package/skills/product-video/references/destinations.md

@@ -1,16 +1,13 @@
 # Destination packaging
 
-What to produce, at what size, for each place a product video or still
-lands. All assets come from ONE take — pick apex moments with
-`vos frames take --at-zooms`, then cut stills with
-`vos frames take --frame <t> --size WxH` and videos with render presets +
-`--range`.
+What to produce, at what size, for each place a product video lands.
+Every cut comes from ONE take: render presets plus `--range`.
 
-**Producing a full launch kit?** Use the `launch-kit` skill from this
-repo — it drives the whole per-channel loop against the machine-readable
-spec sheet (`schema/channel-specs.json` in `@vosjs/cli`) and verifies
-every asset in a manifest. The tables below are the quick reference for
-one-off cuts.
+**Producing a release's full set of cuts?** Use the `launch-kit` skill
+from this repo: it drives the whole per-channel loop against the
+machine-readable spec sheet (`schema/channel-specs.json` in `@vosjs/cli`)
+and verifies every cut in a manifest. The tables below are the quick
+reference for one-off cuts.
 
 ## Landing-page embed (your site's hero or feature section)
 
@@ -38,27 +35,19 @@ one-off cuts.
   ffmpeg -i in.webm -c:v libx264 -b:v <target>k -pass 1 -an -f mp4 /dev/null
   ffmpeg -i in.webm -c:v libx264 -b:v <target>k -pass 2 -movflags +faststart out.mp4
   ```
-- Repo social-preview image: 1280×640.
 
 ## Store and directory listings
 
-| Channel | Asset | Size | Notes |
-|---|---|---|---|
-| Chrome Web Store | screenshots (≤5) | 1280×800 | content only, no device chrome |
-| Chrome Web Store | small promo tile | 440×280 | subject centered |
-| Chrome Web Store | marquee promo | 1400×560 | |
-| Chrome Web Store | icon | 128×128 | |
-| Product Hunt | thumbnail | 240×240 | GIF loops autoplay in the feed |
-| Product Hunt | gallery images | 1270×760 | first image is the header |
+The Chrome Web Store promo video and the Product Hunt video both take a
+YouTube URL only: upload the main demo (16:9, 1920×1080, 60 to 120 s) to
+YouTube and paste its link.
 
 ## Social cuts
 
 | Channel | Asset | Size | Notes |
 |---|---|---|---|
-| YouTube | thumbnail | 1280×720 | |
-| X | feed video | 1200×675 (16:9) | ≤140s, H.264 — upload natively, never a link card |
-| LinkedIn | feed video/image | 1200×627 | native upload; mute-legible |
-| OG card (any link) | image | 1200×630 | |
+| X | feed video | 1920×1080 (16:9) or 1:1 | ≤140s, H.264 — upload natively, never a link card |
+| LinkedIn | feed video | 1080×1920, the vertical cut | native upload; mute-legible |
 | Vertical (Shorts/Reels/TikTok) | video | 1080×1920 (9:16) | keep the subject inside the ~900×1160 center safe zone — platform chrome covers the rest |
 
 ## Performance rules (every channel)

package/skills/vos-footage/SKILL.md

@@ -12,7 +12,7 @@ backdrop, no titles (the composition owns those) — but it is never an
 orphan file: the take it came from lives on the maker's shelf, editable,
 and the handoff says so. That one line is the whole contract.
 
-If the ask is actually a RELEASE (a launch video, a store listing, the
+If the ask is actually a RELEASE (a launch video, the social cuts, the
 whole kit), stop — that is the `launch-kit` skill, and the document that
 survives should be the vosso one.
 

package/skills/vos-migrate/SKILL.md

@@ -99,6 +99,6 @@ next one with `vos record` and the camera plans itself.**
 - Old edits, camera bubbles and captions are baked pixels.
 - The migration re-encodes once (VP9); a badly compressed source stays
   badly compressed — migrating does not restore quality.
-- A spec-size deliverable ladder (store stills, posters) works from the
-  migrated take exactly as from a native one — the `launch-kit` skill
-  takes over when the ask is a release.
+- A release's set of cuts (the demo, the social cuts, the README loop)
+  works from the migrated take exactly as from a native one: the
+  `launch-kit` skill takes over when the ask is a release.