v0.7.2

IPC stability fix and container runtime hardening

Summary

Fixes a critical IPC hang caused by third-party code writing to stdout, and addresses several container runtime regressions introduced by the Chrome for Testing migration.

Highlights

• 🐛 IPC stdout guard — third-party code (puppeteer-extra, stealth plugin) writing to process.stdout no longer corrupts the IPC channel; stray writes are redirected to stderr with a diagnostic warning (#161)
• 🐛 Restore TLS trust store — ca-certificates is no longer purged from the full container image, fixing HTTPS failures at runtime (#160)
• ⚡️ Chrome for Testing — full image now uses a pinned Chrome for Testing tarball instead of distro Chromium, matching the puppeteer compatibility matrix (#159)
• 🦺 Architecture guard — full image build fails fast on non-amd64 instead of silently producing a broken image (#160)
• 🐛 Add libasound2 — missing ALSA shared library added to Chrome dependency set (#160)

Breaking Changes

• Full container image (ghcr.io/pithecene-io/quarry:0.7.2, :latest) is now amd64-only. arm64 users should use the slim image with an external browser sidecar.

Upgrade Notes

• If pulling :latest on arm64, switch to :0.7.2-slim and provide Chromium via --browser-ws-endpoint.
• No SDK API changes. Drop-in replacement for 0.7.1.

Full Changelog: v0.7.1...v0.7.2

What's Changed

• docs(container): 🚚 extract container guide from PUBLIC_API.md by @justapithecus in #156
• fix(ci): ⚡️ build slim image before full to maximize cache reuse by @justapithecus in #157
• fix(examples): 🐛 disable browser reuse in example runner by @justapithecus in #158
• fix(container): ⚡️ use Chrome for Testing tarball on amd64 by @justapithecus in #159
• fix(container): 🐛 fix runtime regressions in full image by @justapithecus in #160
• fix(ipc): 🐛 protect IPC channel from stray stdout writes by @justapithecus in #161
• chore: 🔖 bump lockstep version to 0.7.2 by @justapithecus in #162

Full Changelog: v0.7.1...v0.7.2