Problem
The repository's documented make entry points still describe Gobbler's background worker as Redis/RQ-based even though the supported queue is SQLite-backed. make help currently prints:
make start - Start everything (Docker services + RQ worker)
make worker - Start RQ worker for background tasks
make worker-stop - Stop running RQ workers
The corresponding targets also maintain a private .worker.pid/nohup lifecycle instead of delegating to the public gobbler jobs worker commands used by the README and documentation.
Expected behavior
Make targets should describe the SQLite job worker accurately and delegate worker lifecycle operations to the supported CLI (gobbler jobs worker start/status/stop).
Actual behavior and impact
The stale RQ wording contradicts the installation and queue documentation and can lead maintainers or users to look for Redis/RQ services that Gobbler no longer requires. The separate PID-file implementation also creates a second worker lifecycle surface whose status and cleanup behavior can diverge from gobbler jobs worker.
Scoped root cause
The queue implementation and public documentation migrated to SQLite-backed jobs, but the Makefile help text, comments, and worker recipes retained the previous RQ-era terminology and process management.
Scope
- Update the Makefile's worker-related help, comments, and recipes to use the supported SQLite worker CLI.
- Add a static regression covering the public Makefile worker contract.
- Synchronize patch-version and changelog metadata for the fix.
Non-goals
- Queue schema, claiming, execution, or persistence changes.
- Changes to the
gobbler jobs worker CLI itself.
- Docker service lifecycle redesign.
- New worker features or deployment mechanisms.
Acceptance criteria
make help contains no Redis/RQ worker claims and identifies the SQLite-backed job worker.make start, make worker, and make worker-stop delegate to supported gobbler jobs worker commands rather than private PID-file or pkill logic.- A regression test fails if RQ-era worker text/process management returns.
- Unit tests, Ruff, strict docs, and Makefile smoke checks pass.
Problem
The repository's documented
makeentry points still describe Gobbler's background worker as Redis/RQ-based even though the supported queue is SQLite-backed.make helpcurrently prints:The corresponding targets also maintain a private
.worker.pid/nohuplifecycle instead of delegating to the publicgobbler jobs workercommands used by the README and documentation.Expected behavior
Make targets should describe the SQLite job worker accurately and delegate worker lifecycle operations to the supported CLI (
gobbler jobs worker start/status/stop).Actual behavior and impact
The stale RQ wording contradicts the installation and queue documentation and can lead maintainers or users to look for Redis/RQ services that Gobbler no longer requires. The separate PID-file implementation also creates a second worker lifecycle surface whose status and cleanup behavior can diverge from
gobbler jobs worker.Scoped root cause
The queue implementation and public documentation migrated to SQLite-backed jobs, but the Makefile help text, comments, and worker recipes retained the previous RQ-era terminology and process management.
Scope
Non-goals
gobbler jobs workerCLI itself.Acceptance criteria
make helpcontains no Redis/RQ worker claims and identifies the SQLite-backed job worker.make start,make worker, andmake worker-stopdelegate to supportedgobbler jobs workercommands rather than private PID-file orpkilllogic.