v2.0.3

Highlights

This release fixes a silent deploy failure that let targets run current skills against stale .scrum/scripts/ wrappers, plus the framework-upgrade safety net that keeps it from ever recurring.

Fixed

• Space-safe deploys (#70): setup-user.sh's copy_tree word-split its glob, so a framework under a path containing a space — exactly the Mac app's extracted bundle in ~/Library/Application Support/MaulTeam/ — silently deployed nothing for agents, hooks, rules, and .scrum/scripts wrappers while skills kept updating. All deploy classes now copy correctly from any path.
• Content-keyed framework extraction (#71): the Mac app keys its extracted framework on the bundled commit (framework-<version>-<rev>), so a rebuild at the same version can no longer serve a stale extraction; older caches are swept automatically.

Added

• Upgrade safety (#70): every launch now clean-slate redeploys the wrappers, runs all idempotent state migrations with a hard launch gate (migrate-state.sh), and stamps the deployed framework revision into .scrum/deploy-stamp.json for staleness diagnosis. The status enum is derived from the deployed schema instead of being hardcoded.
• Regression tests deploying end-to-end from a spaced, git-less framework copy; CI now runs the full recursive bats suite and the macapp Swift tests.

Upgrading

Install this build and reopen your project — the next launch fully syncs the deployed wrappers. PBIs already refined before the upgrade are not retroactively gated: if a kind=code PBI is missing demo_plan, set it via .scrum/scripts/set-backlog-item-field.sh <pbi> demo_plan '<how to demo locally>'.

🤖 Generated with Claude Code