editorbrain 0.26.0 → 0.27.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "editorbrain",
-  "version": "0.26.0",
+  "version": "0.27.1",
   "description": "EditorBrain editorial knowledge, portable workspaces and skills for AI video agents",
   "type": "module",
   "license": "UNLICENSED",

package/skill/editorbrain/references/workspace-files.md

@@ -61,13 +61,16 @@ The implemented token resolution is:
 
 Token strengths are `required`, `preferred`, and `example`. An `example` is evidence, not an applied value. Read `resolve` output, `tokenSources` and warnings rather than guessing which setting won. Markdown instructions require the agent's interpretation; the resolver does not semantically reconcile every sentence for you.
 
+Token keys are flat semantic names, **not CSS properties**: 1–80 characters, starting with a lowercase ASCII letter, followed by lowercase letters, digits, `_`, `.` or `-`. Use `font_family` or `font.display`, not `fontFamily`; `font.display` is a literal key, not a nested object. `__proto__`, `constructor` and `prototype` are reserved. A value can be a string, finite number, boolean or array of strings. The same key grammar applies to style tokens and project overrides. Map semantic names explicitly to the chosen renderer; there is no automatic CSS or motion-brand binding.
+
 For example, a token rule inside the generated tokens document may be:
 
 ```json
-"accent": { "value": "#2277AA", "strength": "required" }
+"accent": { "value": "#2277AA", "strength": "required" },
+"font_family": { "value": "Inter", "strength": "preferred" }
 ```
 
-That color is illustrative, never a customer default. Preserve the document's `schemaVersion`, `id` and surrounding `tokens` object. To use a different style for one project, select its existing ID in `project.json`; do not overwrite a shared style that other projects use. To create a separate style, use `editorbrain styles create <id> --name "Name" --dir <workspace>` and follow [style creator](style-creator.md). It creates only a local draft; `styles check <id>` checks its structure and declared local resources without rendering or uploading anything.
+Those values are illustrative, never customer defaults. A font declaration does not install a font: verify the actual family/file and load it in the renderer. Preserve the document's `schemaVersion`, `id` and surrounding `tokens` object. To use a different style for one project, select its existing ID in `project.json`; do not overwrite a shared style that other projects use. To create a separate style, use `editorbrain styles create <id> --name "Name" --dir <workspace>` and follow [style creator](style-creator.md). It creates only a local draft; `styles check <id>` checks its structure and declared local resources without rendering or uploading anything.
 
 ## Scripts and media
 

package/skill/editorbrain-motion/SKILL.md

@@ -34,6 +34,7 @@ Separate resolved graphic identity from authentic material: text/graphics use br
 Choose a feasible method per shot, respecting production preferences:
 
 - **Code/compositing:** read [motion with code](references/code-motion.md) for precise states, typography, diagrams, interfaces or repeatable transitions.
+- **Authored reference:** search `list_authored_scenes` / `editorbrain motion scenes` for a relevant visual mechanism, then read one card. Use [authored scenes](references/authored-scenes.md) only when inspecting or adapting its code. These examples complement video evidence and do not prescribe a template.
 - **Reusable component:** use when its action, composition and timing fit the intended beat, or the user requests that template. Search `list_motion_components` / `editorbrain motion list`, then fetch only the selected pinned recipe. Read [component library](references/component-library.md) to bind tokens and prepare locally. Otherwise author the scene; suitable sub-elements may still be reused. Do not load or rewrite a component's code for parameter-only changes.
 - **Generated clips:** read [generated motion](references/generated-motion.md) for material/character consistency, organic movement and continuity.
 - **Hybrid:** use both where needed; keep exact text, values, logos, interface states and continuity-critical objects under explicit control.

package/skill/editorbrain-motion/references/authored-scenes.md

@@ -0,0 +1,22 @@
+# Authored motion references
+
+Use when a scene needs a visual mechanism (an object transforms, a structure falls, a route untangles, data moves). These are optional reference implementations, not the default format for every video. Start with the intended message and action; author a new scene when the available mechanism does not fit.
+
+## Retrieve only what you need
+
+1. `list_authored_scenes` / `editorbrain motion scenes "dependencia"` searches literal intent, mechanism and niche (accent-insensitive); it is not semantic video search. Default six compact results. Use `nextCursor` as `after` / `--after` to continue the same query.
+2. `get_authored_scene` / `editorbrain motion scene word-structure --scene-version 1.0.0` loads one card: purpose, timing, parameter limits, what requires code changes, exact bundle hash. A similar niche alone does not establish fit.
+3. Inspect `get_authored_scene_preview` / `editorbrain motion preview <id> --scene-version 1.0.0 --ratio tall` (optional `--preview-kind poster`). Video and poster links expire after five minutes; downloads remain reference evidence, not a customer-brand render.
+4. Only when using its code, request `get_authored_scene_source` with the exact ID, version and bundle SHA-256; or `editorbrain motion source word-structure --scene-version 1.0.0 --out .editorbrain-local/word-structure.tar.gz`. CLI download needs login, verifies size/hash, preserves existing files, and does not extract or execute. MCP URLs expire; persist IDs/hashes instead.
+
+The CLI commands require 0.27.0 or later; use advertised MCP tools if the installed CLI is older. Existing `motion list/get/prepare` addresses a different, bounded component catalog.
+
+## Adapt, then review
+
+Read the downloaded README and selected card. Extract only the reviewed bundle into a new project-local directory. It includes one scene, runtime, fonts/licenses and synthesized SFX; no private customer reel assets or renderer installation. Use the current local engine/tooling to capture `window.renderAt(t)`. Do not run a missing renderer from an unrelated workspace.
+
+Map resolved project tokens explicitly to every color/font role through `window.__overrides.brand` before scripts load. Register actual font files with the correct weights/styles and rights. Respect exact required tokens and documented scoped exceptions. Set `sound.enabled` from current preferences; false mutes authored and derived cues, music and voice. Replace demo copy, quantities, language and fictional media; branding overrides alone do not personalize those values. Recompose each requested ratio and align beats to actual narration when present. Verify integration access and existing generation authorization before adding media.
+
+`?demo=1` is for inspecting the original reference only. Production requires complete project binding; missing fonts/assets, invalid theme/ratio and unsupported voice/music time scaling must fail rather than silently use a personal identity. Supplied scenes are opaque, not transparent overlays. Do not reinterpret one scene's fixed item count, timing or font as a universal EditorBrain requirement.
+
+Check source/preview provenance and runtime diagnostics, important states and transitions, then actual motion/audio in the adapted output. Existing previews refer to original source; the guarded portable runtime is separately hashed. Technical validation does not prove creative quality or successful transfer. The 33 general mechanisms exclude all personal `human-computers` reel versions.