Every open bug has a computer attached

A customer reports a bug you can reproduce only with their plugin combination, their locale, and a database in one specific state. You build that environment, reproduce it, and then: because the environment costs money while it exists: you tear it down and write "repro steps" in the ticket. Three weeks later, the engineer assigned rebuilds it from the prose.

On Hoody the reproduction is a container copied from a template, tuned until the bug appears, and linked in the ticket. It stays. Idle, it burns no CPU and shares most of its disk with the base copy-on-write. Two hundred open bugs, two hundred reproductions, one bare metal box. The engineer who picks up the ticket opens the URL and the bug is already happening.