Wake an agent at 3am, retire it at 4

Your nightly job: an agent that scans yesterday's bug reports, clusters duplicates, drafts triage notes. It only needs to exist for about an hour a day.

A hoody-cron entry fires at 3am. It POSTs to hoody-agent's URL with the prompt and the task list. The agent spins up in its own container, reads the reports, writes the notes to a sqlite URL, sends a notification, and exits. The container goes idle. Idle costs nothing.

A second cron at 4am asserts the work is done and tears the container down for good measure. The agent didn't sit running for 23 idle hours. It existed for the work, then stopped existing.

An agent that exists only when there's work for it to do.