compass-release

# Compass release Use this skill for the full Compass release path. Compass releases are immutable, multi-platform artifacts, so the version bump, PR, tag, CI build, release notes, and download verification must describe one exact commit. ## Inputs and defaults Extract these from the user request before changing anything: - `version`: the explicit SemVer requested by the user (for example `0.3.7`). Never guess a version when the request is ambiguous. - `with_vsix`: build the VS Code extension when requested; do not publish it to a GitHub release unless the user explicitly asks. - `release_notes`: summarize the user-visible changes since the previous Compass tag. Keep the notes concise and link the changelog and comparison range. - `repo`: the Compass checkout named by the user. Resolve it with `git rev-parse --show-toplevel`; do not assume a particular worktree path. Use these shell variables after the version is confirmed: ```sh version="<requested-version>" tag="compass-v${version}" branch="codex/release-${version}" target_dir="/Volumes/Workspace/crabbuild-target/compass-release-${version}" ``` ## Safety gates Stop and report the blocker instead of improvising when: 1. The worktree has user changes (`git status --short` is non-empty). Preserve them; never use `git reset --hard`, `git clean`, force-push, or overwrite unrelated files. 2. `/Volumes/Workspace` is missing or `$target_dir` cannot be created and written. Cargo must not fall back to a local `target/` direc...