feat(db): role-keyed dbFor clients for cleanup and exec workloads

[TheodoreSpeaks]

Summary

• Adds cleanup and exec entries to DB_POOL_PROFILES and a lazy, per-role-cached dbFor('cleanup' | 'exec') factory in @sim/db — sub-process pools selected per call-site, for workloads that live inside an existing process: cleanup jobs run in the trigger.dev worker, inline execution log writes run in the Next.js web server. SIM_DB_ROLE remains restricted to web/trigger/realtime.
• Inert until infra exists: dbFor resolves DATABASE_URL_CLEANUP / DATABASE_URL_EXEC with fallback to the base DATABASE_URL, so today these clients hit the same Postgres with their own local pool. DB_APP_NAME does not leak into them — they always report their profile appName (sim-cleanup / sim-exec). Both are tripwire-instrumented (instrumentPoolClient) with the role as the pool label.
• Cleanup callsites: background/cleanup-logs.ts, cleanup-soft-deletes.ts, and cleanup-tasks.ts run all their queries on dbFor('cleanup'); the lib/cleanup/batch-delete.ts helpers now accept an optional dbClient (default: global db, so other consumers are unchanged). snapshotService.cleanupOrphanedSnapshots (only invoked from cleanup-logs) also moved to the cleanup pool.
• Exec callsites: execution-log persistence in lib/logs/execution/logger.ts (idempotency read, start INSERT, the self-contained completion transaction, getWorkflowExecution), all workflow_execution_logs writes in logging-session.ts (progress-marker fallback UPDATEs, status reads, markExecutionAsFailed), and the workflow-state snapshot upsert in snapshot/service.ts run on dbFor('exec'). Billing/usage-ledger work (advisory-lock reconcile transaction, subscription/org lookups, PII-settings read) deliberately stays on the default client.
• Test infra: databaseMock / dbChainMock in @sim/testing expose dbFor returning the shared mock instance; local @sim/db mocks in the touched suites updated the same way.

Type of Change

• New feature

Testing

