fix(idempotency): prevent setInterval leakage across Next.js HMR (#1942)

[neverm1ndthat]

Summary

Fixes Issue #1942: Module-level setInterval in src/lib/backend/idempotency.ts is never cleared

The Bug

The cleanup setInterval was guarded by a module-level let cleanupIntervalId === null check. In Next.js App Router with module hot-reload (HMR), the module scope is recreated on every file change - so cleanupIntervalId would reset to
ull and a brand-new interval would be registered every HMR cycle, while the old ones leaked forever.

The Fix

Replace the module-scoped let binding with a Symbol.for()-keyed reference on globalThis. This persists across HMR boundaries:

s const CLEANUP_INTERVAL_KEY = Symbol.for('commitlabs.idempotency.cleanupInterval'); declare global { var [CLEANUP_INTERVAL_KEY]?: ReturnType<typeof setInterval>; } if (typeof setInterval !== 'undefined' && typeof globalThis[CLEANUP_INTERVAL_KEY] === 'undefined') { globalThis[CLEANUP_INTERVAL_KEY] = setInterval(() => globalStore.cleanup(), 60_000); }

The existing clearCleanupInterval() export is preserved and now correctly reads from the global reference.

[vercel]

@neverm1ndthat is attempting to deploy a commit to the 1nonly's projects Team on Vercel.

A member of the Team first needs to authorize it.