Fixed
- Make
/spec-kitty.planstop instructing agents to update imaginary
agent-specific context files or hunt for non-existentagent context update
commands. Planning now stays focused on the actual mission artifacts it owns. - Clarify
/spec-kitty.specifymission-handle timing and non-blocking charter
behavior so creation-time flows do not assume a mission already exists or stop
on missing charter state. - Tighten generated
/spec-kitty.implement,/spec-kitty.review, and
/spec-kitty.mergewrappers so they use the canonical--mission <handle>
language and explicitly avoid redundant context rediscovery, including
separate charter loads.