Bulchimbeon keeps Macs awake for Claude Code, but fails 3 real tests

Bulchimbeon began from a common nuisance: Macs fall asleep during long AI coding sessions, leaving work unfinished, screens lit all night, or batteries drained. The developer's fix was a pixel-art private in the menu bar who patrols with a flashlight and salutes when the agents finish. Deciding whether an agent is "working" proved harder than expected. The first rule, checking if a Claude Code process is alive, never let the private retire because open windows keep processes running. The final logic instead looks for caffeinate child processes that Claude Code starts only while busy, CPU above 2% over a 60-second average to catch builds and tests, and excludes headless sessions launched with --tools. This logic lives in a pure state machine called DutyEngine with 70 scenario tests covering a quiet five-minute handoff, a battery under 20% retreat, and a heat break with automatic return. Even so, real hardware exposed three blind spots the tests could not: the watchdog vanished with the admin shell because osascript cleaned up its children, saved duty was erased on restart because persist ran before resume, and notifications were silently discarded by macOS for ad-hoc-signed apps. The developer fixed these with a detached perl fork, a synchronized handoff via pipe, a reordered restart sequence, and an osascript fallback that passes text through argv to avoid AppleScript injection.