@teamscala/service-boot 0.23.285 → 0.23.287

package/package.json

@@ -6,7 +6,7 @@
   },
   "name": "@teamscala/service-boot",
   "type": "module",
-  "version": "0.23.285",
+  "version": "0.23.287",
   "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;

package/src/two-phase-boot.ts

@@ -398,9 +398,11 @@ export async function buildFullApp(
 
 	// Client asset building (expensive: Vite build)
 	await buildClientAssets(serviceSlug);
+	log.info(`[two-phase-boot:${serviceSlug}] phase-2 step: buildClientAssets DONE`);
 
 	// Scheduled jobs
 	startScheduledJobs(config, mountRegistry, serviceSlug);
+	log.info(`[two-phase-boot:${serviceSlug}] phase-2 step: scheduledJobs DONE`);
 
 	// pg-boss (mount for UI services - wasn't mounted in minimal app)
 	const { jobs: pgBossJobs } = await mountPgBoss({
@@ -408,6 +410,7 @@ export async function buildFullApp(
 		serviceSlug,
 		packages: config.server_packages ?? [],
 	});
+	log.info(`[two-phase-boot:${serviceSlug}] phase-2 step: mountPgBoss DONE (${pgBossJobs.length} jobs)`);
 	if (pgBossJobs.length > 0) {
 		log.info(
 			`[two-phase-boot:${serviceSlug}] pg-boss mounted ${pgBossJobs.length} job(s): ${pgBossJobs.map((j) => j.handlerSlug).join(", ")}`,

package/src/ui-service.ts

@@ -103,7 +103,16 @@ export async function bootUiService(
 	// Phase 2: Build full app in background (non-blocking)
 	;(async () => {
 		try {
-			const fullAppResult = await buildFullApp(minimalAppResult, deps);
+			const PHASE2_TIMEOUT_MS = 120_000;
+			const fullAppResult = await Promise.race([
+				buildFullApp(minimalAppResult, deps),
+				new Promise<never>((_, reject) =>
+					setTimeout(
+						() => reject(new Error(`buildFullApp timed out after ${PHASE2_TIMEOUT_MS / 1000}s — phase 2 hung silently, see step logs`)),
+						PHASE2_TIMEOUT_MS,
+					),
+				),
+			]);
 			const fullBuildTime = Date.now();
 			const fullDuration = fullBuildTime - startTime;