fix(service-cloud): plumb startupTimeout through lazyPlugin wrapper, externalize pg

While verifying the new out-of-band migration path against Neon, three
real bugs surfaced that explained why the prior cf-cold-start fixes
weren't enough:

1. lazyPlugin() wrapper drops startupTimeout
   The control-plane preset wraps every plugin in a lazyPlugin proxy
   so heavy deps load on init() instead of parse-time. The wrapper
   exposed only { name, init, start, stop } — the kernel reads
   plugin.startupTimeout at start time, so even after we set
   ObjectQLPlugin.startupTimeout = 120_000, the wrapper's missing
   property caused the kernel to fall back to its 30s default. Add an
   opt-in startupTimeout argument to lazyPlugin() and pass it through
   for ObjectQL (120s in production, 600s in OS_MIGRATE_AND_EXIT mode
   for latency-disadvantaged operators migrating across regions).

2. service-cloud bundles pg
   tsup was compiling the dynamic import('pg') into a CJS chunk that
   failed at runtime with 'Dynamic require of "events" is not
   supported'. Mark pg / pg-native / pg-cloudflare as external so they
   resolve from node_modules at runtime.

3. service-cloud doesn't declare pg
   pnpm strict isolation means apps/cloud declaring pg doesn't make it
   resolvable from packages/services/service-cloud/dist/index.js. Add
   pg as an optionalDependency on service-cloud so pnpm symlinks it
   into the package's own node_modules.

Verified: pnpm --filter @objectstack/cloud migrate now runs schema
sync against Neon end-to-end and exits 0 (4m26s first run, 3m53s
idempotent second run).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: hotlong

packages/services/service-cloud/package.json

@@ -40,6 +40,9 @@
     "zod": "^4.4.3",
     "@objectstack/service-storage": "workspace:*"
   },
+  "optionalDependencies": {
+    "pg": "^8.20.0"
+  },
   "devDependencies": {
     "@types/node": "^22.19.18",
     "tsup": "^8.5.1",

packages/services/service-cloud/src/control-plane-preset.ts

@@ -28,10 +28,21 @@ export interface ControlPlanePresetConfig {
   authPlugins?: Record<string, unknown>;
 }
 
-/** Create a lazy-proxy plugin that defers its import to init(). */
-function lazyPlugin(name: string, factory: (ctx: any) => Promise<any>): any {
+/**
+ * Create a lazy-proxy plugin that defers its import to init().
+ *
+ * `startupTimeout` is set on the **wrapper** (not the inner plugin) so the
+ * kernel honours it during Phase 2 start. The kernel reads
+ * `plugin.startupTimeout` from the registered plugin object, but the inner
+ * implementation is not constructed until init() — by which time the
+ * registration is already locked in. Without forwarding the budget on the
+ * wrapper, heavy plugins like `ObjectQLPlugin` (which does N×CREATE TABLE
+ * round-trips against a remote DB) inherit the kernel's default 30s and
+ * time out on cold Neon/Turso boots.
+ */
+function lazyPlugin(name: string, factory: (ctx: any) => Promise<any>, opts?: { startupTimeout?: number }): any {
   let impl: any = null;
-  return {
+  const wrapper: any = {
     name,
     async init(ctx: any) {
       impl = await factory(ctx);
@@ -44,6 +55,10 @@ function lazyPlugin(name: string, factory: (ctx: any) => Promise<any>): any {
       if (impl?.stop) await impl.stop(ctx);
     },
   };
+  if (typeof opts?.startupTimeout === 'number' && opts.startupTimeout > 0) {
+    wrapper.startupTimeout = opts.startupTimeout;
+  }
+  return wrapper;
 }
 
 /**
@@ -67,11 +82,20 @@ export function createControlPlanePlugins(cfg: ControlPlanePresetConfig): any[]
 
   return [
     // ── 1. ObjectQL ────────────────────────────────────────────────────────
+    // Migration mode (`OS_MIGRATE_AND_EXIT=1`) gets a 10-minute startup
+    // budget because schema sync from a developer laptop to a remote DB
+    // can be much slower than from a colocated container. Without this,
+    // operators in latency-disadvantaged regions (e.g. Asia → Neon US East
+    // at ~300ms RTT × 30 tables × 2 phases) hit the 120s kernel ceiling
+    // before all DDL completes. Production cold-boot still uses 120s.
     lazyPlugin('com.objectstack.engine.objectql', async () => {
       const { ObjectQLPlugin } = await import('@objectstack/objectql');
       const plugin = new ObjectQLPlugin();
       oqlRef.ql = (plugin as any).ql ?? plugin;
       return plugin;
+    }, {
+      startupTimeout:
+        process.env.OS_MIGRATE_AND_EXIT === '1' ? 600_000 : 120_000,
     }),
 
     // ── 2. Datasource mapping (no heavy deps) ─────────────────────────────

packages/services/service-cloud/tsup.config.ts

@@ -19,5 +19,13 @@ export default defineConfig({
     '@objectstack/plugin-audit',
     '@objectstack/service-tenant',
     '@objectstack/service-package',
+    // Native / CJS-heavy DB drivers that can't survive being bundled
+    // into ESM (they use `require('events')` etc. internally and rely
+    // on Node's actual module graph, not esbuild's). Resolved at runtime
+    // from the host app's node_modules — declared as optional deps so
+    // pnpm makes them available to this package.
+    'pg',
+    'pg-native',
+    'pg-cloudflare',
   ],
 });