v0.14.1

A runnable quick start and a script project in one command

Summary

This release adds quarry init, which creates a ready script project, and brings the documentation into one consistent, runnable form. It also fixes the SDK's Puppeteer range on JSR and the metrics TUI.

Highlights

• quarry init [<directory>] writes a script project: an ES module package.json with the SDK and the Puppeteer packages the executor loads, an example script, a storage directory, and a mise.toml that pins the CLI. It never overwrites a file, installs nothing, and enforces the project's Node.js range through engine-strict.
• The README quick start runs end to end in four commands (init, cd, npm install, quarry run), and a container path runs the example with no local Node.js project.
• The SDK's JSR package depends on puppeteer with the supported range ^24 || ^25, so Puppeteer 24 installs work again.
• quarry stats metrics --tui renders the metrics snapshot.
• The documentation is organized by audience, the contracts state invariants only, and the guides, contracts, and changelog follow one style with vendor-neutral examples.
• The CLI stub views (inspect job, inspect task, inspect executor, stats jobs, stats tasks, stats executors, list jobs, and list executors), which returned fixed stub data, are removed.

Upgrade Notes

• PUBLIC_API.md setup now installs puppeteer-extra, puppeteer-extra-plugin-stealth, and proxy-agent alongside the SDK. Projects set up by hand need them, and quarry init writes them.
• The container guide's standalone docker run passes --user "$(id -u):$(id -g)" so that a run can write a bind-mounted storage directory.

Full Changelog: v0.14.0...v0.14.1