Day shift skills: ready-for-agent on a Spec means its Tickets are published #286

Parent

#212

What to build

Today the Day shift's spec skill labels a Spec ready-for-agent when it is published, minutes or days before the ticket skill attaches its Tickets. A Spec with no Tickets yet looks exactly like a standalone Ticket, so a Pickup run would start a plain Run on it.

Change the repository's own copies of the two skills, the ones a person uses in a Day shift session, not the Factory skills:

• The spec skill asks, when it publishes, whether Tickets will follow. If so it labels the Spec needs-triage and says that the ticket skill will mark it ready. If not, the Spec stands alone as one session of work, and it labels it ready-for-agent.
• The ticket skill, given a Spec, swaps the Spec's needs-triage for ready-for-agent as its last step, after every Ticket and every blocking link is published. This replaces its rule not to modify the parent issue, for the label only.

The triage label doc says what ready-for-agent means on a Spec, and that in-progress is thirdshift's own label for a Claim, not a sixth triage role.

The Factory skills already label a plan needs-triage and are not changed.

Acceptance criteria

• The Day shift spec skill asks whether Tickets will follow and labels the Spec needs-triage or ready-for-agent accordingly.
• The Day shift ticket skill swaps the Spec's needs-triage for ready-for-agent last, and still changes nothing else on the parent issue.
• The triage label doc explains ready-for-agent on a Spec and names in-progress as thirdshift's label.
• The Factory skills and the generated prompts are unchanged.

Blocked by

None (can start immediately).