@koda-sl/baker-cli 0.199.0 → 0.200.0

package/README.md

@@ -4560,6 +4560,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