chore: dev worker queues match supervisord

Merged
EV
3d ago
+10-10

Description

The light and heavy Celery workers in the dev launch configs (.vscode/launch.json, .zed/debug.json, .zed/tasks.json, .zed/process-compose.k8s.yaml) are missing queues that backend/supervisord.conf runs:

  • light: chat_ttl_deletion, capability_checks_draft
  • heavy: connector_hierarchy_fetching, capability_checks

A dev stack started from these configs, including ods stack up, never runs connector checks: draft runs on the create form stay queued. It also skips chat TTL deletion and hierarchy fetching. This PR adds the queues so the lists match supervisord.

How Has This Been Tested?

Started a stack with ods stack up --profile full and read each worker's [queues] banner in its log. Before the change, the light worker had no capability_checks_draft and the heavy worker had no capability_checks.

Additional Options

  • [Optional] Please cherry-pick this PR to the latest release version.
  • [Optional] Override Linear Check

🤖 Generated with Claude Code

Summary by cubic

Aligns the Celery worker queue lists in the dev launch configs (.vscode/launch.json, .zed/debug.json, .zed/tasks.json, .zed/process-compose.k8s.yaml) with backend/supervisord.conf, so dev stacks started from these configs (including ods stack up) now run connector checks, chat TTL deletion, and hierarchy fetching that were previously skipped.

  • Adds chat_ttl_deletion and capability_checks_draft to the light worker queue list.
  • Adds connector_hierarchy_fetching and capability_checks to the heavy worker queue list.

Summary by CodeRabbit

  • New Features
    • Background processing now supports chat expiration, draft capability checks, full capability checks, and connector hierarchy retrieval. These tasks can be handled by the appropriate lightweight or heavyweight workers, improving support for workflows that rely on them.