Everything That Broke on Day Two

AI agents don't tell you when they're broken. They exit clean, report success, produce nothing. The first real task went fine. The second one hung for 30 minutes and produced nothing. Day one was the build — ports and adapters, Telegram bot, task queue, CLI worker, all wired up and running on PM2 by midnight. ([Post 1] covers the full 16-hour sprint from empty directory to working product.) Day two was when real tasks hit real repos. "Working on the happy path" turned out to be a generous definition of "working." Six bugs shipped with v0.1. In the order we found them. Bug 1: Zero Stdout First production task ran seven minutes, then got killed by the timeout. Task log showed nothing. stdoutTail: "" . The CLI was running, doing work inside its sandbox, writing zero bytes to stdout. Checked if --output-format json was writing to stderr. Checked if FORCE_COLOR: '0' was suppressing output. Checked TTY buffering. None of it. Root cause: HOME . We spawn the CLI as a sandboxed user, but the en