v0.3.8

Fixes

• Keep Cursor provider streams, replay helpers and Pi tool bridges bound to the running Pi host, including packaged installations with local peer dependencies. Stock Pi remains supported.
• Validate SDK replay and bridge tool arguments as JSON objects before Pi dispatch.
• Check the common supported-host contract on published Pi, pinned official source and the maintained fork; qualify historical checkpoint behavior separately on the fork.
• Preserve terminal hyperlink text when validating smoke-test read cards.

Existing extension filters

The Pi entrypoint moves from dist/index.js to the already-shipped src/index.ts. Update explicit include filters to +src/index.ts. For disabled installations, add -src/index.ts and retain -dist/index.js for rollback. Update !dist/** filters to !src/** as appropriate. Settings are not rewritten automatically.

Native source loading does more initial work. Three fresh-process, warm-cache loader measurements on macOS/Node 24.21.0/Pi fork 90e6 were 0.85–1.24 seconds for source versus 0.08–0.13 seconds for dist. These are loader measurements, not TUI startup timings or guarantees for other environments. Compiled output remains available to scripts and programmatic consumers.

Verification

All three named local reviews are green. All 30 required macOS/Ubuntu platform suites and both cleanups passed using the exact published archive. PR and post-merge CI passed against published Pi 0.85.1, pinned official source and the maintained fork.

Windows execution was explicitly waived on the maintainer's machine; Windows support is unchanged. The compaction smoke now verifies the actual persisted summary and SDK bootstrap input and rejects tool-assisted recall. This strengthens the evidence without changing production prompts or claiming a general model-reliability fix.