fix(api): purge snapshot — null out stripe IDs from dropped tables

Build was failing because the new PurgeOrganizationSnapshotService
(added on main while this branch was open) queried db.organizationBilling
and db.pentestSubscription, both of which we dropped in migration
20260427000000_pentest_credits. The git auto-merge couldn't catch this
— it's a logical conflict, not a textual one.

Replace the queries with null literals. The snapshot's `stripe.customerId`
and `stripe.subscriptionId` shape is preserved so downstream consumers
(purge orchestrator, restore tooling) keep working; the legacy tables
had no production data anyway, and v2 billing will add new fields here
when it lands.

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

Author: tofikwest

apps/api/src/admin-organizations/purge-organization-snapshot.service.ts

@@ -22,8 +22,6 @@ export class PurgeOrganizationSnapshotService {
     }
 
     const [
-      billing,
-      pentest,
       trustResources,
       trustNdas,
       trustDocs,
@@ -36,14 +34,13 @@ export class PurgeOrganizationSnapshotService {
       integrations,
       counts,
     ] = await Promise.all([
-      db.organizationBilling.findUnique({
-        where: { organizationId },
-        select: { stripeCustomerId: true },
-      }),
-      db.pentestSubscription.findUnique({
-        where: { organizationId },
-        select: { stripeSubscriptionId: true },
-      }),
+      // The legacy `organization_billing` and `pentest_subscriptions`
+      // tables were dropped in migration 20260427000000_pentest_credits;
+      // they were Stripe-coupled records that never had production data
+      // and have been superseded by the `pentest_credits` wallet model.
+      // The snapshot intentionally omits them — there's nothing to
+      // capture. If/when v2 introduces real Stripe billing, the new
+      // tables get added here at that point.
       db.trustResource.findMany({
         where: { organizationId },
         select: { s3Key: true },
@@ -130,9 +127,13 @@ export class PurgeOrganizationSnapshotService {
     return {
       organization: { id: org.id, name: org.name, slug: org.slug },
       counts,
+      // Stripe IDs intentionally null — the source tables were dropped
+      // in 20260427000000_pentest_credits. The shape is preserved so
+      // downstream consumers (purge orchestrator) don't need to change
+      // until v2 billing replaces these.
       stripe: {
-        customerId: billing?.stripeCustomerId ?? null,
-        subscriptionId: pentest?.stripeSubscriptionId ?? null,
+        customerId: null,
+        subscriptionId: null,
       },
       s3KeysByBucket,
       knowledgeBaseDocumentIds: kbDocs.map((d) => d.id),