Passes in the Command record, and idle Passes in status #770

Parent

#711

What to build

Architect runs and Security runs appear in the Command record and in thirdshift status, and so do Passes that are sitting idle.

• Architect runs and Security runs record their stages: Architecture review; Security audit, Security reproduction and Security fix publishing. A Pass that dispatches a Spec run or a Run records it, so status nests it under the Pass.
• A Pass with no issue shows under its kind and its Command log stamp.
• Idle Passes. For each repository and kind of Pass whose latest Activity log line is a skip, status shows that skip's reason. For example, "Architect run idle on JacobStephens2/thirdshift: Ready issue make release.sh watch ci on default if running and start a release when it is done #765 goes first". So you can see why Weeding or Fencing is waiting.

Acceptance criteria

• A live Architect run in its Architecture review appears in status with that stage and its age, named by kind and stamp.
• A Security run moves through Security audit, Security reproduction and Security fix publishing in its record, and any fix it dispatches nests under it.
• A repository whose latest Pickup run or Architect run line is a skip shows that kind as idle, with the reason.
• status --json carries Passes and idle Passes, documented in the README.
• End-to-end tests with the existing fakes, building on the Architect run, Security run and Activity log tests.