@pixel-point/toolcraft 0.0.9 → 0.0.12

package/templates/runtime/contracts/component-contracts.test.ts

@@ -89,11 +89,17 @@ describe("Toolcraft template component contracts", () => {
       "Do not place Segmented beside Switch, Color, Select, or another control in an inline row; use Select when a finite choice must occupy a half-width column.",
     );
     expect(select?.useWhen.join(" ")).toMatch(/long labels|many options/i);
+    expect(select?.useWhen).toContain(
+      "Use Select when a dropdown choice is more readable than a row of segmented cells.",
+    );
+    expect(select?.layoutConstraints).toContain(
+      "Standalone Select controls render stacked full-width with the label above the dropdown; do not use the compact side-label row with label left and dropdown right.",
+    );
     expect(select?.layoutConstraints).toContain(
-      "Prefer compact two-column inline layout for related short Select pairs that tune one workflow or entity.",
+      "Prefer compact two-column inline layout only for related short Select pairs that tune one workflow or entity.",
     );
     expect(select?.layoutConstraints).toContain(
-      "Use vertical one-select-per-row layout only as a fallback when a label, selected value, or option text would clip, truncate, or lose internal padding in the compact row.",
+      "Use vertical one-select-per-row layout for single Select controls and as the fallback when a Select pair label, selected value, or option text would clip, truncate, or lose internal padding in the compact row.",
     );
     expect(select?.layoutConstraints).toContain(
       "If a compact Select pair falls back to vertical layout, record the fit reason in the spec or worklog.",
@@ -147,6 +153,28 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Multiple vector controls should live in separate semantic sections unless they intentionally belong to the same entity with other related controls.",
     );
+    expect(contract.decisionCatalog?.ownsValueModel).toEqual(
+      expect.arrayContaining([
+        "user-authored stable position",
+        "user-authored stable offset",
+        "user-authored stable direction",
+      ]),
+    );
+    expect(contract.decisionCatalog?.useWhen).toContain(
+      "Use Vector for paired X/Y values only when the user is meant to manually author a stable two-axis product parameter such as position, offset, direction, focus, anchor, light direction, or color-balance movement.",
+    );
+    expect(contract.decisionCatalog?.doNotReplaceWith).toContain(
+      "Do not replace animation, keyboard input, pointer input, physics, timeline phase, velocity, or simulated pose state with Vector just because the internal value has x/y coordinates.",
+    );
+    expect(contract.decisionCatalog?.acceptableAlternatives).toContain(
+      "Use timeline, keyboard/pointer handlers, motion sliders, path/step controls, or renderer simulation state when movement is generated by animation or user input rather than authored as a stable panel value.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Use Vector only for user-authored stable two-axis product parameters. Do not expose Vector for current animation state, keyboard movement, pointer movement, physics state, timeline phase, velocity, target pose, current pose, or simulated position/direction.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Before adding a Vector control to an animated or interactive product, classify movement ownership as direct-authored, timeline-driven, keyboard/pointer-driven, or simulation-owned. Only direct-authored movement may become a visible Vector control; the other ownership modes stay in renderer/runtime interaction state and use controls such as Speed, Step, Spread, Path, Duration, or Timeline when the user needs tuning.",
+    );
     expect(contract.aiUsageRules).toContain(
       'Use variant: "whiteBalance" for temperature/tint pads: X maps cool blue to warm amber, Y maps green to magenta.',
     );
@@ -160,13 +188,19 @@ describe("Toolcraft template component contracts", () => {
       'Default spatial vector pads use coordinateMode: "screen": dragging left/up makes vector.x and vector.y smaller so canvas objects move left/up without renderer-side Y inversion.',
     );
     expect(contract.aiUsageRules).toContain(
-      "Holding Shift while dragging a vector pad locks movement to the dominant axis; do not build a custom pad just to support axis-constrained movement.",
+      "Vector pad value labels render compact rounded coordinates. Do not expose raw floating-point strings such as -0.07070312499999998 in the controls panel.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Double-clicking a vector pad resets both axes to the control default through the normal runtime value update, matching section header reset semantics; if no default is defined, the fallback is 0,0. Do not add a separate custom reset UI for this basic pad reset behavior.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Holding Shift while dragging a vector pad locks movement to the dominant axis and must not select text or page content; do not build a custom pad just to support axis-constrained movement.",
     );
     expect(contract.aiUsageRules).toContain(
       'Use coordinateMode: "cartesian" only when the product intentionally exposes mathematical Y-up coordinates instead of canvas/screen movement.',
     );
     expect(contract.aiUsageRules).toContain(
-      "Vector is a compound control; acceptance must prove vector.x and vector.y both affect the product output.",
+      "Vector is a compound control; acceptance must prove vector.x and vector.y both affect the product output and that the vector represents a user-authored stable two-axis parameter rather than current animation, input, or simulation state.",
     );
   });
 
