@koda-sl/baker-cli 0.201.0-dev.0a9adf6f7 → 0.201.0-dev.6e39c93b9

package/README.md

@@ -86,8 +86,19 @@ All commands return a JSON envelope:
 
 // Dry-run
 { "ok": true, "dryRun": true, "operation": "images.delete", "params": { "id": "abc123" } }
+
+// Unknown option — the command stops instead of running without it
+{ "ok": false, "error": { "code": "UNKNOWN_ARGUMENT", "message": "--dimension-filter is not an option of `baker ga4 query`.", "fix": { "action": "check_schema", "explanation": "Did you mean --dimensions? Run `baker schema ga4 query` ..." }, "retryable": false } }
 ```
 
+### Unknown options are refused
+
+An option a command does not declare stops the run with `UNKNOWN_ARGUMENT`, naming the
+closest real one. Previously such an option was accepted and ignored, so a call that
+looked like it had filtered or narrowed a result was in fact answering the unfiltered
+question — and nothing in the output said so. Run `baker schema <command>` to see
+every option a command takes.
+
 Use `--output` to change format:
 
 | Format  | Description                        | Best for           | Available on |
@@ -2442,16 +2453,15 @@ Get a single video by ID. `--full` includes the auto-generated **transcript** (B
 baker videos get j571abc123 --full --output md
 ```
 
-### `baker videos upload <file|url>`
+### `baker videos upload <file>`
 
-Upload a video. A local path is uploaded directly; an `http(s)` URL is routed to `baker videos ingest`.
+Upload a video file via Mux direct upload.
 
 ```bash
 baker videos upload ./demo.mp4
 baker videos upload ./demo.mp4 --dry-run
 baker videos upload ./testimonial-maria.mp4 \
   --context "Testimonial from Maria, a real customer, filmed on her phone for the autumn campaign"
-baker videos upload https://www.youtube.com/watch?v=abc123
 ```
 
 Supported extensions: `.mp4`, `.mov`, `.webm`, `.avi`, `.mkv`
@@ -2469,41 +2479,6 @@ baker videos group --group-key "instagram:Cx7Ab9"
 
 Same lookup as `baker images group` and takes either kind of id; the two exist so the noun you happen to hold does not decide whether you can ask.
 
-### `baker videos ingest <url>`
-
-Add a video to the library from a link — a direct video file, or a page on YouTube, TikTok, Vimeo, or Instagram.
-
-```bash
-baker videos ingest https://cdn.example.com/hero-loop.mp4          # → { videoId, via: "direct" }
-baker videos ingest https://www.youtube.com/watch?v=abc123         # → { videoId, via: "download" }
-baker videos ingest https://vimeo.com/12345 --external-id vim:12345
-```
-
-Two routes, chosen from the URL and reported as `via`:
-
-- **direct** — the URL ends in a video extension, so Baker fetches the file itself. Nothing is downloaded locally and there is no size limit.
-- **download** — anything else. The video is downloaded locally, stored, and then ingested. Capped at 2 GB.
-
-A direct URL that Baker cannot fetch retries automatically on the download route and reports `fallbackFrom`. Force the download route with `--download`.
-
-| Flag | Purpose |
-|---|---|
-| `--source` | Provenance: `url` or `youtube`. Inferred from the URL when omitted. |
-| `--external-id` | Dedupe key — re-running the same link returns the existing video. Derived from the link automatically on the download route. |
-| `--external-url` | Canonical page URL. Defaults to the input for a page URL. |
-| `--download` | Skip the direct attempt and always download. |
-| `--dry-run` | Preview the resolved route and parameters. |
-
-The download route caps the pull at 1080p — Baker re-encodes for streaming anyway, so fetching a 4K master (what modern YouTube serves by default) only makes the download slower for pixels that get discarded.
-
-**Blocked downloads climb the egress ladder automatically.** The download route goes through the same **direct → datacenter → residential** ladder as every other outbound read (`@baker/proxy`; see [Operations](../../docs/operations.md) → Egress Proxy). There is no proxy flag on any command and nothing to opt into — the unproxied attempt always runs first, so a paid exit costs nothing until a host actually refuses us, and with no `OXYLABS_*` credentials in the environment this is a single plain download.
-
-A rung only opens on evidence that *who we are* was the problem — a 403/429/451, a WAF connection reset, or a bot wall like YouTube's "Sign in to confirm you're not a bot". A private video, a deleted one, a 404 or an unsupported URL fails identically from every address on earth, so it stops after one attempt instead of burning a timeout per tier. That decision is `shouldEscalate`'s, shared with the capture engine and the ad-media downloaders; yt-dlp's stderr is only *parsed* into the signal it takes (`src/lib/ytDlpSignal.ts`), never allowed to judge for itself.
-
-Requires `yt-dlp` on `PATH` (present in the Baker Runtime). Private, age-restricted, or region-locked videos cannot be downloaded — the error carries a `fix` pointing at `baker videos upload <file>`.
-
-**yt-dlp goes stale, and that looks like a broken video.** Large platforms change their players every few weeks and an out-of-date `yt-dlp` then resolves *no* formats at all, failing with "Requested format is not available" or "Only images are available" rather than anything that names the real cause. The error classifies this case separately and says the link is probably fine. The Runtime image installs `yt-dlp` unpinned at build time (`packages/e2b-template/src/template.ts`), so it ages with the image — if platform ingests start failing across the board, rebuild the template before investigating anything else. Direct file URLs don't depend on `yt-dlp` at all and keep working regardless.
-
 ### `baker videos delete <id>`
 
 Delete a video by ID.
@@ -4596,6 +4571,19 @@ $ baker canvas validate my-canvas.json
 
 On error you get an array of `ValidationIssue`s, each with `path`, `code`, `message`, and optional `did_you_mean`.
 
+**Absolute asset paths are healed, not reported.** A `source: "path"` ingest (or a `hyperframe_render`
+composition) written as an absolute path inside the workspace is rewritten to its canvas-relative form
+and the canvas file is saved, before anything else reads it. `normalized_paths` lists what changed.
+`run` does the same and logs it. This is not cosmetic: an absolute path resolves in the Runtime that
+wrote it, so validate, run, and the preview all pass, and only the publish build — a different checkout
+root, a different session — ever sees the break.
+
+Two roots count as "this workspace": the current one, and `/home/user/repo` (`REPO_PATH`), the fixed path
+every Session's workspace is checked out at. A path under either names the same file in any checkout, so
+remapping it is a proof rather than a guess — which is what lets an already-committed canvas heal in the
+publish build instead of blocking it. Anything under a root that maps to neither is left alone, and the
+scaffold's `validate-creatives` gate still rejects it.
+
 Advisory (warning-severity) video invariants include `VIDEO_PROMPT_DECISION_MISSING` (a thin clip prompt that
 names no camera/motion move **and** no exclusions — the six-decision doctrine) and `VIDEO_HOOK_LAYER_MISSING`
 (the hook, scene 0, is thin across two or more of the four hook layers — text/sound/visual/vibe). Warnings never