Bigger fixes as a Spec with Tickets, and a private finding's own issue as its fix #545

Parent

#427

What to build

Bigger fixes. When the reproduction judged that one session can't hold a fix, the fix-publishing session publishes a Spec with Tickets, through thirdshift-to-spec and thirdshift-to-tickets. Each issue is terse and links the private record. The Security run dispatches a Spec run on it, and ends as that Spec run ends.

Private repositories. The finding's own issue becomes the fix's issue: the Ticket, or the Spec whose Tickets are its sub-issues.

Acceptance criteria

• A finding judged too big for one session is fixed by a Spec run on a published Spec with Tickets, each issue terse and linking the record.
• On a private repository, no second issue is published for a one-session fix: the finding's issue is marked ready and dispatched.
• On a private repository, a bigger fix gets its Tickets as sub-issues of the finding's issue.