Ticket-fleet compatibility

A "ticket" here is a Plane ticket, identified by its key (for example GRIM-87), not a GitHub issue. A PR for it stays on GitHub and references the key plus the Plane URL (Refs GRIM-87).

For an existing /ticket-fleet request, use the single delivery workflow in ../ship-it/SKILL.md at the PR endpoint. It ends after publication and fresh checks; it never merges. If the user separately requests a later endpoint, handle that as an explicit /ship-it request under its normal workflow. For multi-ticket coordination, read ship-it's batch reference.

An explicit /ticket-fleet invocation that names the task and owning repository is the user's request to prepare and publish PRs as needed to reach this endpoint, subject to global policy and exact target/change preview. If the repository or target is unclear, clarify it before publication. Automatic skill selection does not authorize publication.

This compatibility entrypoint does not launch headless sessions, grant tool permissions, invoke local models, or authorize merge or deployment. The global AGENTS.md remains the authority source for mutation boundaries. Legacy runner scripts now fail closed and direct callers to /ship-it.