[JacobStephens2]

Summary

Adds the CLI for seeing, following and stopping this machine's Commands across every repository in logs.dir.

Command log + atomic Command record
  Pass → dispatched Run / Spec run → Ticket Runs → Base fixes
  status → live stages, age, recent outcomes, history and idle Passes
  show   → full tree, Session logs and latest events
  logs   → raw Command / Session logs, optionally followed
  stop   → SIGTERM → existing cleanup → triage or --requeue

Records retain process start identity, Harness, Model, Effort, stage history, Ticket blockers and outcomes. History falls back to Activity logs and then current-layout Session logs. README documents the version 1 status/show JSON. Stop refuses ended Commands and individual Ticket Runs, records who requested it, and waits for cleanup.

Closes #711

Evidence

• Before: main has no machine status, show, logs or Stop commands; operators find processes and logs manually.
  After: binary integration tests exercise live Runs, nested Pickup/Spec/Ticket trees, idle Passes, historical recovery, naming, Session selection, log following, and Stop labels and cleanup.
• Before the review fix: stop widgets#20 preserved unfinished Ticket work on origin/issue-21 but printed only Issue branch left: issue-20. The reviewer’s stop_reports_retained_ticket_branches reproduction failed (exit 101).
  After: the identical reproduction passed (exit 0). Stop reuses status's tree reader to report retained branches and pull requests recursively, including Ticket Runs and Base fixes. The regression remains in tests/stop.rs.
• Standards review also consolidated Command stamp parsing used by history, naming and Session lookup.
• Passing local Linux checks: full cargo test; cargo fmt --check; cargo clippy --all-targets -- -D warnings; cargo test --test stop --test status --test show_logs (39 tests); cargo test --bin thirdshift logs:: (24 tests). The full run began during review; the focused checks ran after the corrections in b958ff6.

Test seams: the thirdshift binary against real Git and fake GitHub/Harnesses; the existing recorder effects seam for write failure, concurrency and process identity; the existing in-memory Claim seam for Stop endings. The Stop regression observes CLI output and retained work on fake origin.

Unaddressed findings

• Standards: none. The P3 possible Duplicated Code finding was addressed and its correction reviewed.
• Spec: none. The P2 omitted child-resource finding was reproduced, fixed and its correction reviewed.
• Security: none identified. Single-session guidance review of the pinned diff f3133466986c6dd465939ddf190a643b212f06c6...HEAD and supporting code covered Stop process identity and signaling, record and Stop-request files, log paths, interruption and Claim cleanup, and Session-tail parsing. All 39 CLI tests in stop, status and show_logs, plus 24 logs:: unit tests, passed across isolated offline Linux runs; one CLI fixture needed the installed Node binary added to the sandbox before its successful rerun. macOS received source review only, including comparison with Apple’s process identity declarations and signal wrapper.

Review coverage: both independent reviewers read all 36 changed files, including supporting standards and ADRs, and reread all five files changed by the corrections. Unread changed files: none. Intentionally unread generated output: none. Both reports include their final files-read lists.

Security review outcome

No unaddressed introduced findings.

Merge Danger

Door: two-way

The binary can be rolled back; retained Command records and logs stay on disk. A Stop already requested has lasting effects on the running Command and its issue labels.

Blast Radius: machine

Status spans configured repositories. Stop targets one verified Command process and its existing interruption tree; changes also touch shared recording, Claim ending and Run/Spec Delivery transitions.

Built with codex · gpt-6.1-sol · high

Tickets

• The Command record, and thirdshift status for a live Run #768 landed with Record live Runs and add machine-wide status #777
• Child Runs and Spec runs in the Command record #769 landed with Record child Runs and Spec runs in Command status #781
• Passes in the Command record, and idle Passes in status #770 landed with Record Passes and show idle Passes in status #779
• History in thirdshift status #771 landed with Show recent and historical Commands in status #780
• thirdshift show and thirdshift logs, and naming a Command #772 landed with Add show and logs for named Commands #782
• thirdshift stop for a Run #773 landed with Add thirdshift stop for live Runs #783
• Stop for Spec runs, Pickup runs and Passes #774 landed with Stop for Spec runs, Pickup runs and Passes #784