feat: show startup logs on successful daemon start

[jdx]

Summary

Display daemon logs briefly after successful start/run commands, providing visibility into daemon initialization.

Currently logs are only shown when a daemon fails to start. This change shows startup logs on success too, giving users visibility into whether the daemon initialized properly.

Changes

• Add print_startup_logs() function to logs.rs (similar to existing print_logs_for_time_range() but with "Startup logs" header)
• Add --quiet / -q flag to both start and run commands to suppress startup logs
• Print startup logs after successful daemon start (unless --quiet)

Example Output

=== Startup logs ===
2024-01-15 10:30:45 Server listening on port 3000
2024-01-15 10:30:45 Connected to database
=== End of logs ===

Test plan

• pitchfork start <daemon> - Should show startup logs
• pitchfork start <daemon> --quiet - Should be silent on success
• pitchfork run <daemon> -- <cmd> - Should show startup logs
• pitchfork run <daemon> --quiet -- <cmd> - Should be silent
• Verify failure case still shows error logs regardless of quiet flag

Resolves #104

🤖 Generated with Claude Code

---

Note

Shows recent daemon logs after successful startup for visibility, with an option to suppress.

• New print_startup_logs() in logs.rs; invoked by start and run after success (captures start time per daemon)
• Adds -q --quiet flag to start and run to suppress startup log output
• Updates CLI usage/docs (commands.json, start.md, run.md, pitchfork.usage.kdl) including backticked [daemons.<name>], logs --clear (all daemons), and list help text
• Adds /docs/.vitepress/dist to .gitignore

^{Written by Cursor Bugbot for commit b9197ca. This will update automatically on new commits. Configure here.}