v0.2 Plan

Scope

v0.2 focuses on three areas:

1. Agent-facing expression helper docs and schema guidance (#32)
2. Theme and palette support proposal (#33)
3. Pure-data animation tick API (#31)

The v0.2.0 release candidate scope is now closed to new runtime features. Second-stage planning is documented here rather than kept as a long-running planning issue.

Status: Released to npm as @yangyus8/emotile@0.2.0.

#32: Expression Helper Docs

• Valid minimal expression examples
• Common repairable mistakes catalog
• Recommended generation constraints
• How to use validate / normalize / repair effectively

#33: Theme and Palette Proposal

• Compare external palette input vs expression-embedded palette
• Design for deterministic color mapping
• No runtime theme implementation in this issue
• No schema changes unless Architect approves follow-up implementation issue

#31: Animation Tick API

• Explicit time / tick input
• No runtime loop, no timers, no requestAnimationFrame
• No browser / Canvas / GPU / desktop-pet dependency
• Output must be pure data (expression or PixelFrame)
• Behavior must be deterministic

v0.2.0 Release Scope Decision

v0.2.0 should ship with:

• tickExpression
• Agent helpers and generation guidance
• The theme/palette design proposal

Theme/palette runtime support is deferred to v0.3 by default. A narrow v0.2 runtime follow-up should only be considered if a concrete downstream integration needs it before release. Until then, do not create Builder runtime issues for theme/palette implementation.

Explicitly Deferred

• Variable canvas sizes
• Theme/palette runtime implementation
• ESM / dual-build
• Browser / Canvas / GPU integration
• Preset expression catalogs (happy_01, sad_02, etc.)
• PNG / SVG / GIF export
• Terminal renderer (braille/unicode)
• Game engine integrations