backend-manager 5.0.91 → 5.0.92

package/CHANGELOG.md

@@ -33,7 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 - Payment schemas for webhook and intent validation.
 - `payment.processors` config section for Stripe, PayPal, Chargebee, and Coinbase configuration.
 - `npx bm stripe` CLI command for standalone Stripe webhook forwarding.
-- Auto-start Stripe CLI webhook forwarding with `npx bm emulators` (gracefully skips when prerequisites are missing).
+- Auto-start Stripe CLI webhook forwarding with `npx bm emulator` (gracefully skips when prerequisites are missing).
 - `Manager.version` property exposing the BEM package version.
 - Journey test accounts for payment lifecycle testing (upgrade, cancel, suspend, trial).
 - Stripe fixture data for subscription states (active, trialing, canceled).
@@ -57,7 +57,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 - Firestore security rules testing support.
 - HTTP client with auth helpers (`http.as('admin').command()`).
 - Rich assertion library (`isSuccess`, `isError`, `hasProperty`, etc.).
-- New `bm emulators` command for standalone emulator management.
+- New `bm emulator` command for standalone emulator management.
 - Enhanced `bm test` with path filtering and parallel test support.
 
 ### Changed

package/CLAUDE.md

@@ -414,10 +414,10 @@ Manager.handlers.bm_api = function (mod, position) {
 ### Running Tests
 ```bash
 # Option 1: Two terminals
-npx bm emulators  # Terminal 1 - keeps emulators running
-npx bm test       # Terminal 2 - runs tests
+npx bm emulator  # Terminal 1 - keeps emulator running
+npx bm test      # Terminal 2 - runs tests
 
-# Option 2: Single command (auto-starts emulators)
+# Option 2: Single command (auto-starts emulator)
 npx bm test
 ```
 
@@ -519,7 +519,7 @@ assert.fail(message)                           // Explicit fail
 
 ## Stripe Webhook Forwarding
 
-BEM auto-starts Stripe CLI webhook forwarding when running `npx bm serve` or `npx bm emulators`. This forwards Stripe test webhooks to the local server so the full payment pipeline works end-to-end during development.
+BEM auto-starts Stripe CLI webhook forwarding when running `npx bm serve` or `npx bm emulator`. This forwards Stripe test webhooks to the local server so the full payment pipeline works end-to-end during development.
 
 **Requirements:**
 - `STRIPE_SECRET_KEY` set in `functions/.env`
@@ -830,14 +830,22 @@ The `test` processor generates Stripe-shaped data and auto-fires webhooks to the
 | Middleware pipeline | `src/manager/helpers/middleware.js` |
 | Schema validation | `src/manager/helpers/settings.js` |
 | Rate limiting | `src/manager/helpers/usage.js` |
-| User properties | `src/manager/helpers/user.js` |
+| User properties + schema | `src/manager/helpers/user.js` |
 | Batch utilities | `src/manager/helpers/utilities.js` |
 | Main API handler | `src/manager/functions/core/actions/api.js` |
 | Config template | `templates/backend-manager-config.json` |
 | CLI entry | `src/cli/index.js` |
 | Stripe webhook forwarding | `src/cli/commands/stripe.js` |
+| Intent creation | `src/manager/routes/payments/intent/post.js` |
+| Webhook ingestion | `src/manager/routes/payments/webhook/post.js` |
+| Webhook processing (on-write) | `src/manager/events/firestore/payments-webhooks/on-write.js` |
+| Payment analytics | `src/manager/events/firestore/payments-webhooks/analytics.js` |
+| Transition detection | `src/manager/events/firestore/payments-webhooks/transitions/index.js` |
 | Payment processor libraries | `src/manager/libraries/payment-processors/` |
-| Payment transition handlers | `src/manager/events/firestore/payments-webhooks/transitions/` |
+| Stripe library | `src/manager/libraries/payment-processors/stripe.js` |
+| Price ID resolver | `src/manager/libraries/payment-processors/resolve-price-id.js` |
+| Order ID generator | `src/manager/libraries/payment-processors/order-id.js` |
+| Test accounts | `src/test/test-accounts.js` |
 
 ## Environment Detection
 

package/README.md

@@ -733,7 +733,7 @@ npx backend-manager <command>
 | `bem serve` | Start local Firebase emulator |
 | `bem deploy` | Deploy functions to Firebase |
 | `bem test [paths...]` | Run integration tests |
-| `bem emulators` | Start Firebase emulators (keep-alive mode) |
+| `bem emulator` | Start Firebase emulator (keep-alive mode) |
 | `bem stripe` | Start Stripe CLI webhook forwarding to local server |
 | `bem version`, `bem v` | Show BEM version |
 | `bem clear` | Clear cache and temp files |
@@ -749,7 +749,7 @@ Set these in your `functions/.env` file:
 | Variable | Description |
 |----------|-------------|
 | `BACKEND_MANAGER_KEY` | Admin authentication key |
-| `STRIPE_SECRET_KEY` | Stripe secret key (enables auto webhook forwarding in `serve`/`emulators`) |
+| `STRIPE_SECRET_KEY` | Stripe secret key (enables auto webhook forwarding in `serve`/`emulator`) |
 
 ## Response Headers
 
@@ -761,16 +761,16 @@ bm-properties: {"code":200,"tag":"functionName/executionId","usage":{...},"schem
 
 ## Testing
 
-BEM includes an integration test framework that runs against Firebase emulators.
+BEM includes an integration test framework that runs against the Firebase emulator.
 
 ### Running Tests
 
 ```bash
 # Option 1: Two terminals (recommended for development)
-npx bm emulators  # Terminal 1 - keeps emulators running
-npx bm test       # Terminal 2 - runs tests
+npx bm emulator  # Terminal 1 - keeps emulator running
+npx bm test      # Terminal 2 - runs tests
 
-# Option 2: Single command (auto-starts emulators, shuts down after)
+# Option 2: Single command (auto-starts emulator, shuts down after)
 npx bm test
 ```
 

package/TODO-MARKETING.md

@@ -0,0 +1,3 @@
+1. Determine name via AI on signup
+2. Add to sendgrid marketig cotacts
+3. then, develop a way to SYNC them to the marketing contacts. we coould sync on payment changes (liek newly subscribed, cancelled, etc) so we can segment them??

package/TODO-PAYMENT-v2.md

@@ -0,0 +1,71 @@
+TODO payments
+
+would it be beneficial to... check the time on the event and the time in our datbase and skip if the time in oour database is nwer than the vent, indicatig that it is stale? or is this redundatn since we fetch the latest resource anyway?
+
+next, we need to do certain things based on the CHANGE thats happening to the resource (subscription or one time) that is different that simply updating the user doc and the payments-subscriptions or payments-one-time collection. For example:
+  * if a new subscription is created, we send a welcome email and grant access to the product (but this cant happen when a user fixes their payment method from a failed payment, only when a new subscription is created)
+  * if a subscription is cancelled, we send a cancellation email
+  * if a subscription payment fails, we send a paymetn failed "please update your payment method" email
+  * if a subscription payment succeeds after previously failing, we send a "payment successful, your access has been restored" email
+
+more endpoints to build
+payments/cancel
+  * takes a subscrition id and requests to cancel at the end of the billing period (not immediately). this can only be done if the user has an non cancelled subscription.
+  * there should be an accompanying frontend form that asks some outboardig quetsions
+    * Why are you cancelling (checkboxes + textbox) with randomzed order of the checkboes
+  * after doing this, users should still be able to reactivate it
+payments/manage
+  * fetches the customer portal link from the payment processor and redirects the user there
+  * acessible from the user's account page in biling setion
+  * only accessible if the user has a non cancelled subscription
+
+Note: * for managing and cancelling, they should be under a sinlge button/dropdown called "manage subscription".
+  * it could have links to the 2 pages as items in the dropdown, or we could take them to a dedicated page (or expand an accordian) that has more information about managing it
+  * we need to make it hard to cancel, buried in some info, and make it more prominent to manage it, since we want to encourage users to manage their subscription rather than cancelling it.
+
+payments/refund
+  * takes a subscription id and requests a refund.
+  * we can only refund the most recent payment and we can only refund if the subscription is cancelled.
+  * we can only refund if the most recent payment in FULL was made less than 7 days ago, otherwise we can only refund a prorated amount.
+payments/reactivate
+  * takes a subscription id and reactivates a cancelled subscription. this can only be done if the subscription is still within its billing period, otherwise the user would have to create a new subscription.
+payments/upgrade
+  * takes a subscription id and a new plan id and upgrades the user's subscription to the new plan. this can only be done if the user has an active subscription.
+
+
+trial support:
+when a peyment intent happens, we can only grant a trial if the user has never had a trial which involves checking the paymetns-subscriptions collection for the user to see if any exist. if any exist in any form, then we dont give a trial.
+we also need a test for this
+
+block multipl epayments
+check if user has a non-cancelled sub during payment intent creation, if so, block the payment intent from being created. this will prevent multiple payments from being made at the same time and causing issues. we can check the payments-subscriptions collection for ALL usbcriptions belonging to the UID. we can use this for the trial check as well (recycle the results).
+we also need a test for this
+
+
+
+also, can you check and confirm if the usage.js sends back the users current usage in th headers? i think it does? maybe it our tests we can check to ensure that the user is probably having their usage set this way?
+
+
+MANAGEMENT LINK
+we need an endpoint that returns a management link for the user to manage their subscription. this will involve us looking up the users current subscription, then calling the appropriate method on the payment processor to get a management link. we can only return a management link if the user has an active subscription.
+
+
+TODO
+
+* authorizations ystem that tries to charge the card to see if its valid?
+* bm_cronDaily task that doublechecks subscriptions??
+  * could check existing ones eveyr month to ensure they are still vlaud and not messed up from failed webhook processing or could check every day to ensure theres no users with multiple subscirptions active simultaneously?
+* bm_cronDaily yto handle disputes?
+  * automatically provide evidence?
+
+ATTRIBUTIONS!!!
+// Filter attribution entries older than 30 days
+const attribution = webManager.storage().get('attribution', {});
+const maxAge = 30 * 24 * 60 * 60 * 1000; // 30 days in ms
+const filtered = {};
+
+for (const [key, entry] of Object.entries(attribution)) {
+  if (!entry?.timestamp) continue;
+  if ((Date.now() - new Date(entry.timestamp).getTime()) < maxAge) {
+    filtered[key] = entry;
+  }

package/TODO.md

@@ -23,11 +23,18 @@ BEM
   * Teach it how to mock requests and use test user's SECRET API KEYS to authenticate requests
   * BEM should create a few test accounts: basic, then one for each plan level
 
+TODO
+Update deps!!!! theres lots
+* we culd have a test that TRIES EACH IMPORT ?? incase updating it fails due to ESM VULLSHIT?
+
 
 ADD HEALTHCHECK TO BEM!!!
   ✗ https://api.clockii.com/backend-manager?command=healthcheck → fetch failed
 
 TODO
+PAYMENT
+https://hookdeck.com/webhooks/platforms/guide-to-paypal-webhooks-features-and-best-practices
+
 
 # TEST REWRRK
 btw... the account.json needs to be removed. remove it from BEM and the consumong project. when we make our test system, we DO NOT NEED TO STORE THE ACCOUBT IN A JSON file. we just need a source of truth in BEM for what uid/emails to look for

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "backend-manager",
-  "version": "5.0.91",
+  "version": "5.0.92",
   "description": "Quick tools for developing Firebase functions",
   "main": "src/manager/index.js",
   "bin": {
@@ -20,7 +20,7 @@
   "projectScripts": {
     "start": "npx bm setup && npx bm serve",
     "deploy": "npx bm setup && npx bm deploy",
-    "emulators": "npx bm setup && npx bm emulators",
+    "emulator": "npx bm setup && npx bm emulator",
     "test": "npx bm setup && npx bm test",
     "setup": "npx bm setup"
   },
@@ -49,7 +49,7 @@
     "@google-cloud/pubsub": "^5.3.0",
     "@google-cloud/storage": "^7.19.0",
     "@octokit/rest": "^19.0.13",
-    "@sendgrid/mail": "^7.7.0",
+    "@sendgrid/mail": "^8.1.6",
     "@sentry/node": "^6.19.7",
     "body-parser": "^1.20.4",
     "busboy": "^1.6.0",

package/src/cli/commands/{emulators.js → emulator.js}

@@ -5,12 +5,12 @@ const jetpack = require('fs-jetpack');
 const JSON5 = require('json5');
 const powertools = require('node-powertools');
 const WatchCommand = require('./watch');
-const { DEFAULT_EMULATOR_PORTS } = require('./setup-tests/emulators-config');
+const { DEFAULT_EMULATOR_PORTS } = require('./setup-tests/emulator-config');
 
-class EmulatorsCommand extends BaseCommand {
+class EmulatorCommand extends BaseCommand {
   async execute() {
-    this.log(chalk.cyan('\n  Starting Firebase emulators (keep-alive mode)...\n'));
-    this.log(chalk.gray('  Emulators will stay running until you press Ctrl+C\n'));
+    this.log(chalk.cyan('\n  Starting Firebase emulator (keep-alive mode)...\n'));
+    this.log(chalk.gray('  Emulator will stay running until you press Ctrl+C\n'));
 
     // Warn if TEST_EXTENDED_MODE is enabled
     if (process.env.TEST_EXTENDED_MODE) {
@@ -26,29 +26,29 @@ class EmulatorsCommand extends BaseCommand {
     // Start Stripe webhook forwarding in background
     this.startStripeWebhookForwarding();
 
-    // Run emulators with keep-alive command (use single quotes since runWithEmulators wraps in double quotes)
-    const keepAliveCommand = "echo ''; echo 'Emulators ready. Press Ctrl+C to shut down...'; sleep 86400";
+    // Run emulator with keep-alive command (use single quotes since runWithEmulator wraps in double quotes)
+    const keepAliveCommand = "echo ''; echo 'Emulator ready. Press Ctrl+C to shut down...'; sleep 86400";
 
     try {
-      await this.runWithEmulators(keepAliveCommand);
+      await this.runWithEmulator(keepAliveCommand);
     } catch (error) {
       // User pressed Ctrl+C - this is expected
-      this.log(chalk.gray('\n  Emulators stopped.\n'));
+      this.log(chalk.gray('\n  Emulator stopped.\n'));
     }
   }
 
   /**
-   * Run a command with Firebase emulators
-   * @param {string} command - The command to execute inside emulators:exec
+   * Run a command with Firebase emulator
+   * @param {string} command - The command to execute inside the Firebase emulator
    * @returns {Promise<void>}
    */
-  async runWithEmulators(command) {
+  async runWithEmulator(command) {
     const projectDir = this.main.firebaseProjectPath;
 
     // Load emulator ports from firebase.json
     const emulatorPorts = this.loadEmulatorPorts(projectDir);
 
-    // Check for port conflicts before starting emulators
+    // Check for port conflicts before starting emulator
     const canProceed = await this.checkAndKillBlockingProcesses(emulatorPorts);
     if (!canProceed) {
       throw new Error('Port conflicts could not be resolved');
@@ -58,9 +58,9 @@ class EmulatorsCommand extends BaseCommand {
     // hosting is included so localhost:5002 rewrites work (e.g., /backend-manager -> bm_api)
     // pubsub is included so scheduled functions (bm_cronDaily) can be triggered in tests
     // Use double quotes for command wrapper since the command may contain single quotes (JSON strings)
-    const emulatorsCommand = `BEM_TESTING=true firebase emulators:exec --only functions,firestore,auth,database,hosting,pubsub --ui "${command}"`;
+    const emulatorCommand = `BEM_TESTING=true firebase emulators:exec --only functions,firestore,auth,database,hosting,pubsub --ui "${command}"`;
 
-    await powertools.execute(emulatorsCommand, {
+    await powertools.execute(emulatorCommand, {
       log: true,
       cwd: projectDir,
     });
@@ -90,4 +90,4 @@ class EmulatorsCommand extends BaseCommand {
   }
 }
 
-module.exports = EmulatorsCommand;
+module.exports = EmulatorCommand;

package/src/cli/commands/index.js

@@ -8,7 +8,7 @@ module.exports = {
   ServeCommand: require('./serve'),
   DeployCommand: require('./deploy'),
   TestCommand: require('./test'),
-  EmulatorsCommand: require('./emulators'),
+  EmulatorCommand: require('./emulator'),
   CleanCommand: require('./clean'),
   IndexesCommand: require('./indexes'),
   WatchCommand: require('./watch'),

package/src/cli/commands/setup-tests/{emulators-config.js → emulator-config.js}

@@ -25,9 +25,9 @@ const REQUIRED_EMULATORS = {
   ui: { enabled: true, port: DEFAULT_EMULATOR_PORTS.ui },
 };
 
-class EmulatorsConfigTest extends BaseTest {
+class EmulatorConfigTest extends BaseTest {
   getName() {
-    return 'emulators config in firebase.json';
+    return 'emulator config in firebase.json';
   }
 
   async run() {
@@ -75,5 +75,5 @@ class EmulatorsConfigTest extends BaseTest {
   }
 }
 
-module.exports = EmulatorsConfigTest;
-module.exports.DEFAULT_EMULATOR_PORTS = DEFAULT_EMULATOR_PORTS;
+module.exports = EmulatorConfigTest;
+module.exports.DEFAULT_EMULATOR_PORTS = DEFAULT_EMULATOR_PORTS;

package/src/cli/commands/setup-tests/index.js

@@ -24,7 +24,7 @@ const FirestoreIndexesInJsonTest = require('./firestore-indexes-in-json');
 const RealtimeRulesInJsonTest = require('./realtime-rules-in-json');
 const StorageRulesInJsonTest = require('./storage-rules-in-json');
 const RemoteconfigTemplateInJsonTest = require('./remoteconfig-template-in-json');
-const EmulatorsConfigTest = require('./emulators-config');
+const EmulatorConfigTest = require('./emulator-config');
 const HostingRewritesTest = require('./hosting-rewrites');
 const FirestoreIndexesSyncedTest = require('./firestore-indexes-synced');
 const StorageLifecyclePolicyTest = require('./storage-lifecycle-policy');
@@ -64,7 +64,7 @@ function getTests(context) {
     new RealtimeRulesInJsonTest(context),
     new StorageRulesInJsonTest(context),
     new RemoteconfigTemplateInJsonTest(context),
-    new EmulatorsConfigTest(context),
+    new EmulatorConfigTest(context),
     new HostingRewritesTest(context),
     new FirestoreIndexesSyncedTest(context),
     new StorageLifecyclePolicyTest(context),

package/src/cli/commands/setup-tests/project-id-consistency.js

@@ -9,7 +9,7 @@ const chalk = require('chalk');
  * - functions/backend-manager-config.json (firebaseConfig.projectId)
  * - functions/service-account.json (project_id)
  *
- * Mismatches cause tests to fail when running emulators in separate terminals
+ * Mismatches cause tests to fail when running emulator in separate terminals
  * because different parts of the system connect to different Firestore databases.
  */
 class ProjectIdConsistencyTest extends BaseTest {

package/src/cli/commands/test.js

@@ -4,8 +4,8 @@ const chalk = require('chalk');
 const jetpack = require('fs-jetpack');
 const JSON5 = require('json5');
 const powertools = require('node-powertools');
-const { DEFAULT_EMULATOR_PORTS } = require('./setup-tests/emulators-config');
-const EmulatorsCommand = require('./emulators');
+const { DEFAULT_EMULATOR_PORTS } = require('./setup-tests/emulator-config');
+const EmulatorCommand = require('./emulator');
 
 class TestCommand extends BaseCommand {
   async execute() {
@@ -42,14 +42,14 @@ class TestCommand extends BaseCommand {
     // Build the test command
     const testCommand = this.buildTestCommand(testConfig);
 
-    // Check if emulators are already running
-    const emulatorsRunning = this.areEmulatorsRunning(emulatorPorts);
+    // Check if emulator is already running
+    const emulatorRunning = this.isEmulatorRunning(emulatorPorts);
 
-    if (emulatorsRunning) {
-      this.log(chalk.cyan('Running tests against EXISTING emulators'));
+    if (emulatorRunning) {
+      this.log(chalk.cyan('Running tests against EXISTING emulator'));
       await this.runTestsDirectly(testCommand, functionsDir, emulatorPorts);
     } else {
-      this.log(chalk.cyan('Starting emulators and running tests...'));
+      this.log(chalk.cyan('Starting emulator and running tests...'));
       await this.runEmulatorTests(testCommand);
     }
   }
@@ -164,16 +164,16 @@ class TestCommand extends BaseCommand {
   }
 
   /**
-   * Check if emulators are already running
+   * Check if emulator is already running
    */
-  areEmulatorsRunning(emulatorPorts) {
+  isEmulatorRunning(emulatorPorts) {
     // Check if functions emulator port is in use
-    // If it is, assume all emulators are running
+    // If it is, assume emulator is running
     return this.isPortInUse(emulatorPorts.functions);
   }
 
   /**
-   * Run tests directly (emulators already running)
+   * Run tests directly (emulator already running)
    */
   async runTestsDirectly(testCommand, functionsDir, emulatorPorts) {
     this.log(chalk.gray(`  Hosting: http://127.0.0.1:${emulatorPorts.hosting}`));
@@ -192,16 +192,16 @@ class TestCommand extends BaseCommand {
   }
 
   /**
-   * Run tests with Firebase emulators (starts emulators, runs tests, shuts down)
+   * Run tests with Firebase emulator (starts emulator, runs tests, shuts down)
    */
   async runEmulatorTests(testCommand) {
-    this.log(chalk.gray('  Starting Firebase emulators...\n'));
+    this.log(chalk.gray('  Starting Firebase emulator...\n'));
 
-    // Use EmulatorsCommand to run tests with emulators
-    const emulatorsCmd = new EmulatorsCommand(this.main);
+    // Use EmulatorCommand to run tests with emulator
+    const emulatorCmd = new EmulatorCommand(this.main);
 
     try {
-      await emulatorsCmd.runWithEmulators(testCommand);
+      await emulatorCmd.runWithEmulator(testCommand);
     } catch (error) {
       // Only exit with error if it wasn't a user-initiated exit
       if (error.code !== 0) {

package/src/cli/index.js

@@ -21,7 +21,7 @@ const InstallCommand = require('./commands/install');
 const ServeCommand = require('./commands/serve');
 const DeployCommand = require('./commands/deploy');
 const TestCommand = require('./commands/test');
-const EmulatorsCommand = require('./commands/emulators');
+const EmulatorCommand = require('./commands/emulator');
 const CleanCommand = require('./commands/clean');
 const IndexesCommand = require('./commands/indexes');
 const WatchCommand = require('./commands/watch');
@@ -106,9 +106,9 @@ Main.prototype.process = async function (args) {
     return await cmd.execute();
   }
 
-  // Emulators (keep-alive mode)
-  if (self.options['emulators'] || self.options['emulator']) {
-    const cmd = new EmulatorsCommand(self);
+  // Emulator (keep-alive mode)
+  if (self.options['emulator'] || self.options['emulators']) {
+    const cmd = new EmulatorCommand(self);
     return await cmd.execute();
   }
 

package/src/manager/events/auth/on-create.js

@@ -1,5 +1,3 @@
-const fetch = require('wonderful-fetch');
-const moment = require('moment');
 const { FieldValue } = require('firebase-admin/firestore');
 
 const MAX_RETRIES = 3;
@@ -15,7 +13,9 @@ const RETRY_DELAY_MS = 1000;
  * - Checks if user doc already exists (auth.uid) → skips if exists (handles test accounts, provider linking)
  * - Batch writes user doc + increment count atomically
  * - Retries up to 3 times with exponential backoff on failure
- * - Sends analytics event (non-critical, no retry)
+ *
+ * Non-critical work (name inference, welcome emails, marketing contact) is handled
+ * by the user/signup endpoint, which the frontend calls after account creation.
  */
 module.exports = async ({ Manager, assistant, user, context, libraries }) => {
   const startTime = Date.now();
@@ -71,42 +71,13 @@ module.exports = async ({ Manager, assistant, user, context, libraries }) => {
       await batch.commit();
     }, MAX_RETRIES, RETRY_DELAY_MS);
 
-    assistant.log(`onCreate: Successfully created user doc for ${user.uid}`);
+    assistant.log(`onCreate: Successfully created user doc for ${user.uid} (${Date.now() - startTime}ms)`);
   } catch (error) {
     assistant.error(`onCreate: Failed to create user doc after ${MAX_RETRIES} retries:`, error);
 
     // Don't reject - the user was already created in Auth
-    // The user:sign-up endpoint will handle creating the doc if it's missing
-    return;
-  }
-
-  // Send emails in dev/production, or in test mode if TEST_EXTENDED_MODE=true
-  // Note: Must be passed to the emulator
-  const shouldSendEmails = !assistant.isTesting() || process.env.TEST_EXTENDED_MODE;
-
-  if (!shouldSendEmails) {
-    assistant.log(`onCreate: Skipping emails/SendGrid (BEM_TESTING=true, TEST_EXTENDED_MODE not set)`);
-  } else {
-    assistant.log(`onCreate: Sending emails/adding to SendGrid for ${user.uid}`);
-
-    // Add to marketing lists (SendGrid + Beehiiv) via centralized endpoint
-    fetch(`${Manager.project.apiUrl}/backend-manager/marketing/contact`, {
-      method: 'POST',
-      response: 'json',
-      body: {
-        backendManagerKey: process.env.BACKEND_MANAGER_KEY,
-        email: user.email,
-        source: 'auth:on-create',
-      },
-    }).catch(e => assistant.error('onCreate: add-marketing-contact failed:', e));
-
-    // Send welcome emails (non-blocking, don't fail on error)
-    sendWelcomeEmail(Manager, assistant, user).catch(e => assistant.error('onCreate: sendWelcomeEmail failed:', e));
-    sendCheckupEmail(Manager, assistant, user).catch(e => assistant.error('onCreate: sendCheckupEmail failed:', e));
-    sendFeedbackEmail(Manager, assistant, user).catch(e => assistant.error('onCreate: sendFeedbackEmail failed:', e));
+    // The user/signup endpoint will handle creating the doc if it's missing
   }
-
-  assistant.log(`onCreate: Completed for ${user.uid} (${Date.now() - startTime}ms)`);
 };
 
 /**
@@ -133,127 +104,3 @@ async function retryBatchWrite(assistant, fn, maxRetries, delayMs) {
 
   throw lastError; // All retries failed
 }
-
-/**
- * Send welcome email (immediate)
- */
-function sendWelcomeEmail(Manager, assistant, user) {
-  return fetch(`${Manager.project.apiUrl}/backend-manager/admin/email`, {
-    method: 'POST',
-    response: 'json',
-    body: {
-      backendManagerKey: process.env.BACKEND_MANAGER_KEY,
-      to: [{ email: user.email }],
-      categories: ['account/welcome'],
-      subject: `Welcome to ${Manager.config.brand.name}!`,
-      template: 'd-b7f8da3c98ad49a2ad1e187f3a67b546',
-      group: 25928,
-      copy: false,
-      ensureUnique: true,
-      data: {
-        email: {
-          preview: `Welcome aboard! I'm Ian, the CEO and founder of ${Manager.config.brand.name}. I'm here to ensure your journey with us gets off to a great start.`,
-        },
-        body: {
-          title: `Welcome to ${Manager.config.brand.name}!`,
-          message: `
-            Welcome aboard!
-            <br><br>
-            I'm Ian, the founder and CEO of <strong>${Manager.config.brand.name}</strong>, and I'm thrilled to have you with us.
-            Your journey begins today, and we are committed to supporting you every step of the way.
-            <br><br>
-            We are dedicated to ensuring your experience is exceptional.
-            Feel free to reply directly to this email with any questions you may have.
-            <br><br>
-            Thank you for choosing <strong>${Manager.config.brand.name}</strong>. Here's to new beginnings!
-          `,
-        },
-        signoff: {
-          type: 'personal',
-          name: 'Ian Wiedenman, CEO',
-          url: `https://ianwiedenman.com?utm_source=welcome-email&utm_medium=email&utm_campaign=${Manager.config.app.id}`,
-          urlText: '@ianwieds',
-        },
-      },
-    },
-  })
-  .then((json) => {
-    assistant.log('sendWelcomeEmail(): Success', json);
-    return json;
-  });
-}
-
-/**
- * Send checkup email (7 days after signup)
- */
-function sendCheckupEmail(Manager, assistant, user) {
-  return fetch(`${Manager.project.apiUrl}/backend-manager/admin/email`, {
-    method: 'POST',
-    response: 'json',
-    body: {
-      backendManagerKey: process.env.BACKEND_MANAGER_KEY,
-      to: [{ email: user.email }],
-      categories: ['account/checkup'],
-      subject: `How's your experience with ${Manager.config.brand.name}?`,
-      template: 'd-b7f8da3c98ad49a2ad1e187f3a67b546',
-      group: 25928,
-      copy: false,
-      ensureUnique: true,
-      sendAt: moment().add(7, 'days').unix(),
-      data: {
-        email: {
-          preview: `Checking in from ${Manager.config.brand.name} to see how things are going. Let us know if you have any questions or feedback!`,
-        },
-        body: {
-          title: `How's everything going?`,
-          message: `
-            Hi there,
-            <br><br>
-            It's Ian again from <strong>${Manager.config.brand.name}</strong>. Just checking in to see how things are going for you.
-            <br><br>
-            Have you had a chance to explore all our features? Any questions or feedback for us?
-            <br><br>
-            We're always here to help, so don't hesitate to reach out. Just reply to this email and we'll get back to you as soon as possible.
-            <br><br>
-            Thank you for choosing <strong>${Manager.config.brand.name}</strong>. Here's to new beginnings!
-          `,
-        },
-        signoff: {
-          type: 'personal',
-          name: 'Ian Wiedenman, CEO',
-          url: `https://ianwiedenman.com?utm_source=checkup-email&utm_medium=email&utm_campaign=${Manager.config.app.id}`,
-          urlText: '@ianwieds',
-        },
-      },
-    },
-  })
-  .then((json) => {
-    assistant.log('sendCheckupEmail(): Success', json);
-    return json;
-  });
-}
-
-/**
- * Send feedback email (14 days after signup)
- */
-function sendFeedbackEmail(Manager, assistant, user) {
-  return fetch(`${Manager.project.apiUrl}/backend-manager/admin/email`, {
-    method: 'POST',
-    response: 'json',
-    body: {
-      backendManagerKey: process.env.BACKEND_MANAGER_KEY,
-      to: [{ email: user.email }],
-      categories: ['engagement/feedback'],
-      subject: `Want to share your feedback about ${Manager.config.brand.name}?`,
-      template: 'd-c1522214c67b47058669acc5a81ed663',
-      group: 25928,
-      copy: false,
-      ensureUnique: true,
-      sendAt: moment().add(14, 'days').unix(),
-    },
-  })
-  .then((json) => {
-    assistant.log('sendFeedbackEmail(): Success', json);
-    return json;
-  });
-}