• packages/db: tsc --noEmit clean; vitest 24/24 (tx-tripwire + connection-url).
• apps/sim: tsc --noEmit — no new errors (one pre-existing error in providers/meta/index.ts exists on clean origin/staging).
• vitest: cleanup suites, lib/logs/execution/** (191 tests), plus every other suite that locally mocks @sim/db and transitively imports the touched modules (66 tests) — all passing.
• bun run lint:check and bun run check:api-validation:strict pass.

Checklist

• I have signed the CLA

🤖 Generated with Claude Code

https://claude.ai/code/session_01NNy9Fzpfc1FdHAzYyb6Ycy

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 22, 2026 12:08am

[cursor]

PR Summary

Medium Risk
Changes which connection pool backs high-volume cleanup and execution-log writes; behavior is unchanged when dedicated URLs are unset, but misconfigured pools could affect Postgres load or timeouts.

Overview
Introduces dbFor('cleanup' | 'exec') in @sim/db: lazy, cached Drizzle clients with their own pool sizes and Postgres application_name (sim-cleanup / sim-exec). SIM_DB_ROLE is limited to process roles (web, trigger, realtime); sub-pools are chosen per call site. Optional DATABASE_URL_CLEANUP and DATABASE_URL_EXEC fall back to the process URL until infra wires dedicated endpoints.

Cleanup background jobs and helpers (batch-delete, chat file collection, large-value prune/mark-deleted, orphaned snapshot cleanup) route reads/deletes through dbFor('cleanup'). Storage billing transactions that delete billable workspace files still use the default db.

Execution logging (workflow_execution_logs, progress markers, completion transaction, snapshot upsert/read) uses dbFor('exec'); billing/usage-ledger work remains on the global client. Tests and @sim/testing mocks expose dbFor returning the shared mock db.

^{Reviewed by Cursor Bugbot for commit 165a7bb. Bugbot is set up for automated code reviews on this repo. Configure here.}

[TheodoreSpeaks]

@greptile review

[greptile-apps]

Greptile Summary

This PR adds role-keyed database clients for cleanup and execution-log workloads. The main changes are:

• New cleanup and exec pool profiles in @sim/db.
• A lazy dbFor('cleanup' | 'exec') client factory.
• Cleanup jobs routed through the cleanup pool.
• Execution-log and snapshot persistence routed through the exec pool.
• Test database mocks updated to expose dbFor.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
packages/db/db.ts	Adds the role-specific pool profiles and the cached dbFor factory.
apps/sim/background/cleanup-logs.ts	Routes log cleanup queries and large-value metadata cleanup through the cleanup client.
apps/sim/background/cleanup-soft-deletes.ts	Routes soft-delete cleanup queries through the cleanup client while preserving the billing transaction boundary.
apps/sim/background/cleanup-tasks.ts	Routes task and chat cleanup work through the cleanup client.
apps/sim/lib/cleanup/batch-delete.ts	Adds optional database-client injection for cleanup delete helpers.
apps/sim/lib/cleanup/chat-cleanup.ts	Moves chat file collection reads onto the cleanup client.
apps/sim/lib/execution/payloads/large-value-metadata.ts	Adds optional database-client injection for large-value tombstone and metadata pruning.
apps/sim/lib/logs/execution/logger.ts	Routes execution-log persistence through the exec client while keeping billing work on the default client.
apps/sim/lib/logs/execution/logging-session.ts	Routes execution progress, status, and failure writes through the exec client.
apps/sim/lib/logs/execution/snapshot/service.ts	Routes snapshot writes and reads through the exec client and orphan cleanup through the cleanup client.

_{Reviews (6): Last reviewed commit: "feat(db): log which connection each dbFo..." | Re-trigger Greptile}

[greptile-apps]

Greptile Summary

This PR adds workload-specific database clients for cleanup and execution logging. The main changes are:

• Adds cleanup and exec pool profiles plus a cached dbFor factory.
• Routes cleanup jobs through the cleanup client.
• Routes execution-log persistence and snapshot writes through the exec client.
• Lets batch-delete helpers accept an explicit database client.
• Updates env validation and database mocks for the new keyed clients.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• The changed cleanup paths consistently use the cleanup client.
• The changed execution-log paths consistently use the exec client where intended.
• The new database factory is cached per role and keeps process-role validation separate from workload clients.

Important Files Changed

Filename	Overview
packages/db/db.ts	Adds cleanup and exec pool profiles, keeps process roles restricted, and exposes a cached dbFor factory.
apps/sim/lib/cleanup/batch-delete.ts	Adds an optional client parameter to cleanup delete helpers while preserving the existing default client.
apps/sim/background/cleanup-logs.ts	Moves cleanup log queries and delete helpers to the cleanup client.
apps/sim/background/cleanup-soft-deletes.ts	Moves soft-delete cleanup selects and deletes to the cleanup client.
apps/sim/background/cleanup-tasks.ts	Moves task cleanup queries and deletes to the cleanup client.
apps/sim/lib/logs/execution/logger.ts	Moves execution-log persistence to the exec client while keeping billing work on the default client.
apps/sim/lib/logs/execution/logging-session.ts	Moves progress markers, status reads, and failure writes to the exec client.
apps/sim/lib/logs/execution/snapshot/service.ts	Moves snapshot upserts to the exec client and orphan cleanup to the cleanup client.
apps/sim/lib/core/config/env.ts	Adds optional keyed database URLs for cleanup and exec pools.
packages/testing/src/mocks/database.mock.ts	Extends shared database mocks so dbFor returns the same mock instance as db.

_{Reviews (2): Last reviewed commit: "feat(db): role-keyed dbFor clients for c..." | Re-trigger Greptile}

[TheodoreSpeaks]

@greptile review

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c7ac96b. Configure here.}

[TheodoreSpeaks]

@greptile review

[TheodoreSpeaks]

@greptile review

[TheodoreSpeaks]

@greptile review