@vosjs/cli 0.56.0 → 0.57.0

package/dist/cli.js

@@ -730,7 +730,7 @@ async function cmdCheck(argv) {
   return result.ok ? EXIT_OK : EXIT_ERROR;
 }
 async function delegate(argv, viaAlias = false) {
-  const { run } = await import("./run-OIZ7NQPU.js");
+  const { run } = await import("./run-JE4G42EJ.js");
   if (viaAlias && argv[0]) {
     process.stderr.write(
       `note: "vos voila ${argv[0]}" is now "vos ${argv[0]}".
@@ -770,7 +770,7 @@ async function main() {
     const engine = HELP_ENGINE.split("\n").filter(
       (l) => l.startsWith(`  vos ${cmd} `)
     );
-    const { verbHelp } = await import("./run-OIZ7NQPU.js");
+    const { verbHelp } = await import("./run-JE4G42EJ.js");
     const take = verbHelp(cmd);
     process.stdout.write(
       `${engine.join("\n")}
@@ -802,7 +802,7 @@ ${take.includes("no such verb") ? "" : take}`
 main().then(async (code) => {
   if (code === EXIT_OK) {
     const verb = process.argv[2] ?? "";
-    const { HELP } = await import("./run-OIZ7NQPU.js");
+    const { HELP } = await import("./run-JE4G42EJ.js");
     const documented = [
       ...helpFlagsFor(HELP_ENGINE, verb),
       ...helpFlagsFor(HELP, verb)

package/dist/index.js

@@ -18,7 +18,7 @@ import {
   takePaths,
   validateActions,
   waitForPageDone
-} from "./chunk-XXAY42XS.js";
+} from "./chunk-Z74Y4WNW.js";
 import {
   BrowserUnavailableError,
   apiError,

package/dist/{run-OIZ7NQPU.js → run-JE4G42EJ.js}

@@ -6,7 +6,7 @@ import {
   takeBackdrop,
   takeBrowserArgs,
   verbHelp
-} from "./chunk-XXAY42XS.js";
+} from "./chunk-Z74Y4WNW.js";
 import "./chunk-JX2YEL3M.js";
 import "./chunk-6XPFWQKP.js";
 export {
@@ -17,4 +17,4 @@ export {
   takeBrowserArgs,
   verbHelp
 };
-//# sourceMappingURL=run-OIZ7NQPU.js.map
+//# sourceMappingURL=run-JE4G42EJ.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vosjs/cli",
-  "version": "0.56.0",
+  "version": "0.57.0",
   "description": "The vos CLI: record the real product from a scripted browser flow, auto-zoom from the cursor track, cut as data in doc.json, render deterministic video and stills, deliver a release's media per destination spec, and sync with vos.so. One binary, every verb, MIT.",
   "type": "module",
   "license": "MIT",
@@ -51,14 +51,14 @@
     "acorn-walk": "^8.3.5",
     "mediabunny": "^1.55.7",
     "playwright": "^1.49.0",
-    "@vosjs/core": "^0.25.5",
+    "@vosjs/core": "^0.25.6",
     "@vosjs/editor": "^1.4.0",
-    "@vosjs/shared": "^0.6.0",
-    "@vosjs/elements": "^0.10.0",
+    "@vosjs/elements": "^0.10.1",
     "@vosjs/render-core": "^0.3.11",
-    "@vosjs/studio-core": "^0.33.2",
-    "@vosjs/timeline": "^0.4.1",
-    "@vosjs/tween": "^0.8.2"
+    "@vosjs/shared": "^0.6.0",
+    "@vosjs/studio-core": "^0.33.3",
+    "@vosjs/timeline": "^0.5.0",
+    "@vosjs/tween": "^0.8.3"
   },
   "devDependencies": {
     "@types/node": "^22",

package/skills/VERSION

@@ -1 +1 @@
-0.16.0
+0.18.0

package/skills/vos-authoring/SKILL.md

@@ -20,6 +20,8 @@ the render: a config produces the same frames on every machine.
 3. **Generate the config**: write a complete, valid VosConfigJson to
    `<kebab-case-name>.json` wherever the project keeps configs.
 4. **Validate locally** (see below), then render or preview it.
+5. **Push it and give the link** (see below): the work is done when the
+   user has a link that plays it, not when a file sits on disk.
 
 If the user provides an image, analyze its visual style (colors, mood,
 composition, lighting) and translate those qualities into the scene.
@@ -44,12 +46,25 @@ vos preview my-config.json             # local playback page
 vos info   my-config.json
 ```
 
-## Share for preview (no account needed)
+## Push it and give the link
 
-Local render is the default — nothing leaves the machine unless the user
-asks for sharing or hosting. When they do want to see it hosted (playable
-link, fine-tuning in the vos.so studio) and no API key is configured, use
-the claimable push:
+A vos program is made to be watched, tuned in the studio and remixed, so
+finish by pushing it and handing back the link. Skip the push only when the
+user said to keep the work local.
+
+Find a credential in this order, without printing it: `VOS_API_KEY`, then
+the first line of `~/.config/vos/credentials`. With one, push:
+
+```bash
+vos push my-config.json --title "…" --desc "one line" --wait
+# --wait stays until the cover has rendered, then prints the links
+```
+
+The vos lands PRIVATE on the key owner's shelf: only they can open the
+links, and publishing stays their act on vos.so. Keyed pushes never expire;
+iterate with `vos push my-config.json --vos <id>`.
+
+No credential at all? Use the claimable push instead of stopping:
 
 ```bash
 vos push my-config.json --claimable --title "…"
@@ -62,12 +77,16 @@ curl -s -X POST https://vos.so/api/claim \
 # → { "claimUrl": "https://vos.so/claim/…", "expiresAt": "…" }
 ```
 
-Hand `claimUrl` to the user and nowhere else — it is the only reference and
-the only credential. It lasts 72 hours; unclaimed work is deleted after
+Hand `claimUrl` to the user and nowhere else: it is the only reference and
+the only credential. It lasts 72 hours, and unclaimed work is deleted after
 that (re-push if it lapses). Claiming moves the vos into the user's
-library. With a key configured (`VOS_API_KEY` or `vos login`), prefer
-`vos push` — keyed pushes have no expiry. Programs only, config ≤200KB,
-5 pushes per day per network.
+library. Programs only, config ≤200KB, 5 pushes per day per network.
+
+End your reply with the links, never only a file path: the watch page
+(`https://vos.so/vos/<id>`, it plays the program) and the studio
+(`https://vos.so/studio?vos=<id>`, where the user tunes your knobs), or
+the claim link when there was no credential. A local MP4 is a bonus, not
+the deliverable.
 
 ## VosConfigJson structure
 
@@ -162,7 +181,8 @@ Values must reference declared param keys with matching types.
 Configs pushed to vos.so get preview-rendered on a software-GL fleet: no
 `THREE.DoubleSide` on transmission materials (hard hang), no `dispersion`
 (too slow), and any fetched asset must be reachable and CORS-open. These are
-fine for purely local renders on a real GPU.
+fine for purely local renders on a real GPU. They are things to avoid, never
+a reason to skip the push: keep transmission single-sided, and push.
 
 ## Your own passes: depth of field, refraction
 

package/skills/vos-create/SKILL.md

@@ -180,6 +180,8 @@ publish; promoting is the human's gesture on vos.so.
 **Look at what landed.** Every push renders a still within about 15
 seconds: `GET /api/vos/{id}`, follow `contentUrls.thumbnail`, and view the
 image before reporting done. A push you never looked at is not finished.
+Then end your reply with the links: the watch page
+(`https://vos.so/vos/<id>`) and the studio (`https://vos.so/studio?vos=<id>`).
 
 **Pace a batch**: back-to-back pushes are fine at the quota (the render
 queue spaces browser launches and backs off itself). Verify state after a

package/skills/vos-port/SKILL.md

@@ -171,7 +171,7 @@ approximation.
    TODO per scene, each scene's words shown in its window, a painter only
    when the inventory needs one, and the PAINTER STARTER as
    `content.refs.lib` when the piece needs a painter or springs: Remotion's
-   `spring` to the frame, `springTo` for the timeline, `interpolate`,
+   `spring` to the frame, `springSeconds` for a tween eased `spring(...)`, `interpolate`,
    `bezier`, seeded noise; never read another engine's source for these),
    `doc.json` with the score as a track, and
    `port/REPORT.md` (substituted faces, gaps). Read the report first. On an
@@ -206,7 +206,7 @@ stated approximation:
 | a colour per split unit (`charStyle` making one letter red) | segments carry x/y/opacity/scale/rotation only: a separate element, or paint it |
 | `mixBlendMode` | no blend modes on elements: paint it |
 | a shape's colour as a knob | an svg's colours are compiled in (static `colors`): paint the shape if its colour must change live |
-| `spring()` | no spring EASE in the dialect; the scaffold's painter starter (cli 0.56+) has `lib.springTo`, Remotion's spring on the timeline a step per frame, exact. Older: `back.out(n)`, by eye |
+| `spring()` | the `spring(damping, stiffness, mass)` ease (cli 0.57+), duration `lib.springSeconds(config)`: Remotion's spring on the timeline, exact. Older: `lib.springTo` (0.56), else `back.out(n)` by eye |
 | `@remotion/noise`, SVG `feTurbulence` | the painter, on the starter's `lib.noise2D/noise3D` (the same character, not the same values) |
 | a group transform (scale the whole scene) | no element groups: tween each element the same way |
 

package/skills/vos-port/references/elements-and-context.md

@@ -1,4 +1,4 @@
-<!-- Generated by scripts/build-element-reference.mjs from @vosjs/core 0.25.5, @vosjs/elements 0.9.0, @vosjs/timeline 0.4.1 and @vosjs/shared 0.6.0. Do not edit by hand: re-run the script. -->
+<!-- Generated by scripts/build-element-reference.mjs from @vosjs/core 0.25.5, @vosjs/elements 0.10.0, @vosjs/timeline 0.4.1 and @vosjs/shared 0.6.0. Do not edit by hand: re-run the script. -->
 
 # Elements, the context and eases: the declarations
 
@@ -722,7 +722,13 @@ An `ease` string anywhere GSAP takes one. Beyond the names below the
 engine accepts the parameterized forms `back.out(1.7)`,
 `elastic.out(1, 0.3)`, `steps(5)`, and `css-bezier(x1, y1, x2, y2)`,
 which is CSS's `cubic-bezier` and Remotion's `Easing.bezier` with the same
-four numbers (`cubic-bezier` itself is not a name). A bare family
+four numbers (`cubic-bezier` itself is not a name), and (`@vosjs/timeline`
+0.5+) `spring(damping, stiffness, mass)`, defaults 10, 100, 1 (`spring`,
+`spring.in`, `spring.inOut` too): a damped spring stretched over the tween,
+landing exactly on its target. A tween as long as the spring's settle time
+moves as Remotion's `spring()` does, frame for frame; a ported program reads
+that duration from `content.refs.lib.springSeconds({ damping, stiffness })`,
+and a longer one stretches it as `durationInFrames` does. A bare family
 (`'power2'`) means `.out`. **An unknown name is not an error: it plays
 linear.** `vos check` warns `unknown-ease` for a literal `ease: '…'` it
 cannot resolve; through `@vosjs/core` 0.25.0 that warning also fired on

package/skills/vos-port/references/remotion.md

@@ -16,7 +16,7 @@ rows name what has no element equivalent yet.
 | `useCurrentFrame()` | nothing in a tween (the timeline is the clock); `ctx.time * fps` inside `onFrame` |
 | `interpolate(f, [a, b], [x, y], { easing, extrapolate: 'clamp' })` | `tl.fromTo(props, { p: x }, { p: y, duration: (b - a) / fps, ease }, a / fps)` |
 | `Easing.bezier(x1, y1, x2, y2)` | `ease: 'css-bezier(x1, y1, x2, y2)'` (exact) |
-| `spring({ frame, fps, config })` | the painter starter (cli 0.56+): `content.refs.lib.springTo(tl, props, { y: [from, to] }, at, { fps, config })` puts Remotion's own spring on the timeline, a step per frame, exact to the frame; `lib.spring({ frame, fps, config })` is the value (`durationInFrames`, `delay`, `overshootClamping` as Remotion's). On an older CLI: `back.out(n)` of a similar overshoot, by eye |
+| `spring({ frame, fps, config })` | the `spring(damping, stiffness, mass)` ease ON THE TIMELINE (cli 0.57+): `tl.to(p, { y: 0, ease: 'spring(200)', duration: content.refs.lib.springSeconds({ damping: 200 }) }, at)` moves exactly as Remotion's spring; a longer duration stretches it as `durationInFrames` does. Never compute a spring in `onFrame`. `lib.spring({ frame, fps, config })` is the value, for a painter. On cli 0.56, `lib.springTo`; older, `back.out(n)` by eye |
 | `<Sequence from durationInFrames>` | `tl.addLabel(name, from / fps)` and the scene's elements tweened in and out inside that window |
 | `<TransitionSeries>` + `fade()` | opacity tweens across the overlap window |
 | `<AbsoluteFill>` + flex centring | `position: 'center'`; offsets in `transform: { translateX, translateY }` (design px) |