optimizations

docs/QUEUE.md

@@ -33,6 +33,14 @@ php artisan migrate
 
 We provide an example Supervisor config at `deploy/supervisor/skinbase-queue.conf`.
 
+The example worker listens on the application queues currently used by Skinbase features, including AI and discovery jobs:
+
+```text
+forum-security,forum-moderation,vision,recommendations,discovery,mail,default
+```
+
+If you split workloads across dedicated workers, make sure any queues configured through `VISION_QUEUE`, `RECOMMENDATIONS_QUEUE`, or `DISCOVERY_QUEUE` are explicitly covered by at least one worker process.
+
 To use it on a Debian/Ubuntu server:
 
 ```bash
@@ -100,5 +108,18 @@ php artisan queue:flush
 - Ensure `QUEUE_CONNECTION` in `.env` matches the driver you've configured.
 - If using `database` driver, the `jobs` and `failed_jobs` tables must exist.
 - The mailable used for contact submissions is queued; if the queue worker is not running mails will accumulate in the queue table (or Redis).
+- AI auto-tagging, embedding generation, vector index repair, and recommendation cache regeneration are all queued. If you move them onto dedicated queues, the shipped example worker commands must be updated to consume those queue names.
+
+8) AI and discovery queue checklist
+-----------------------------------
+
+If you are enabling the recommendation AI stack in production, verify all of the following:
+
+- `QUEUE_CONNECTION` is backed by a real worker-capable driver such as `redis` or `database`
+- `VISION_QUEUE`, `RECOMMENDATIONS_QUEUE`, and `DISCOVERY_QUEUE` either stay on `default` or are present in a worker `--queue=` list
+- `UPLOAD_QUEUE_DERIVATIVES=true` has workers online before you enable it, otherwise upload post-processing will stall
+- `php artisan queue:restart` is run after deploys so workers pick up new code and config
+
+See `docs/recommendation-ai-production.md` for a stack-specific runbook.
 
 Questions or prefer a different process manager? Tell me your target host and I can produce exact commands tailored to it.