v0.6.3

What's Changed

Fixed

• Runtime: SDK/CLI version mismatches are now classified as version_mismatch instead of executor_crash, with an actionable error message directing users to align their SDK and CLI versions (#133)
• Lode: Upgraded to Lode v0.7.2 — fixes O(n²) flush performance caused by linear snapshot ID lookups in dataset.Write() (pithecene/lode#108) (#135)

Changed

• Runtime: Version mismatch errors increment run_failed (not run_crashed) and do not fire executor_crash metric (#133)
• CLI: version_mismatch outcome maps to exit code 3 (non-retryable, same as policy_failure) (#133)
• Contracts: CONTRACT_RUN.md and CONTRACT_INTEGRATION.md now enumerate version_mismatch as a fifth outcome status (#133)
• Contracts: CONTRACT_CLI.md now documents exit code mapping; CONTRACT_METRICS.md now documents outcome→metric mapping (#137)
• Infra: Migrated npm/JSR scope from @justapithecus to @pithecene-io (#138)
• Infra: Migrated Go module path from github.com/justapithecus/quarry to github.com/pithecene-io/quarry (#138)
• Lode: Upgraded to Lode v0.7.2 (github.com/pithecene-io/lode) (#138)

Lockstep Version Bump

All components at 0.6.3: Go runtime, SDK, contract constant, executor bundle, golden fixtures.

Install

# CLI (via mise)
mise install github:pithecene-io/quarry@0.6.3

# SDK (via JSR)
npx jsr add @pithecene-io/quarry-sdk

# SDK (via GitHub Packages)
pnpm add @pithecene-io/quarry-sdk

Full Changelog: v0.6.2...v0.6.3

What's Changed

• fix(runtime): classify version mismatch as distinct outcome, not executor_crash by @justapithecus in #133
• chore(release): v0.6.3 — version mismatch detection by @justapithecus in #134
• chore(deps): bump lode v0.7.0 → v0.7.1 by @justapithecus in #135
• docs(release): add lode v0.7.1 upgrade to v0.6.3 changelog by @justapithecus in #136
• docs(contracts): add exit codes, outcome→metric mapping for version_mismatch by @justapithecus in #137
• infra: 🔧 migrate org scope from @justapithecus to @pithecene-io by @justapithecus in #138

Full Changelog: v0.6.2...v0.6.3