Document worker logging scenarios for POSIX shells and PowerShell

[highbyte]

Documentation gap

The worker documentation explains stdout/stderr, color behavior, and durable redirection, but the examples in docs/reference/worker.md are POSIX-shell-specific. Wrighty also supports Windows, where PowerShell uses different syntax for redirection, background execution, and teeing output.

This can leave operators unsure how to retain unattended-worker logs or show output in the terminal while also writing it to a file.

Suggested documentation

Add a concise Common logging scenarios subsection under Terminal color and machine output, with tested examples for POSIX shells and PowerShell covering:

• terminal output only;
• terminal output plus an appended combined log (tee / Tee-Object);
• background execution with durable logs;
• NDJSON stdout with stderr stored separately;
• preserving the Wrighty exit code when output passes through a tee pipeline;
• service-managed logging, where the process manager owns capture and retention.

Also clarify that:

• Wrighty does not create, rotate, or retain conventional log files itself;
• worker lifecycle events and heartbeats—including warning- and danger-classified lifecycle events such as needs-attention, failed, and timed-out—go to stdout, while separate CLI safety and diagnostic warnings and command errors go to stderr;
• combining the streams loses that distinction;
• --color never is recommended for durable human-readable logs;
• Wrighty intentionally does not log the agent transcript, model reasoning, or tool calls.

Non-goals

• Adding a --log-file option or changing worker logging behavior.
• Implementing log rotation or retention.
• Providing complete launchd, systemd, or Windows service installation guides.