docs: genericize site-specific examples in nk-billing and nk-marketing

Replace product-specific names in code comments, type docs, the README, and a
test fixture with generic placeholders, so the public packages carry no
references to private downstream sites.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: jleclanche

.changeset/nk-billing-generic-docs.md

@@ -0,0 +1,6 @@
+---
+"@ingram-tech/nk-billing": patch
+---
+
+Docs only: replace site-specific examples in code comments with generic
+placeholders. No runtime or API change.

.changeset/nk-marketing-generic-docs.md

@@ -0,0 +1,6 @@
+---
+"@ingram-tech/nk-marketing": patch
+---
+
+Docs only: replace site-specific examples in the README and type comments with
+generic placeholders. No runtime or API change.

packages/nk-billing/src/balance.ts

@@ -1,6 +1,6 @@
 /**
- * Customer-balance wallet — Stripe's own credit ledger, for pay-as-you-go sites
- * (domains.ingram.tech). Distinct from the in-app credit ledger in
+ * Customer-balance wallet — Stripe's own credit ledger, for pay-as-you-go
+ * sites. Distinct from the in-app credit ledger in
  * `@ingram-tech/nk-billing/credits`: this stores the balance *in Stripe* as a
  * signed integer (negative = credit available to the customer), so there is no
  * local table to keep in sync. Pick this when the unit you sell is money;

packages/nk-billing/src/client.ts

@@ -4,8 +4,9 @@
  *
  * This is the one pattern every Ingram site had hand-rolled identically (the
  * `getStripe()` singleton); it lives here once now. Single-mode sites call
- * {@link getStripe}; the dual-mode site (cloud.ingram.tech) calls
- * {@link stripeFor} with a mode and gets one memoised client per mode.
+ * {@link getStripe}; a dual-mode site (its own merchant of record, running the
+ * Stripe sandbox beside live) calls {@link stripeFor} with a mode and gets one
+ * memoised client per mode.
  */
 
 import Stripe from "stripe";

packages/nk-billing/src/credits.ts

@@ -1,6 +1,6 @@
 /**
  * The in-app credit ledger — the stateful half of nk-billing, for sites that
- * meter usage in abstract "credits" rather than money (integrain). It follows
+ * meter usage in abstract "credits" rather than money. It follows
  * nextkit's Django-app model: this package owns its tables and ships their
  * migration (`migrations/0001_billing.sql`), and takes the database connection by
  * **injection** so it never reaches into the consuming site's schema.

packages/nk-billing/src/customers.ts

@@ -4,9 +4,9 @@
  * then finds it back by metadata search — no local `stripe_customer_id` column is
  * required just to locate the customer (though sites cache it for speed).
  *
- * The metadata key differs per site (`financica_organization_id`,
- * `integrain_org_id`, …), so it is always passed in explicitly via
- * {@link CustomerRef} rather than baked in here — that is the framework seam.
+ * The metadata key differs per site (`acme_organization_id`, `acme_user_id`,
+ * …), so it is always passed in explicitly via {@link CustomerRef} rather than
+ * baked in here — that is the framework seam.
  */
 
 import type Stripe from "stripe";
@@ -15,7 +15,7 @@ import { getStripe } from "./client.js";
 /** Identifies a Stripe customer by a metadata tag → local entity id. */
 export interface CustomerRef {
 	/** The Stripe `metadata` key the local id is stored under, e.g.
-	 *  "integrain_org_id". Choose one per site and use it everywhere. */
+	 *  "acme_org_id". Choose one per site and use it everywhere. */
 	metadataKey: string;
 	/** The local entity id (org id, user id, …). */
 	id: string;

packages/nk-billing/src/keys.ts

@@ -8,17 +8,17 @@
  *
  * Two deployment shapes are supported, picked per call site, never both at once:
  *
- *   1. Single-mode (the default — financica / integrain / thornhill): one
- *      account, one key. `getStripe()` reads STRIPE_SECRET_KEY and
- *      `webhookSecret()` reads STRIPE_WEBHOOK_SECRET.
+ *   1. Single-mode (the default for most sites): one account, one key.
+ *      `getStripe()` reads STRIPE_SECRET_KEY and `webhookSecret()` reads
+ *      STRIPE_WEBHOOK_SECRET.
  *
- *   2. Dual-mode (cloud.ingram.tech, which is its own merchant of record and
- *      runs the Stripe sandbox beside live): `stripeFor("test"|"live")` reads
+ *   2. Dual-mode (a site that is its own merchant of record and runs the Stripe
+ *      sandbox beside live): `stripeFor("test"|"live")` reads
  *      STRIPE_SECRET_KEY_{TEST,LIVE} and `webhookSecret(mode)` reads
  *      STRIPE_WEBHOOK_SECRET_{TEST,LIVE}.
  *
  * Nothing here hardcodes a price ID. Prices are resolved at runtime by their
- * stable Stripe `lookup_key` (set on the Price in the infra Pulumi program), so
+ * stable Stripe `lookup_key` (set on the Price out of band, e.g. in your IaC), so
  * the same key resolves in test and live even though their price IDs differ.
  */
 

packages/nk-marketing/README.md

@@ -76,11 +76,11 @@ const result = await marketing.sendLifecycle({
 	campaignKey: "first-invoice-nudge",
 	email: contact.email,
 	userId: contact.userId,
-	from: { name: "Peppost" },
-	subject: "Send your first Stripe e-invoice with Peppost",
+	from: { name: "Acme" },
+	subject: "Send your first invoice with Acme",
 	content: "You're all set up — here's how to send your first invoice…",
 	cta: { label: "Open dashboard", href: "https://example.com/dashboard" },
-	footerReason: "you have a Peppost account",
+	footerReason: "you have an Acme account",
 });
 // result.status: "sent" | "duplicate" | "suppressed"
 ```

packages/nk-marketing/src/client.test.ts

@@ -310,15 +310,15 @@ describe("sendLifecycle", () => {
 		email: "a@acme.test",
 		subject: "Send your first invoice",
 		content: "Get started.",
-		from: { name: "Peppost" },
+		from: { name: "Acme" },
 	};
 
 	it("sends once, then reports duplicate", async () => {
 		expect(await marketing.sendLifecycle(opts)).toEqual({ status: "sent" });
 		expect(await marketing.sendLifecycle(opts)).toEqual({ status: "duplicate" });
 		expect(sendMock).toHaveBeenCalledOnce();
 		const arg = sendMock.mock.calls[0]?.[0];
-		expect(arg?.from).toBe("Peppost <notifications@mail.test>");
+		expect(arg?.from).toBe("Acme <notifications@mail.test>");
 		expect(arg?.listUnsubscribe?.url).toContain("token=");
 	});
 

packages/nk-marketing/src/types.ts

@@ -50,7 +50,7 @@ export interface Cta {
 
 /** Sender identity for a lifecycle send (broadcasts take it from the audience). */
 export interface Sender {
-	/** Display name, e.g. "Peppost". */
+	/** Display name, e.g. "Acme". */
 	name: string;
 	/** Local part of the from address; defaults to "notifications". */
 	localPart?: string;
@@ -99,8 +99,8 @@ export interface LifecycleOptions {
 	cta?: Cta;
 	from: Sender;
 	/**
-	 * Footer line explaining why the contact received this, e.g. "you have a
-	 * Peppost account". Defaults to a generic account-based reason.
+	 * Footer line explaining why the contact received this, e.g. "you have an
+	 * Acme account". Defaults to a generic account-based reason.
 	 */
 	footerReason?: string;
 }