v6.2.2

What's New

Setup now explains a sandbox-blocked initialization

• When a setup step fails with Operation not permitted (EPERM), spex-setup-report.sh adds an actionable hint. This typically happens under Codex, whose workspace sandbox guards the project's .agents/ directory (where spec-kit installs its Codex skills), so specify init stops there. The hint points to the fix: approve the filesystem escalation when prompted, or grant the project write access to the blocked directory.
• Builds on v6.2.1's change that surfaces a failed step's stdout, so the real error and the hint now appear together instead of only "Shell command exited with code 1."

Full Changelog: v6.2.1...v6.2.2