You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The run-published-issue catalogue Step starts a Ticket run, or a Spec run for a Spec, on the issue the session Step before it published, as part of this Command (a child run, not a Command of its own). That Step's final message ends with the issue's URL on its last line, as an Architecture review names its plan. thirdshift checks the issue as it checks an Architect plan: in this repository, open, by a Trusted account, and created since the Step began. This is how a Process can grill, spec and then build, with the Spec's Tickets running in parallel worktrees.
Acceptance criteria
A Process whose session Step publishes a Spec, followed by run-published-issue, starts a Spec run on it, whose Ticket runs run in parallel up to spec.parallel.
A published standalone Ticket gets a Ticket run.
A final message without the URL line, or an issue that fails the checks, fails the Step without starting a run, naming the reason.
run-published-issue not directly after a session Step is refused.
The child run's outcome decides the Step's outcome, and it is recorded under the Process's Command.
Activity
JacobStephens2 commentedon Oct 27, 2026
Closed by #1427, merged into issue-877 by a thirdshift Ticket run with Self-merge.