pi-commandcode-provider 0.6.2

Summary

• Fix omp plugin install on Oh My Pi 18.x: 0.6.1 imported registerApiProvider from @earendil-works/pi-ai/compat, which OMP's bundled pi-ai does not export, so the plugin failed extension validation. The compat registration now resolves at runtime and is skipped on hosts that register custom APIs themselves (#74, #75).
• Run the Oh My Pi compatibility suite against a real omp binary in CI as a required check, so a change that only loads on plain pi fails before release (#75).
• Pin the CI memory benchmark and Oh My Pi jobs to Bun 1.4.0, Node 22.23.2, and pi 0.84.4 (#76).

No runtime behaviour changes for plain pi compared to 0.6.1.

Full list: CHANGELOG.md

Contributors

• @AmeMizuki — #74

Validation

• npm test (214 unit tests, pi-local end-to-end against a mock Command Code API), typecheck, format:check, git diff --check
• npm audit --audit-level=moderate: 0 vulnerabilities
• CI green on release commit 245c352 (#77), including the new required Oh My Pi compatibility check (omp 18.1.2, Bun 1.4.0)
• Reproduced #74 with omp 18.1.2: plugin install pi-commandcode-provider@0.6.1 fails, @0.6.0 succeeds; @0.6.2 installs

Links

#74 #75 #76 #77