A background job is one POST, not a platform

You need to transcode a folder of videos. On a jobs platform, that's a function to write in their shape, a deploy step, and an invocation. On Hoody, it's the command you'd have typed, sent as a POST.

POST /api/v1/daemon/quick-start launches the ffmpeg command as an ephemeral program. GET /api/v1/daemon/quick-start/{id}/status tells you it's running. GET /api/v1/daemon/quick-start/{id}/logs shows the output. When the process exits, it's gone: nothing registered, nothing to clean up.

No decorator, no packaging format, no worker framework. The thing you wanted to run is the thing that runs, supervised, with status and logs as URLs.

A background job is one POST, not a platform.