chore(release): publish OpenPI 0.10.0

[tt-a1i]

Problem

The npm latest release is still 0.9.0, so registry users cannot access the Web, Code Mode, delegation, and reliability changes already merged to main since September 24.

Value

Deliver these improvements as OpenPI 0.10.0 with explicit Pi compatibility requirements.

Approach

Bump package.json from 0.9.0 to 0.10.0. No runtime or configuration changes. Publish the merged main commit through the existing tag-driven validation and npm workflow, then verify the registry artifact and a fresh isolated installation.

Validation

Independent read-only review of 041d333 passed with no confirmed blocker. bun install --frozen-lockfile, bun run check, git diff --check, and npm pack --ignore-scripts passed; package contains the Web bundle and Code Mode renderer. bun run test passed: Node 2288 passed / 9 skipped / 0 failed (389.38s), UI 1158 passed across 82 files (46.42s). All 19 PR checks passed, including 17 CI jobs on the exact head 041d333. Slow local fixtures are recorded separately; no timeouts or assertions were weakened. Tag validation and registry installation will be recorded separately after publication.

Impact

• User-visible behavior: package version 0.10.0; release notes describe accumulated main changes.
• Model-visible context/tools, runtime/lifecycle, persisted config/data: none in this version change.
• Compatibility: accumulated main changes require Pi >=0.99.1. The compact Code Mode renderer requires Pi 1.0.2; older supported hosts keep native rendering.
• Risk: publication is permanent; tag and package identities will be checked before publishing, and registry integrity checked afterward.