[JacobStephens2]

Summary

status
  Command records
  fill missing Commands from Activity logs + Command logs
  fill remaining history from grouped Session logs
  show live Commands, then completions from the last 24 hours
status --all
  show all Commands, newest first

Closes #771

Evidence

Seams under test: the thirdshift binary's status text and versioned JSON, driven with fixture logs and real Commands using the existing external-tool fakes (#711's testing decision).

• Before: recent-history fixture returned 0 Commands instead of 1; Activity recovery returned 0 instead of 3; Session fallback returned 2 instead of 4. The Spec review's exact reproducers also failed for pre-Harness Activity starts and overlapping failed Commands.
  After: all 15 binary status tests pass, including retained regressions for both Spec findings. Both exact reviewer reproducers now exit 0. cargo fmt --check and cargo clippy --all-targets -- -D warnings pass. Full cargo test: 1,887 passed, 2 existing tests ignored, across all 46 test binaries.

Both review axes verified their fixes: one Standards duplication judgement and two Spec behavior findings addressed.

Unaddressed findings

• Standards: none.
• Spec: none.

Review coverage: both axes read every one of the 19 changed files against the captured issue-711 fixed point (f313346), including all files in this PR's smaller diff against the current server branch. Unread changed files: none. Generated-output exclusions: none.

Merge Danger

Door: two-way

Blast Radius: status

Adds an optional completion time to retained Command records and extends the status JSON with history provenance.

Built with codex · gpt-6.1-sol · high