[JacobStephens2]

Summary

The crontab recipes log into a folder per command, and the Pickup run section ends with a whole crontab holding both lines.

 ~/.thirdshift/logs/
-├── architect-cron.log
-└── pickup-cron.log
+└── commands/
+    ├── architect/cron.log
+    └── pickup/cron.log

# cron reads no shell profile: list every directory that holds thirdshift, claude, gh, git and the build tools
PATH=/home/you/.local/bin:/home/you/.cargo/bin:/usr/local/bin:/usr/bin:/bin

# Architect runs, nightly
0 2 * * * cd ~/repos/widgets && thirdshift architect base main >> ~/.thirdshift/logs/commands/architect/cron.log 2>&1

# Pickup runs, every half hour
*/30 * * * * cd ~/repos/widgets && thirdshift pickup base main >> ~/.thirdshift/logs/commands/pickup/cron.log 2>&1

With it: the mkdir -p for both folders, and a warning that a line run together with the comment after it never starts its pass. That is what broke the Pickup runs on tracewake: ... 2>&1# Edit this file is Syntax error: Bad fd number in sh, so cron fired the line every half hour and nothing reached the log.

CONTEXT.md gains Session log and Command log, the terms #259 builds on. Both describe #259's design: stamps in local time, and a Command log per command. Neither is built yet.

Evidence

• Before: README recipes logged to ~/.thirdshift/logs/<kind>-cron.log, one recipe per section, with nothing on joining them or on the glued-line failure.
  After: cargo test --test command_surface: 29 passed. Those tests check that help points to the README recipes without repeating them.

Merge Danger

Door: two-way

Docs only. An existing crontab keeps logging where it did.

Blast Radius: docs

The glossary describes Command logs before #259 builds them.

🤖 Generated with Claude Code