@@ -361,6 +395,12 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Do not use Palette when opacity belongs to the same color entity; use ColorOpacity instead.",
     );
+    expect(contract.decisionCatalog?.requiredAcceptance).toContain(
+      "Prove Palette family and shade selections update runtime state immediately, before delayed persistence/commit settles.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Palette is a live control like Color and Slider: family and shade changes must update runtime state immediately so the next canvas interaction uses the selected token without waiting for delayed commit or persistence timers.",
+    );
     expect(contract.aiUsageRules).toContain(
       "Do not use Palette for gradients or color transitions; use Gradient instead.",
     );
@@ -402,13 +442,20 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.commands).toContain("canvas.panBy");
     expect(contract.commands).toContain("canvas.setOffset");
     expect(contract.commands).toContain("media.import");
+    expect(contract.commands).toContain("media.transform");
     expect(contract.capabilities).toContain("editable-size");
     expect(contract.aiUsageRules).toContain(
-      "Use intrinsic-media for single-layer upload/generation apps so imported media natural size becomes canvas.size.",
+      "Do not let canvas.upload choose intrinsic-media by default. Upload without explicit sizing resolves to editable-output so source/background images do not own product output size.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Use intrinsic-media only for true media-viewer or source-native apps where the natural uploaded/generated media size is the product output; record the reason and prove it with intrinsic-media-size acceptance.",
     );
     expect(contract.aiUsageRules).toContain(
       "Use editable-output for generated, exportable, shader, poster, badge, wall, banner, thumbnail, procedural, reference-clone, and product-output apps so users always see Aspect ratio, Canvas width, and Canvas height.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "When an uploaded image is a background/source inside the product canvas, keep the current canvas.size, keep Setup/canvas controls visible, and render the image as cover/crop inside the current canvas bounds without letterbox or aspect distortion.",
+    );
     expect(contract.aiUsageRules).toContain(
       "A user-provided, reference, fixed-format, or base/default size is not a reason to remove size controls; model it as canvas.size plus editable-output so the size is an initial value, not a hidden lock.",
     );
