Reconcile the production fork with upstream useSend v1.9.7

[vladbisceanu]

Delivers: a controlled reconciliation of growthpath-mail with upstream useSend v1.9.7 while preserving GrowthPath-specific security, bootstrap, and Railway runtime work.

Done when: the complete upstream diff and Prisma migrations are reviewed; the local BullMQ connection patch that upstream now contains is removed rather than duplicated; focused tests and the full relevant build pass; a fresh recoverable Postgres backup is verified before deployment; and the exact live merge SHA plus /api/health are proven after deployment.

Keep main as the upstream mirror. Perform the reconciliation on a feature branch targeting growthpath-mail, and record which local commits remain intentionally carried.

[vladbisceanu]

Reconciliation review started from current growthpath-mail (0e2d8d04d0637e32f10275d36490cdfc4f0d8d1f).

Upstream v1.9.7 is exactly one commit beyond the fork's main mirror: d7b95aa5c8a7584b103eb35a48238c489baa79dd (fix: use BullMQ-safe campaign batch job IDs (#446)). The complete delta is two files: the already-carried one-line job-ID correction plus 33 lines of focused unit-test coverage. There are no Prisma migration changes.

The reconciliation will merge the tagged upstream commit into a feature branch targeting growthpath-mail. Git ancestry will record v1.9.7; the local equivalent implementation will not be applied a second time, while upstream's missing regression test will be retained. The production-hardening, bootstrap, and Railway commits remain intentionally carried.

Before production merge I will create and verify a fresh named Postgres backup. The required Production gate, exact-SHA Railway deployment, and SHA-bearing health endpoint provide the remaining release proof.

[vladbisceanu]

Reconciled and proven in production.

• upstream mirror: main now points to v1.9.7 commit d7b95aa5c8a7584b103eb35a48238c489baa79dd
• PR: chore: reconcile upstream v1.9.7 #11
• reviewed PR head: 977d835a0ad987f43c888f580a7eadd329daba62
• production merge commit: d1e6e5ad1d7550a11e768562174d66cd443f999d
• required PR gate: run 32965252291 — success, including the production image build
• protected-branch gate: run 32965740462 — success on the exact merge commit
• locked pre-release backup: pre-v1.9.7 / e33e5854-5d90-4de8-9ce5-0e9875cd8568, created 2026-08-26T11:47:20.716Z, no expiry; PITR enabled, bucket wired, live recovery available
• Railway deployment: da018f72-d312-44d7-9a76-ddacc5af2d04 — SUCCESS for the exact merge commit
• migration log: 41 migrations found, no pending migrations
• public readiness proof: GET https://send.growthpath.systems/api/health returned HTTP 200 with {"data":"Healthy","commitSha":"d1e6e5ad1d7550a11e768562174d66cd443f999d"}

The complete upstream delta and migration surface were reviewed. There were no Prisma changes. The campaign implementation and regression test now match v1.9.7 exactly; the equivalent local BullMQ change remains only as immutable historical ancestry and contributes no separate tree delta. GrowthPath's SNS, AGPL, Railway/runtime, bootstrap, service-ownership, and production-hardening commits remain intentionally carried.