#1175 Link new tickets to their blockers and parents

[williamthorsen]

What

The create-ticket skill now instructs agents to propose a blocked-by, blocking, or parent relationship when the reason for creating the ticket implies one, confirm it with the user, and to record it on the tracker itself rather than as prose in the ticket body. The --blocked-by, --blocking, and --parent flags set the relationship directly.

Why

Work that deserves more than one pull request gets more than one ticket, and those tickets stand in real relationships to each other. Reaching the forge unlinked, they lost those relationships to whatever a body happened to say, leaving the tracker's own blocker and sub-issue views blank on work that had them.

Details

🎉 Features

• An ## Arguments section declares --parent, --blocked-by, and --blocking, each taking ticket references in the project's own form. related is absent from the vocabulary because GitHub cannot express it.
• A new step 4 decides the relationships from the reason the ticket is being created, sharpened by the ticket the current branch derives from. An explicit argument replaces the inference for its own relationship. Where nothing applies, the step passes silently, so the common backlog-idea case gains no prompt.
• Deciding sits after platform resolution, so a confirmation can name a relationship the resolved forge cannot express while it is still free to drop.
• A new step 7 applies the relationships once the ticket exists, carrying all three in a single gh issue edit call on the GitHub path. Applying after creation means a rejected reference costs the link and never the ticket.
• Nothing in the relationship path can abort the run. A forge that expresses no relationships, a type it cannot express, a failed call, and a path that creates no remote ticket at all are each recorded and skipped, and the completion output names every relationship created and every one skipped with its reason.
• The GitHub path is documented against the gh 2.94 flags rather than the REST dependencies endpoint they replace, which takes an issue's database id and forces a lookup the flags removed.

♻️ Refactoring

• Two inserted steps shift four others, so every step cross-reference in the skill was renumbered as its own pass.

🧪 Tests

• create-ticket joins the reinforced-skills list, so the action-items convention it now inlines is held in place against a later DRY sweep.

Closes #1175

[github-actions]

Dependency audit

Production dependency audit passed.