@@ -419,13 +466,13 @@ describe("Toolcraft template component contracts", () => {
       "A reference or previous app lacking a size editor, or defining a fixed-size baseline, is not a fixed-output reason for a generated product app; product-output clones still use editable-output.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Resolved canvas.size exists for every canvas app, but visible Canvas width and Canvas height controls are mandatory only for editable-output sizing and do not depend on settingsTransfer.",
+      "Resolved canvas.size exists for every canvas app, but visible Canvas width and Canvas height controls are mandatory only for editable-output sizing and live in the mandatory runtime Setup section.",
     );
     expect(contract.aiUsageRules).toContain(
       "If canvas.size is provided without an explicit sizing mode, defineToolcraft treats it as editable-output and adds Canvas width and Canvas height controls.",
     );
     expect(contract.aiUsageRules).toContain(
-      "The runtime Canvas width and Canvas height block uses the technical Setup section and renders without a visible section heading; do not add a separate Canvas section label above these fields.",
+      "The runtime Canvas width and Canvas height block uses the mandatory headerless Setup controls block; do not add a separate Canvas section label above these fields.",
     );
     expect(contract.aiUsageRules).toContain(
       "When the user manually edits Canvas width or Canvas height, the runtime keeps the typed dimension, keeps the other dimension unchanged, switches Aspect ratio to Custom, and shows the reduced current ratio in the custom ratio inputs.",
@@ -458,7 +505,10 @@ describe("Toolcraft template component contracts", () => {
       "Use schema persistence policy for app state that should survive reload.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Persistence may include values, canvas, panels, timeline, and layers; history and media blobs are not persisted.",
+      "Persistence may include values, canvas, panels, timeline, layers, and media; history is not persisted.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Use persistence include: [\"media\"] only when runtime media state must survive reload, such as predefined attached files that users can delete, reorder, or transform. Do not use ad hoc storage for media state.",
     );
     expect(contract.aiUsageRules).toContain(
       'Apps with visible runtime panels and localStorage persistence must include "panels" so dragged panel positions survive reload.',
@@ -467,32 +517,35 @@ describe("Toolcraft template component contracts", () => {
       'Apps with localStorage persistence must include acceptance coverage for changing a user setting, reloading the browser page, and seeing the restored value or product output.',
     );
     expect(contract.aiUsageRules).toContain(
-      "Settings import/export is a preset transfer feature for complex apps; it must not be used to hide or replace broken persistence reload behavior.",
+      "Settings import/export is a mandatory runtime preset transfer feature; it must not be used to hide or replace broken persistence reload behavior.",
     );
   });
 
-  it("documents settings transfer as a runtime-owned complex-app feature", () => {
+  it("documents settings transfer as a mandatory runtime-owned feature", () => {
     const contract = getToolcraftComponentContract("settingsTransfer");
 
     expect(contract.kind).toBe("settings");
     expect(contract.stateMode).toBe("runtime-owned");
     expect(contract.aiUsageRules).toContain(
-      'Use schema settingsTransfer: "auto" for complex apps unless the prompt explicitly disables settings import/export.',
+      "Generated apps keep a controls panel so runtime Setup is visible from the first run; product controls are added after that mandatory runtime section.",
     );
     expect(contract.aiUsageRules).toContain(
-      "After adding, removing, or reorganizing controls, sections, timeline, or layers, recalculate settings-transfer eligibility. The runtime threshold is 12 product controls, 5 product sections, or weighted score 18.",
+      "Do not gate Export Settings / Import Settings behind complexity thresholds, app size, or prompt wording.",
     );
     expect(contract.aiUsageRules).toContain(
       "Do not hand-roll settings import/export through app routes, hidden file inputs, or panelActions.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Settings transfer appears as the first technical Setup controls-panel section when enabled and renders without a visible section heading; it imports and exports control values, canvas size, and timeline state.",
+      "Settings transfer appears in the first visible headerless Setup controls-panel block; it imports and exports control values, canvas size, and timeline state.",
     );
     expect(contract.aiUsageRules).toContain(
-      "A settings-transfer section with only Export Settings and Import Settings means canvas sizing is not editable-output or canvas size controls already exist elsewhere.",
+      "App-authored sections must not declare runtime Setup targets such as runtime.settingsTransfer, canvas.aspectRatio, canvas.size.width, canvas.size.height, canvas.renderScale, or panels.timeline.extended; those controls never suppress the mandatory runtime Setup controls.",
     );
     expect(contract.aiUsageRules).toContain(
-      "When settings transfer and editable-output canvas sizing are both enabled, the first technical Setup runtime section contains Export Settings, Import Settings, Aspect ratio, Canvas width, Canvas height, and optional Resolution scale in that order and renders without a visible section heading.",
+      "When editable-output canvas sizing is enabled, the first visible Setup runtime section contains Export Settings, Import Settings, Aspect ratio, Canvas width, Canvas height, and optional Resolution scale in that order.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "When panels.timeline is enabled, Setup appends the Timeline switch as the last control; when panels.timeline is omitted, the Timeline switch must not appear.",
     );
   });
 
@@ -564,13 +617,13 @@ describe("Toolcraft template component contracts", () => {
       "Visual discrete sliders must still drag smoothly; browser performance tests should use expectToolcraftDiscreteSliderDragSmoothness for real pointer drag.",
     );
     expect(slider.aiUsageRules).toContain(
-      "Use schema disabled: true for unavailable sliders; do not recreate a disabled-looking slider with custom markup.",
+      "Use visibleWhen for sliders that are meaningful only in some mode/type/source/include/count states; inactive branches should disappear so the panel shows only controls usable in the current state.",
     );
     expect(slider.aiUsageRules).toContain(
-      "Use disabledWhen for sliders that are only meaningful in some mode values, such as Fill level and Islands being disabled when Fill mode is Full.",
+      "Do not use schema disabled: true or disabledWhen for product sliders; product panels should show only controls usable in the current state. Use visibleWhen for unavailable product states instead of rendering disabled controls.",
     );
     expect(slider.aiUsageRules).toContain(
-      "Do not leave a mode-dependent slider active while making the renderer ignore it; the UI must expose the unavailable state.",
+      "Do not leave an inactive conditional slider visible while making the renderer ignore it; hide it with visibleWhen.",
     );
     expect(rangeSlider.decisionCatalog.requiredAcceptance).toContain(
       "Prove dragging rangeSlider.lower and rangeSlider.upper both affect product output while the drag is in progress, not only after pointer release, blur, Apply, or a final commit.",
@@ -621,19 +674,19 @@ describe("Toolcraft template component contracts", () => {
       "RangeSlider defaultValue must start with different lower and upper values so the two-thumb control does not collapse into a single-value slider.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
-      "Manual range value editing accepts common separators such as slash, hyphen, spaces, and dashes; do not create custom parsers for RangeSlider labels.",
+      "Manual range value editing accepts common separators such as slash, hyphen, spaces, and dashes, including when values include unit suffixes such as 30%-150% or 30% - 90%; do not create custom parsers for RangeSlider labels.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
       "Visual discrete sliders must still drag smoothly; browser performance tests should use expectToolcraftDiscreteSliderDragSmoothness for real pointer drag.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
-      "Use schema disabled: true for unavailable range sliders; do not recreate a disabled-looking range slider with custom markup.",
+      "Use visibleWhen for range sliders that are meaningful only in some mode/type/source/include/count states; inactive branches should disappear so the panel shows only controls usable in the current state.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
-      "Use disabledWhen for range sliders that are only meaningful in some mode values; keep the value so it returns when the mode becomes relevant again.",
+      "Do not use schema disabled: true or disabledWhen for product range sliders; product panels should show only controls usable in the current state. Use visibleWhen for unavailable product states instead of rendering disabled controls.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
-      "Do not leave a mode-dependent range slider active while making the renderer ignore it; the UI must expose the unavailable state.",
+      "Do not leave an inactive conditional range slider visible while making the renderer ignore it; hide it with visibleWhen.",
     );
     expect(rangeSlider.aiUsageRules).toContain(
       "Acceptance must prove both rangeSlider.lower and rangeSlider.upper change the product output; testing one handle is not enough.",
@@ -763,6 +816,9 @@ describe("Toolcraft template component contracts", () => {
     expect(anchorGrid.aiUsageRules).toContain(
       "AnchorGrid is a position selector; acceptance must prove anchorGrid.position changes product placement, not only selected button state.",
     );
+    expect(anchorGrid.decisionCatalog?.acceptableAlternatives).toContain(
+      "Use Vector only for stable direct-authored continuous position or direction parameters.",
+    );
     expect(channelMixer.aiUsageRules).toContain(
       "ChannelMixer is RGB-specific: it renders R/G/B tabs and Red, Green, Blue sliders for an RGB channel matrix.",
     );
@@ -803,6 +859,9 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Every app entity introduced by the AI must have an acceptance test that proves its product responsibility.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "Any supplied video, GIF, screen-recording, contact-sheet, or extracted-frame reference requires a Video Reference Study before implementation: storyboard frames, frame-to-frame transition analysis, behavior decomposition, and acceptance mapping. Do not implement video references from a single screenshot or high-level summary.",
+    );
     expect(contract.aiUsageRules).toContain(
       "Compound control browser tests must explicitly exercise each required value part, not only one visible sub-control.",
     );
@@ -822,16 +881,19 @@ describe("Toolcraft template component contracts", () => {
       "Conditional entities require fixtures that make the condition observable.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Use visibleWhen for mode-, type-, variant-, or count-exclusive sections or controls that do not belong to the current selected state.",
+      "Use visibleWhen for mode-, type-, source-, include-, variant-, or count-exclusive sections or controls that do not belong to the current selected state.",
     );
     expect(contract.aiUsageRules).toContain(
       "When a count/quantity control determines how many sibling controls are available, hide unavailable siblings with visibleWhen; do not render all possible controls while the renderer reads only the first N.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Use disabledWhen for controls that belong to the current entity but are temporarily unavailable for the selected mode; the disabled value must be preserved.",
+      "If a switch/select/segmented/imagePicker/checkbox chooses a branch for the same product entity, controls outside the current branch use visibleWhen, not disabledWhen.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Do not leave inactive conditional controls visible and enabled while making the renderer ignore them.",
+      "Do not use schema disabled: true or disabledWhen for generated product controls; the panel should show only controls usable in the current state. Runtime primitives may still have disabled styling internally, but app schemas should model product availability with visibleWhen.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Do not leave inactive conditional controls visible while making the renderer ignore them.",
     );
   });
 
@@ -867,7 +929,7 @@ describe("Toolcraft template component contracts", () => {
       "Performance matrices must declare rendererWorkload as none, simple-composition, text-output, vector-output, or pixel-output.",
     );
     expect(contract.aiUsageRules).toContain(
-      "A full performance checkpoint must run with pnpm verify:perf only when the first working app version exists or the user requests performance, lag, jank, animation speed, drag/zoom stabilization work, or otherwise complains about performance.",
+      "A full performance checkpoint must run only when the first working app version exists or the user requests performance, lag, jank, animation speed, drag/zoom stabilization work, or otherwise complains about performance; use the agent-controlled browser first and pnpm verify:perf only as the Playwright fallback.",
     );
     expect(contract.aiUsageRules).toContain(
       "Renderer, canvas, animation, export, timeline, layers, canvas.renderScale, bug fixes, and performance-sensitive control changes use targeted functional/browser checks first and targeted performance scenarios only for touched workload, viewport, or export paths.",
@@ -992,12 +1054,21 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Reference clone specs must list every detected transport behavior explicitly, including pause-resume, restart, time-progress, export-at-time, playback, scrub, duration, loop, and keyframes when present.",
     );
+    expect(contract.aiUsageRules).toContain(
+      'Toolcraft reference timelines must declare referenceTimeline.loopDuration with source "reference", "user-request", or "product-derived", plus seconds and evidence; runtime/template fallback 8s is not a valid source.',
+    );
+    expect(contract.aiUsageRules).toContain(
+      "panels.timeline.defaultDurationSeconds must match referenceTimeline.loopDuration.seconds for referenceTimeline.mode toolcraft-playback/toolcraft-keyframes.",
+    );
     expect(contract.aiUsageRules).toContain(
       'Do not downgrade custom reference timelines to panels.timeline mode "playback". State buttons, trim handles, selected-range playback, or range export require referenceTimeline.mode "custom-reference-timeline" and dedicated acceptance.',
     );
     expect(contract.aiUsageRules).toContain(
       "Reference clone acceptance must include referenceCoverage rows for canvas sizing, control mapping, renderer state, and any renderer loop, spawn/update cadence, pause/resume, export/copy, or media lifecycle behavior in the reference.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "Video reference assets used in a reference clone also require starterTransferMode.videoReferenceStudy with storyboard frames, frame-to-frame transition analysis, behavior decomposition, and acceptance mapping.",
+    );
   });
 
   it("documents concise control label rules", () => {
@@ -1024,22 +1095,22 @@ describe("Toolcraft template component contracts", () => {
       "Controls-panel sections should stay discrete: two to seven product controls is the normal size, and larger sections must split by product sub-entity or workflow stage.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Every app-authored controls-panel body section must have a short meaningful visible title. Runtime-created setup/settings sections use the technical title Setup but render without a visible heading; sticky footer action sections use the technical title Export but render without a visible heading.",
+      "Every app-authored controls-panel body section must have a short meaningful visible title. Runtime-created Setup renders as the first visible headerless controls block with no title, reset action, collapse button, or collapsed state; sticky footer action sections use the technical title Export but render without a visible heading.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Every visible controls-panel section title renders through the standard 36px collapsible header row with vertically centered text and the runtime collapse icon; generated apps must not hand-build section headers.",
+      "Every visible app-authored controls-panel section title renders through the standard 36px collapsible header row with vertically centered text and the runtime collapse icon; generated apps must not hand-build section headers.",
     );
     expect(contract.aiUsageRules).toContain(
       "Controls-panel section expand and collapse uses the standard runtime height/opacity animation; generated apps must not replace it with instant custom section visibility.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Ordinary controls-panel section collapsed/expanded state persists as a runtime UI preference per app. It is not undo/redo state, not settings import/export state, and Reset controls must not clear it. Runtime technical Setup/settings sections and sticky footer Export sections are not collapsible.",
+      "Controls-panel section collapsed/expanded state persists as a runtime UI preference per app. It is not undo/redo state, not settings import/export state, and Reset controls must not clear it. Runtime Setup is not collapsible; sticky footer Export sections are not collapsible.",
     );
     expect(contract.aiUsageRules).toContain(
       "Ordinary controls-panel section headers expose the runtime section reset action before the collapse button; it dispatches controls.resetTargets and restores only that section's control targets to their schema defaultValue.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Ordinary controls-panel body sections use 8px top spacing and 24px bottom spacing for their control content. Runtime technical Setup/settings sections use 12px top and bottom spacing to match side padding. Sticky footer action sections keep their dedicated spacing.",
+      "Runtime Setup and ordinary controls-panel body sections use 8px top spacing and 24px bottom spacing for their control content. Sticky footer action sections keep their dedicated spacing.",
     );
     expect(contract.aiUsageRules).toContain(
       "Broad section titles such as Flow, Icon, Shapes, Scene, Text, Typography, or Motion are only valid for small cohesive groups; use specific titles such as Flow Motion, Flow Geometry, Letter Burst, Shape Colors, Logo Glow, Logo Plate, or Text Block for larger groups.",
@@ -1129,21 +1200,51 @@ describe("Toolcraft template component contracts", () => {
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.commands).toContain(
       "timeline.togglePlayback",
     );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.commands).toContain(
+      "panels.setHidden",
+    );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.capabilities).toContain("keyframes");
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
-      "Do not enable the timeline panel just because a renderer is animated.",
+      "Any product output animation must enable the top Toolcraft timeline; do not ship animated product output with only local requestAnimationFrame playback.",
     );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
       "Before choosing no timeline for any animated product, write an Animation Intent Inventory: product transport, editable keyframes, or autonomous decorative output, plus the user-facing time behaviors present or intentionally absent.",
     );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
-      'User-requested product animation defaults to panels.timeline mode "playback" unless the spec explicitly declares autonomous decorative/self-running output with no play, pause, scrub, duration, loop, or export-at-time behavior.',
+      'User-requested product animation defaults to panels.timeline mode "playback" unless the spec explicitly declares autonomous decorative/self-running output with no play, pause, scrub, duration, loop, export-at-time behavior, or video export.',
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      'Any product app with Export Video must enable the top Toolcraft timeline: use panels.timeline mode "playback" for product animation transport, or mode "keyframes" when exported animation is driven by keyframes.',
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "Video export renderers must render deterministic frames from runtime timeline timestamps and duration; do not treat autonomous wall-clock time or captureStream recording time as the source of product duration.",
     );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
       "Playback renderers must consume runtime timeline state; pause freezes output, scrubbing renders a deterministic frame, and the full animation cycle maps to state.timeline.durationSeconds instead of a local fixed duration.",
     );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
-      "Playback renderers may compute an initial default duration, but must not watch state.timeline.durationSeconds and dispatch timeline.setDuration back to a computed local duration. User-edited timeline duration is the source of truth after initialization or reset.",
+      'When panels.timeline is enabled for a new Toolcraft app, appTransferMode.animationIntent must match it: mode "timeline-playback" for playback, or mode "timeline-keyframes" for keyframes.',
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "When the product has a known loop duration, declare it as panels.timeline.defaultDurationSeconds; the runtime timeline duration starts from that loop duration instead of an unrelated 8s default.",
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      'Timeline animation intent must declare loopDuration with source "reference", "user-request", or "product-derived", plus seconds and evidence; runtime/template fallback 8s is not a valid source.',
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "panels.timeline.defaultDurationSeconds must match animationIntent.loopDuration.seconds for playback/keyframe animation, so the initial timeline UI shows the declared product loop instead of a generic default.",
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "Playback renderers may compute an initial loop duration default during app initialization or reset, but must not watch state.timeline.durationSeconds and dispatch timeline.setDuration back to a computed local duration. User-edited timeline duration becomes the loop duration source of truth after initialization or reset.",
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "Playback renderers should use getToolcraftTimelineLoopTime or getToolcraftTimelineLoopProgress to derive product loop phase from state.timeline.currentTimeSeconds and state.timeline.durationSeconds; do not hand-roll wall-clock, fixed-duration, mirror, yoyo, ping-pong, or reverse phase math.",
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "Product animation loop means a seamless forward-only cycle by default: motion advances in one direction, first and last frames stitch without a visible jump, and mirror/yoyo/ping-pong/reverse loops require explicit user request.",
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "Changing timeline duration must preserve seamless forward-loop semantics: one full product animation cycle maps from 0 to state.timeline.durationSeconds, first and last frames still stitch, direction does not reverse, and changing duration must not switch the renderer to wall-clock or fixed local speed.",
     );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
       "When non-looping playback reaches the end, pressing Play again restarts playback from time 0.",
@@ -1187,6 +1288,12 @@ describe("Toolcraft template component contracts", () => {
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
       'Custom timeline UI is allowed only for explicit referenceTimeline.mode "custom-reference-timeline" transfers with browser-backed referenceTimelineCoverage.',
     );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      'When panels.timeline is enabled, runtime inserts a Setup switch labeled "Timeline" as the last runtime setup control after Resolution scale.',
+    );
+    expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
+      "The Timeline Setup switch controls only compact versus extended runtime presentation: off shows the compact Play-only transport, on shows the extended timeline with scrubber, duration, loop, and keyframe UI. It must not stop playback, change keyframes, affect export, enter product values, or be reset by Reset controls/settings transfer.",
+    );
     expect(TOOLCRAFT_COMPONENT_CONTRACTS.timelinePanel.aiUsageRules).toContain(
       "If timeline verification fails, wire the renderer to runtime timeline state or remove panels.timeline.",
     );
@@ -1215,6 +1322,9 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Product-output apps must always include export in panelActions.",
     );
+    expect(contract.aiUsageRules).toContain(
+      'Export-labeled panelActions use icon "upload-simple", matching the Setup "Export Settings" action; do not use "download", "download-simple", or "export" icons for Export PNG or Export Video.',
+    );
     expect(contract.aiUsageRules).toContain(
       "Static or still-output apps include Export PNG as the primary footer action.",
     );
@@ -1236,6 +1346,9 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Animated apps include Export Video as the primary footer action and Export PNG as a secondary footer action.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "Any app with Export Video must enable the top Toolcraft timeline; video duration, loop, and rendered timestamps come from runtime timeline state.",
+    );
     expect(contract.aiUsageRules).toContain(
       'Animated apps with Export Video must expose a separate "Video Export" controls section.',
     );
@@ -1266,6 +1379,12 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Video export code must choose the actual MIME/container through MediaRecorder.isTypeSupported or an equivalent encoder capability check, then fall back safely.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "Video export must use getToolcraftVideoExportSize for current and 4K dimensions. Current video export uses the current canvas/output size with even encoder-safe rounding; 4K video fits inside an encoder-safe 3840x2160 box, preserves canvas aspect ratio, and uses even pixel dimensions. Do not hand-roll 4096px long-edge video sizing.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Video export must set recording canvas dimensions before captureStream, MediaRecorder, VideoEncoder, or equivalent encoder setup, and must reject recorder/encoder errors instead of returning corrupt blobs.",
+    );
     expect(contract.aiUsageRules).toContain(
       "Offline video export duration must be encoded from runtime timeline timestamps. Do not rely on canvas.captureStream plus MediaRecorder wall-clock recording time as the only duration mechanism for rendered-frame export.",
     );
@@ -1288,7 +1407,7 @@ describe("Toolcraft template component contracts", () => {
       "PNG export must use createToolcraftPngExportCanvas so background transparency and selected image dimensions or retina fallback are applied consistently; turning Include off makes preview product background and PNG alpha transparent without hiding the Toolcraft canvas backing or video background.",
     );
     expect(contract.aiUsageRules).toContain(
-      "Video export must keep product background and use getToolcraftRetinaExportSize for retina dimensions.",
+      "Video export must keep product background and use getToolcraftVideoExportSize for current/4K output dimensions.",
     );
     expect(contract.aiUsageRules).toContain(
       "Copy PNG can be a secondary action when clipboard output is useful, but copy does not replace export.",
@@ -1310,10 +1429,21 @@ describe("Toolcraft template component contracts", () => {
   it("documents file upload ownership across single-layer and multi-layer apps", () => {
     const contract = getToolcraftComponentContract("fileDrop");
 
-    expect(contract.commands).toEqual(["media.delete", "media.import", "media.reorder"]);
+    expect(contract.commands).toEqual([
+      "media.delete",
+      "media.import",
+      "media.reorder",
+      "media.transform",
+    ]);
     expect(contract.aiUsageRules).toContain(
       'Use fileDrop with assetKind: "image" for image-only source media and assetKind: "file" for arbitrary uploaded files.',
     );
+    expect(contract.aiUsageRules).toContain(
+      "If an app ships with predefined source files or background images, declare them as schema media.defaultAssets with sourceTarget matching the fileDrop control. They must render as ordinary attached files in fileDrop, not as hidden renderer constants or canvas placeholder artwork.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "Predefined media files are default runtime state: users can remove them to get an empty source/canvas state, persistence may keep that removal with include: [\"media\"], and global or section Reset restores the default attached files.",
+    );
     expect(contract.aiUsageRules).toContain(
       "When uploaded/imported content is part of the source-material flow, the canvas must not show agent-invented artwork, CTA text, fake sample output, decorative placeholders, or preset source designs before real content exists; keep the canvas neutral/runtime-backed and put upload affordance in fileDrop.",
     );
@@ -1323,11 +1453,17 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "In single-layer apps, the runtime shows the uploaded image as the fileDrop preview and provides the clear action.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "In image mode, the runtime owns image transform actions: 90° Right, Flip horizontal, and Flip vertical. These actions render through the built-in actions-control in one three-column row with compact visible labels: 90°, Flip H, Flip V; keep a 6px vertical gap between the uploader and action row. Do not create a custom image action button grid. They update runtime mediaAssets transform metadata, and product preview/export must consume that metadata instead of keeping a separate transform state.",
+    );
+    expect(contract.aiUsageRules).toContain(
+      "When exactly one uploaded image is present, image transform actions are visible immediately. When multiple images are present, users select a thumbnail first; no transform actions render until a thumbnail is selected, and the action applies only to that selected image.",
+    );
     expect(contract.aiUsageRules).toContain(
       "In file mode, the runtime shows uploaded files as a sortable list with paperclip icons, file names, remove buttons, and --border/5 separators.",
     );
     expect(contract.aiUsageRules).toContain(
-      "In single-layer apps, global Reset controls and section reset must remove uploaded fileDrop source media and return the fileDrop target to defaultValue.",
+      "In single-layer apps, global Reset controls and section reset must restore fileDrop source media to schema media.defaultAssets for that target; when no default asset exists, Reset removes uploaded media and returns the fileDrop target to defaultValue.",
     );
     expect(contract.aiUsageRules).toContain(
       "Use fileDrop with multiple: true when the app needs several uploaded images as one source set; do not build a custom thumbnail uploader for this.",
@@ -1341,6 +1477,9 @@ describe("Toolcraft template component contracts", () => {
     expect(contract.aiUsageRules).toContain(
       "Dragging thumbnails reorders runtime mediaAssets; preview, export, and renderer mapping must consume that media order instead of maintaining a separate product-only order.",
     );
+    expect(contract.aiUsageRules).toContain(
+      "When uploaded images are used as canvas/background source material, draw them with cover/crop behavior: scale proportionally until the current canvas bounds are fully covered, keep the canvas size/settings unchanged, and crop overflow at the canvas bounds.",
+    );
     expect(contract.aiUsageRules).toContain(
       "Do not create custom upload buttons, file lists, or file sorting for generic source uploads when fileDrop can represent the source set.",
     );