Prepare Posecode 0.2 for third-party embeds

[a-baran-orhan]

What

• define the Posecode 0.2 timing vocabulary, including drive, settle, flow, and snap, while preserving legacy easing aliases
• add a parser validation CLI with recursive, strict, and JSON modes
• expose embed compatibility metadata and structured ready/error events
• support canonical and human-readable per-side ground locks such as foot_left and left foot
• harden inline custom-element startup and reduce cascading parser diagnostics
• update package versions, generated documentation, examples, editor completions, CI, and integration guidance

Why

A third-party basketball site authored movements with the current Posecode vocabulary but loaded posecode-embed@0.1.0. Its cards failed on modes such as drive, and consumer-facing compatibility/version checks were not available. This release makes that mismatch visible, validates assets before deployment, and supports the single-foot contacts used by sports movements.

Impact

Consumers can pin compatible parser/embed versions, validate complete movement libraries in CI, listen for machine-readable embed state, and author basketball-style phases with natural timing and contact language.

Verification

• npm run typecheck
• npm test -- --run — 268 tests passed
• npm run build:packages
• npm run build
• npm run eval — 1,049/1,049 checks across 73 movements; zero parse failures and zero clamp warnings
• npm publish dry-runs for parser, renderer, and embed
• browser smoke test of the built 0.2 embed bundle with drive, settle, snap, travel, and ground-lock: left foot

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
posecode	Ready	Preview, Comment	Jul 15, 2026 2:02pm