editorbrain 0.30.0 → 0.31.0

package/skill/editorbrain/references/storage-and-previews.md

@@ -6,6 +6,10 @@ command availability first; older CLI versions do not include these commands.
 Keep source footage and masters local unless the user asks to upload them.
 `storage status` / MCP `storage_status` reports actual workspace capacity and
 reservations. The current upload limit is 90 MiB **per file**, separate from quota.
+Compare the actual file bytes with capacity minus used and reserved bytes before
+uploading. If it does not fit, inspect eligible cleanup candidates or prepare a
+smaller copy without sacrificing necessary legibility. Do not change a plan/quota
+or bypass protected files. Cleanup still follows the authorization below.
 
 For review, prepare a separate small copy:
 ```sh
@@ -21,10 +25,18 @@ conversion. Never overwrite or delete the original to save space.
 When sharing is authorized, upload the inspected copy with `assets upload <file>
 --purpose preview --source-sha256 <original-hash>`. Use its **own** hash when
 registering a review/sample. Do not present preview verification as master QA.
+`--source-sha256` is optional and must identify different source bytes; omit it
+when uploading the already prepared file without a distinct source asset.
 New final uploads use `--purpose final`; absent purpose protects as original.
 Re-uploading identical bytes reuses the previous category; it cannot relabel a
 protected master as removable. There is no automatic server compression.
 
+Prefer H.264/AAC MP4 for ordinary web/mobile review; preserve special formats only
+when the deliverable needs them. After registering the sample, open its actual
+project page in the correct workspace and verify visible playback and time
+progression. A successful upload, loaded metadata or local decode does not prove
+the hosted player works. Report devices or audio review not actually tested.
+
 Cleanup is optional and separate from editing. Show exact names, sizes and IDs,
 obtain explicit approval, then owners may use `storage cleanup --ids <sha>,<sha>
 --confirm` (max 20), or the web storage panel. Only unused previews/temporaries can

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

@@ -111,3 +111,27 @@ See [memory and review](memory-and-review.md) for memory schemas, version restor
 ## Optional audio production context
 
 Brand `audio.json` and project `audio.json` are selected optional sources, validated and hashed by resolve/pull, exposed as `audioProduction` in resolved/workflow context, and included in handoffs. See [audio production](audio-production.md) only when configuring voice, SFX banks/exclusions or loudness. They contain portable IDs and preferences, not provider credentials or machine-specific paths. Existing projects need no migration. Detailed provenance and QA reports stay private in `.editorbrain-local/` and are read on demand; merely creating a JSON under `videos/` does not add it to resolved context.
+
+## Creative decision ownership
+
+The optional editorial profile field `creativeDirection` in brand `design.md`
+is `automatic` or `guided`; `project.json.creativeDirection` overrides it for
+that video. `resolve`, workflow context and `editorialSnapshot.creativeDirection`
+return the effective mode and its source (`project`, `brand`, or `implicit`).
+Omission preserves legacy guidance, never silently opts a brand into automatic.
+The current explicit task still governs; project changes do not overwrite the
+brand. Both modes inspect library evidence and adapt to the actual material.
+Automatic fills unspecified aesthetics; guided starts from saved choices.
+Neither overrides required tokens, media/audio restrictions, language, review
+or spending. This field does not replace `freedom` (visual consistency),
+`motionSelection` (motion taste), or `reviewMode` (when to ask for review).
+
+`creativePreferencesReviewed` in the same profile records explicit category
+confirmations (including deliberate delegation). The shared guide lists valid
+categories. Partial onboarding intake updates accumulate them; `null` clears
+them. Populated preference fields do not imply confirmation. Effective direction
+includes `configuration: {status, pending}`; explicit guided brands must finish
+pending categories through [onboarding](onboarding.md) before editing. Automatic
+and legacy unspecified brands do not require that checklist. A project override
+does not enroll or complete brand onboarding; an automatic exception skips that
+checklist for the selected video without deleting the saved brand state.

package/skill/editorbrain-motion/SKILL.md

@@ -17,13 +17,21 @@ Read the sibling [EditorBrain contract](../editorbrain/AGENTS.md) once in the ac
 
 Use `resolve_project` / `editorbrain resolve <id>` and `check_workflow` / `editorbrain workflow check` for current context. Reuse valid results already obtained. Read `tokens`, `tokenSources`, warnings, conditional `context.memory.confirmed`, effective `mediaPreferences` and the current member's integration checkpoint. Compare workflow `version` and `contextVersion` at existing checkpoints before proposals, paid generation and full rendering; fetch only changed relevant context. Do not add another approval cycle or reload every guide.
 
-Apply the implemented token precedence: skip `example` tokens; apply style tokens, then brand tokens over matching style tokens, then reasoned project overrides. Changing an effective `required` token requires an intentional, user-supported exception with `overrideRequired: true`. Adapt incompatible techniques; never silently substitute a required color/font. Read [workspace files](../editorbrain/references/workspace-files.md) when resolving conflicts or saving changes. Examples, demos and provider defaults supply no customer palette, typography or preferences. Apply confirmed memory at its stated scope; prose memory cannot bypass required tokens.
+Use the resolved identity without applying a second precedence order. The shared
+[decision ownership](../editorbrain/AGENTS.md#decision-ownership) governs this
+specialty; [workspace files](../editorbrain/references/workspace-files.md) owns
+token precedence and explicit project exceptions. Consult it for conflicts or
+changes. Adapt techniques to the effective constraints. Proposed changes to the
+story, identity or approved timing return to the project direction with their
+reason before dependent work; examples and provider defaults cannot authorize them.
 
 Read [media preferences](../editorbrain/references/media-preferences.md) when interpreting saved choices. Honor exclusions, disabled categories and authorized exceptions; do not force disabled motion. `motionSelection` governs scene selection; `motionProduction` governs production preference, independently. A `code` preference does not authorize a paid AI fallback. Fetch only the selected recipe/version. Before generation, verify the session tool/model and existing spending authorization using [integrations](../editorbrain/references/integrations.md). Declared access or a preference is not a working connection.
 
 ## Design and execute the scene
 
-For a real subject or demonstration, establish the authentic media first using the host's image/video search, browser and user footage. Follow [real media and evidence](../editorbrain/references/real-media.md) when sourcing. Code-based production can composite real photos, captured interfaces and footage; it does not require drawing every element. Animate around inspected evidence; a code animation or generated likeness cannot substantiate a real person, event or product behavior. Abstract explanations and labelled illustrations can still start with authored/generated motion.
+In a full-video edit, reuse the direction and inspected **edited-video references** that explain why this scene needs animation. If they are missing for a new or changed direction, follow [editorial evidence](../editorbrain/references/editorial-evidence.md) before choosing motion. Motion search supplies implementation mechanisms, not evidence that the whole edit fits. For a standalone animation, explicit template request or scoped correction, work from the relevant brief and existing evidence without imposing a new full-video search.
+
+For a real subject or demonstration, establish authentic media from permitted sources first, using user footage and available web tools as allowed. Follow [real media and evidence](../editorbrain/references/real-media.md) when sourcing. Code-based production can composite real photos, captured interfaces and footage; it does not require drawing every element. Animate around inspected evidence; a code animation or generated likeness cannot substantiate a real person, event or product behavior. Abstract explanations and labelled illustrations can still start with authored/generated motion.
 
 Describe each meaningful shot through its intention, visible entry state, action/change, readable or perceptible hold, and exit state. Connect timing to the actual voice, action or music when used. Use the project's existing plan; keep detailed shot records local. There is no required shot count, effect, provider, pilot or sound layer.
 
@@ -31,6 +39,8 @@ Design the visual action for this video's specific message before selecting a co
 
 Separate resolved graphic identity from authentic material: text/graphics use brand roles; footage, skin, product colors, screenshots and logos retain their authentic identity unless the approved direction changes them. Distinguish real interface states from labelled illustrative UI. Preserve the selected style's mechanism while adapting subject, layout and timing.
 
+Before authoring substantial code motion, make a bounded `motion scenes` lookup for the required action and inspect a promising mechanism, if accessible. This is source research for code production, not a competing engine or a requirement to use a template. Reuse valid research during corrections. A bad preset claim may need new copy while its visual mechanism remains useful; reject mechanisms that do not fit.
+
 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.
@@ -39,13 +49,22 @@ Choose a feasible method per shot, respecting production preferences:
 - **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.
 
-Use the engine/provider's real capabilities and relevant skill. The component preparer supplies editable HTML scenes, not an encoded video or generation API. Rendering still uses the available local tools. Test difficult mechanisms when uncertainty warrants it, reusing existing approval.
+For a fully animated/faceless piece with a feasible code route, a JavaScript
+composition can coordinate the whole sequence on one deterministic master clock,
+including photos, generated imagery, footage, masks, camera and audio cues.
+Plan the changing scenes and their handoffs, not a fixed slide layout with every
+element fading in. An encoder such as FFmpeg exports/mixes the result; it does not
+choose its motion. Respect an explicitly chosen engine and use other tools where
+they solve a real production need. Code availability alone does not establish
+that this route is best for every user or that its output is good animation.
+
+Use the engine/provider's real capabilities and relevant skill. The component preparer supplies editable HTML scenes, not an encoded video or generation API. Rendering still uses the available local tools. When the edit prioritizes elaborate motion or faithful transfer, render its most demanding short passage before extending that approach to the whole piece. Compare the actual action, staging, readable holds and transitions with the inspected reference; fix lost mechanisms before adding decoration. This internal check reuses existing approval, including direct mode, and does not require a new customer decision.
 
 ## Review and preserve
 
 Review important states and transition strips, then actual motion and relevant audio. Recompose and verify each requested ratio. SFX remain optional and must respect exclusions; timeline cues or meters do not prove audibility. For substantial motion/audio work use [production and review](../editorbrain/references/production-and-review.md) and the review order in [motion craft](references/motion-craft.md), reusing checks already performed.
 
-Check whether the viewer can tell what changed and why from the animation itself. If removing the moving graphic leaves the explanation unchanged, reconsider whether the motion is only decoration. Do not treat passed font, bounds, seek or encoding checks as artistic approval.
+Check whether the viewer can tell what changed and why from the animation itself. If removing the moving graphic leaves the explanation unchanged, reconsider whether the motion is only decoration. Compare the sequence with the inspected mechanisms and any applicable user-approved quality sample using [production review](../editorbrain/references/production-and-review.md). Do not treat passed font, bounds, seek or encoding checks as artistic approval.
 
 Tie findings to output hash/version and time; distinguish observed, inferred and designed decisions. Frames cannot establish motion, and silent inspection cannot establish sound quality. Report uninspected modalities explicitly. After a local correction, recheck affected events and the delivered whole.
 

package/skill/editorbrain-motion/references/code-motion.md

@@ -10,6 +10,13 @@ A scene needs a meaningful state change: reveal a relationship, assemble a proce
 
 Use short text as part of the action where appropriate: a request can become a constraint, a duration can become a calendar interval, or a word can become a visible boundary. Preserve object identity and show the consequence of each action. Design anticipation, action and a perceptible hold around the beat, rather than dividing every scene into equal steps. Camera moves, masks, deformation and light/dark changes are options, not a required effects checklist. [Motion craft](motion-craft.md) gives the shot intent, starting values and common failures.
 
+Let media participate in the action: an image may fill the frame, become an
+object inside a larger system, then reveal a detail. For example, separate
+information fragments can gather into a summary that carries into the next
+beat. This illustrates a mechanism, not required imagery. When two scenes share
+an object, match its crop, bounds, anchor and state at the handoff; otherwise a
+continuous camera move can hide an accidental jump. Inspect adjacent frames.
+
 Use a compact shot record when the existing plan lacks this detail:
 
 | Field | What to record |
@@ -49,6 +56,11 @@ Use sparse beat frames to inspect composition and dense transition strips around
 
 Recompose each requested ratio: adjust hierarchy, line breaks, staging, asset crop and trajectory as necessary. Generate evidence from each output, since a horizontal pass does not validate a vertical crop. Watch the final export for continuity, pace and closure; listen if audio is present and the modality is available. Follow the shared [production review](../../editorbrain/references/production-and-review.md) for delivery checks.
 
+Compare editorial quality there as well: successful seeks, easing functions and
+font bounds do not show that the scene explains its message or meets a relevant
+approved sample. Review the composite, including imagery and occlusion, not just
+isolated text boxes or the source code.
+
 Keep localized findings concise: `output hash/version → time/interval → observed defect → evidence → correction`. A contact sheet plus transition strips and playable output can be a local review artifact; no particular HTML format or helper is required. Preserve editable sources, asset hashes, engine details and final timing locally. Recheck the modified interval and final delivery without reopening approved unrelated scenes.
 
 For frame boundaries and supplied geometry, read [targeted motion review](../../editorbrain/references/motion-review.md). It provides an optional CLI sampling plan and collision candidates; it does not replace watching motion.