The Inbox's groups in thirdshift status #816

Parent

#776

What to build

thirdshift status shows the Inbox: the machine's Commands grouped by what each asks of the Day shift, in the order the Console will show them. The groups:

• Needs you:

  • live problems first: Silent, then Slow;
  • then, newest first:
    • Died: the process is gone with no outcome;
    • Failed;
    • Triage: a Stop that left the issue needs-triage;
    • Finding: a Security finding waiting on a decision.

  An ended item leaves Needs you when a later Command on the same issue starts on this machine, or once it's older than inbox.days (7 by default). Failures with the same cause show as one item with a count.

• Ready for review: ended ready, with its pull request.

• Landing: live Runs at CI watch or Self-merge. One already in Needs you is pointed to there, not listed twice.

• Working: every other live Command, with a Spec run's Tickets beneath it.

• Done: ended in the last day.

• Resolved: ended from one day to inbox.days ago, with nothing waiting.

--all still adds the history. Each row has a state word, so nothing depends on colour. The grouping lives in the shared blocking code, so the Console can render it.

Acceptance criteria

• status prints the groups in this order, with Needs you ordered as described.
• status --json gives each Command its group, and its Needs you kind where it has one.
• An ended problem leaves Needs you when a later Command on the same issue starts, or after inbox.days. Nothing is read from GitHub.
• Failures with the same cause collapse into one item with a count.
• Landing doesn't list a Command that's already in Needs you.
• inbox.days defaults to 7, and also bounds Resolved.
• Tested through the binary with fixture Command records, prior art Spec: see, follow and Stop a machine's Commands from the CLI #711's status tests.