surface

Cut a Surface release the way this repo does it — prepare the version-bump PR (Cargo version, Cargo.lock, doc pins, CHANGELOG) off a release/X.Y.Z branch, then after it merges, tag vX.Y.Z to trigger the build/npm-publish/docs-sync workflow. Use when the user asks to "cut a release", "release X.Y.Z", "prepare a release", or "tag the release".

Open a pull request for the current work following this repo's conventions — branch off main, run the gates, commit with the Co-Authored-By footer, push, and open a PR with the 🤖 footer and a Closes

Explain something in plain, non-technical language — "explain like I'm 5". Use when the user asks to ELI5, "explain simply", "in plain English", "what did we just do", or wants a jargon-free version of a PR, diff, commit, code, error, or concept.

Scan a milestone (or the backlog / open issues) for low-effort, high-value work, triage genuine quick wins from disguised epics, and recommend what to do next. Use when the user asks for "quick wins", "low-hanging fruit", "what's easy in milestone X", or "anything I can knock out".