post-merge-cleanupsolid

# post-merge-cleanup The walk back from a merged PR, selected by cleanup intent or an explicit entry. The work has landed on the default branch. What is left is local: the branch you are standing on, and whatever the run left in the tree. This skill returns you to a clean, fast-forwarded default checkout without losing anything you have not explicitly agreed to lose. **It is ordinary lifecycle work and never needs `$ca-override`.** When it cannot proceed, it names the gate that stopped it. Issue #308 recorded the alternative: with no owner for this transition, the routing loop reached for `$ca-chore`, then for `$ca-override` — a bypass manufactured to cover a coverage hole. <!-- catalog-compatibility-notice:start --> > Compatibility route. Prefer `$ca-pr --cleanup` for new explicit usage. The retained entry > and natural-language intent use this owner under > [includes/command-compatibility.md](../../includes/command-compatibility.md). <!-- catalog-compatibility-notice:end --> ## Entry boundaries Select this owner for an already-merged branch cleanup request, `$ca-pr --cleanup`, or the explicit `$ca-cleanup` compatibility entry. Do not require repeated slash syntax. An explanation-only or dirty-state question is read-only, not a deletion request. An unmerged branch belongs to the finishing owner, not this cleanup. MUST NOT require `$ca-override` for ordinary cleanup; name a real blocker instead. This owner neither stages nor commits. Keeping work may hand it to the exis