@teamscala/service-boot 0.23.286 → 0.23.288

package/package.json

@@ -6,7 +6,7 @@
   },
   "name": "@teamscala/service-boot",
   "type": "module",
-  "version": "0.23.286",
+  "version": "0.23.288",
   "sideEffects": false,
   "files": [
     "src"
@@ -19,6 +19,7 @@
     "@teamscala/auth": "*",
     "@teamscala/aws": "*",
     "@teamscala/cache": "*",
+    "@teamscala/channel": "*",
     "@teamscala/chat-completion": "*",
     "@teamscala/db": "*",
     "@teamscala/db-validation": "*",
@@ -448,6 +449,14 @@
       "types": "./src/handlers/bun-stable-watch.d.ts",
       "default": "./src/handlers/bun-stable-watch.ts"
     },
+    "./handlers/pane-outbox-drain": {
+      "types": "./src/handlers/pane-outbox-drain.d.ts",
+      "default": "./src/handlers/pane-outbox-drain.ts"
+    },
+    "./handlers/pane-outbox-drain.ts": {
+      "types": "./src/handlers/pane-outbox-drain.d.ts",
+      "default": "./src/handlers/pane-outbox-drain.ts"
+    },
     "./handlers/projects-digest": {
       "types": "./src/handlers/projects-digest.d.ts",
       "default": "./src/handlers/projects-digest.ts"

package/src/handlers/pane-outbox-drain.d.ts

@@ -0,0 +1 @@
+export {};

package/src/handlers/pane-outbox-drain.ts

@@ -0,0 +1,39 @@
+/**
+ * @system server-boot
+ * @status handwritten
+ * @edit edit directly
+ *
+ * The `pane-outbox-drain` pg-boss handler — delivers messages the operator's
+ * WhatsApp PA queues into `pane_messages` to the addressed agent pane.
+ *
+ * WHY THE REGISTRATION LIVES HERE AND THE WORK LIVES IN @teamscala/channel.
+ * The delivery itself belongs to the channel capability, so `paneOutboxDrainTick`
+ * is owned by `@teamscala/channel` beside the dispatch handler it calls. But
+ * `pgBossHandlerRegistry` is SERVER tier and `@teamscala/channel` is ADAPTER
+ * tier, so the channel package cannot register a pg-boss handler without an
+ * upward dependency — forbidden by `vertical-dependency-only`, which has no
+ * carve-out. server → adapter is DOWNWARD, so the registration sits here and
+ * imports the work, exactly as the four sibling handlers in this directory do.
+ *
+ * The MountContext route (`ctx.registerScheduledJob`) is tier-legal but NOT
+ * usable: `start-scheduled-jobs.ts` offers only `long_running` (invoked once,
+ * runs forever) and `recurring` (whose handlers "manage their own setInterval").
+ * Both are the in-process timer that `pg-boss-for-background-work` forbids and
+ * that the timer half of `in-memory-state-is-not-durable` describes — a timer
+ * only fires if its host outlives it, so on a restart-prone service it silently
+ * never runs while logging that it started. pg-boss is the only durable option,
+ * because the job row outlives any worker.
+ *
+ * Scoped to scala-channel by its `scheduled_job` row's `service_slug`, so it
+ * runs on the service that owns the channel rather than on scala-agents, whose
+ * UI-asset build failures used to take PA delivery down with them.
+ *
+ * Registered under slug `@teamscala/service-boot:pane-outbox-drain`.
+ */
+import { paneOutboxDrainTick } from "@teamscala/channel/pane-outbox/drain-tick";
+import { pgBossHandlerRegistry } from "../pg-boss-handler-registry.ts";
+
+pgBossHandlerRegistry.register(
+	"@teamscala/service-boot:pane-outbox-drain",
+	paneOutboxDrainTick,
+);

package/src/pg-boss-mount.d.ts

@@ -20,6 +20,7 @@ import "./handlers/upstream-issue-sync.ts";
 import "./handlers/scheduled-browser-tests.ts";
 import "./handlers/scala-tools-currency-watch.ts";
 import "./handlers/registry-stale-inactive-sweep.ts";
+import "./handlers/pane-outbox-drain.ts";
 export interface PgBossMountContext {
     databaseUrl: string;
     serviceSlug: string;

package/src/pg-boss-mount.ts

@@ -33,6 +33,7 @@ import "./handlers/upstream-issue-sync.ts";
 import "./handlers/scheduled-browser-tests.ts";
 import "./handlers/scala-tools-currency-watch.ts";
 import "./handlers/registry-stale-inactive-sweep.ts";
+import "./handlers/pane-outbox-drain.ts";
 
 export interface PgBossMountContext {
 	databaseUrl: string;
@@ -224,6 +225,28 @@ export async function mountPgBoss(
 					handlerSlug: config.handler_slug,
 				});
 			}
+
+			// A SUCCESSFUL mount emitted nothing until now, while every failure
+			// path above recorded an event — so the one state you most need to
+			// confirm ("is this job actually scheduled on this service?") was the
+			// only one with no evidence. Combined with resolveHandler THROWING
+			// into boss.work() rather than warning, that made "never scheduled"
+			// and "fired and threw" externally identical, and cost a
+			// scheduled_job relocation that had to be reverted undiagnosed on
+			// 2026-07-30. Emitting on success makes the mount set queryable
+			// (event-log-is-the-only-durable-event-log).
+			const mounted = jobs[jobs.length - 1];
+			recordEvent({
+				kind: "pgboss.job.mounted",
+				payload: {
+					service: ctx.serviceSlug,
+					slug: entry.slug,
+					queue: queueName,
+					handler: config.handler_slug,
+					cron: mounted?.cron ?? null,
+					interval_seconds: mounted?.intervalSeconds ?? null,
+				},
+			});
 		} catch (err) {
 			// crash-isolation for the mount path: a work()/schedule() failure
 			// (e.g. DB not open, queue conflict) degrades to "this job unavailable"