Stop hoody-terminal in production with one POST

A compliance audit lands on Tuesday. The auditors want proof that nobody can shell into production containers during the review window. The naive answer is to ssh in and disable the terminal service: except hoody-terminal is how you'd ssh in, and disabling it from outside is somebody else's policy problem.

The Hoody Daemon manages every Hoody Kit service. hoody-terminal, hoody-display, hoody-code, hoody-files: they're all daemon programs you can list, stop, disable. You POST disable on hoody-terminal across all production containers. Shell access goes dark. The audit log shows the disable timestamp. Re-enable on Friday with another POST.

This is the meta-capability nobody anticipates: the Kit manages itself. Need to harden? Stop the surfaces you don't need. Need to debug? Re-enable the ones you do.