The dev environment that tracks production like a branch

The local copy of production is always a lie: a compose-file approximation, a seed script, a README that says "roughly matches prod." On Hoody you copy the production container once: full filesystem, packages, configuration, data. That copy is your debugging environment. When prod drifts: a hotfix, a schema change, new data shapes: you don't rebuild. You POST a sync, and only the changes move; ten seconds to a few minutes later the twin matches again, keeping its own container ID, URLs, and settings.

Reproducing a production bug stops being an act of reconstruction. You sync, you reproduce, you fix: on production's diff-for-diff sibling, not its artist's impression. And a standing twin costs nothing worth counting while it idles.