docs(jobs): name the binding contract the registrars actually use

This commit is contained in:
Marc-André Bombeck committed 2026-07-27 23:29:20 +02:00
1 parent ae294573ef
commit 1f47db5955
2 files changed
+3 -3

No files matched your search

+1 -1
View File
@@ -2,7 +2,7 @@
* v1.4.25 W16c — Enqueue helper + handler glue for the pg-boss
* `pr-detection` queue. Lives in `src/lib/jobs/` next to the other
* job-side helpers; the worker process binds the handler in
* `reminder-worker.ts` via `boss.work(PR_DETECTION_QUEUE, ...)`.
* the maintenance registrar via `createAndWork(boss, PR_DETECTION_QUEUE, …)`.
*
* The Next.js side (ingest routes) imports `enqueuePrDetection` and
* never touches pg-boss directly — `getGlobalBoss()` returns the
+2 -2
View File
@@ -8,8 +8,8 @@
* the domain registrars under `src/lib/jobs/reminder/`. Each registrar owns the
* four facts the v1.4.37 dead-queue guards pin — the queue-name constant, its
* `allQueues` membership, its `[QUEUE, CRON]` schedule tuple, and its
* `boss.work(QUEUE, …, handler)` binding — so a queue can never be declared
* without being provisioned, scheduled, and drained.
* `createAndWork(boss, QUEUE, …, handler)` binding — so a queue can never be
* declared without being provisioned, scheduled, and drained.
*
* Usage: Run as a standalone process or call startReminderWorker() from a
* custom server setup. In dev, use: npx tsx src/lib/jobs/reminder-worker.ts