v0.7.1

Containerized distribution and stdout flush reliability fix

Summary

Quarry is now available as container images via GHCR, and a race condition causing false executor_crash classification on successful runs has been fixed.

Highlights

• 🐳 Container images via GHCR — ghcr.io/pithecene-io/quarry:0.7.1 (full, with system Chromium + fonts) and ghcr.io/pithecene-io/quarry:0.7.1-slim (no browser, BYO Chromium via --browser-ws-endpoint)
• 🐛 Fix false executor_crash — process.exit() was discarding buffered stdout before it reached the OS pipe, causing the Go runtime to see EOF without a terminal event and misclassify successful runs
• ✅ Integration test for pipe boundary — dedicated regression test spawns a child process writing IPC frames and asserts all frames (including terminal event) are readable before EOF
• 👷 Dockerfile lint in CI — docker build --check runs on PR and main workflows
• 📝 Container usage docs — standalone docker run, Docker Compose with FS/S3, slim image with external browser sidecar

Upgrade Notes

• No breaking changes from v0.7.0
• Container users: the full image includes system Chromium and sets QUARRY_NO_SANDBOX=1 automatically
• The slim image requires an external browser via --browser-ws-endpoint

Full Changelog: v0.7.0...v0.7.1

What's Changed

• docs(readme): 📝 update docs for v0.7.0 by @justapithecus in #151
• feat(ci): 🐳 add containerized distribution via GHCR by @justapithecus in #152
• fix(executor): 🐛 drain stdout before exit to prevent false executor_crash by @justapithecus in #153
• chore: 🔖 bump lockstep version to 0.7.1 by @justapithecus in #154

Full Changelog: v0.7.0...v0.7.1