@vosjs/cli 0.69.0 → 0.70.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/dist/{chunk-5DUXN3RX.js → chunk-KIFXVPBR.js} +417 -261
- package/dist/chunk-KIFXVPBR.js.map +1 -0
- package/dist/{chunk-5GZ3GPAK.js → chunk-YZAM4W7B.js} +12 -7
- package/dist/{chunk-5GZ3GPAK.js.map → chunk-YZAM4W7B.js.map} +1 -1
- package/dist/cli.js +4 -4
- package/dist/index.d.ts +1 -1
- package/dist/index.js +2 -2
- package/dist/{run-NDBUFOIG.js → run-7QR3CQSF.js} +3 -3
- package/package.json +5 -5
- package/schema/actions.schema.json +7 -7
- package/dist/chunk-5DUXN3RX.js.map +0 -1
- /package/dist/{run-NDBUFOIG.js.map → run-7QR3CQSF.js.map} +0 -0
package/README.md
CHANGED
|
@@ -90,6 +90,8 @@ vos record --actions actions.json --out take --strict # footage replaced; the
|
|
|
90
90
|
vos plan take --reuse # re-time that cut onto the new recording; what could not follow is named
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
+
Every manual span follows the step it was made on (the gesture whose window held it, or the one just before it), keeping its offset exactly; a span whose step is missing or skipped in the new recording is dropped and named with what it framed, never re-timed to a place with nothing under it. A layer pinned to a step (`pin: { step }`) plays when that step plays in the new cut; a layer that is not pinned keeps its output second, and when the step under it moved the report names it with the step's new time and the pin to write. A take fetched from vos.so can be recorded again: the script rides the document and `vos fetch --media` writes it back as `actions.json`.
|
|
94
|
+
|
|
93
95
|
**Already have a video?** A Cursor cloud agent's PR video, a Playwright run's `video.webm`, a Loom export: `vos ingest` makes it a take. The file becomes `recording.<container>` (stream-copied into a seekable container, or copied as it is), `meta.json` comes from the file's own dimensions and duration, and a trace recorded beside it becomes `cursor.json`, so the planner has clicks to zoom on.
|
|
94
96
|
|
|
95
97
|
```bash
|
|
@@ -208,7 +210,7 @@ take/
|
|
|
208
210
|
frames/ raw screencast JPEGs, indexed by frames.json (kept for re-encode)
|
|
209
211
|
cursor.json the synthesized CursorTrack: exact coordinates, element rects
|
|
210
212
|
meta.json RecordingMeta (producer: "cli", per-step source extents)
|
|
211
|
-
actions.json the script that produced it, with the resolved url
|
|
213
|
+
actions.json the script that produced it, with the resolved url; pushed inside the document and written back by a fetch or pull with --media
|
|
212
214
|
doc.json ProjectDoc, the editable cut
|
|
213
215
|
doc.prev.json the previous cut, kept by a re-record for `vos plan --reuse`
|
|
214
216
|
vos.json hosted tracking (vos id + base version), written by push, fetch and pull
|