test(e2e): Batch C LIVE prod specs (W-STACKS/STACKS-ADV/LIFECYCLE/AUTH2) (#186)

Adds e2e/live-stacks-lifecycle.spec.ts driving the stack, resource-
lifecycle, and secondary-auth user-flows against PROD via the minted
cohort account. Closes Batch C of the prod-coverage matrix (waves 11-14).

W-STACKS: POST /stacks/new (single-service minimal manifest -> 202
accepted contract) -> GET /api/v1/stacks (list) + GET /api/v1/stacks/:slug
+ GET /stacks/:slug (get) -> PATCH /stacks/:slug/env (merge -> 200, merged
key present; incremental + invalid-key 400) -> missing-slug 404 -> two-step
DELETE /stacks/:slug (paid 202 pending OR 200) + confirm-deletion cancel
-> skip-email reap -> gone. Full multi-service Kaniko build DEFERRED
(202-accepted contract only, mirrors live-writes deploy 202).

W-STACKS-ADV: GET /api/v1/stacks/:slug/family (PRO 200 + private
Cache-Control), POST /api/v1/stacks/:slug/promote (non-destructive
contract: 412 needs-build / 402 / 400 / 202, never 5xx; reaps any
accidentally-created sibling), DELETE confirm-deletion cancel arm (404 with
no pending row).

W-LIFECYCLE: on a FAST cache resource (no dedicated DB) -- pause -> resume
(Pro+), rotate-credentials, backup CONTRACT (cache -> 400
unsupported_resource_type, postgres-only; never waits for a real backup),
backups/restores list, reap.

W-AUTH2: POST /auth/email/start accepted contract (Brevo-gated, delivery
NOT asserted), POST /auth/github body-flow no-credential contract
(400 missing_code / 401 oauth_failed / 503 not-configured), and a
DISPOSABLE claimed-session logout round-trip (/auth/me 200 -> logout ->
SAME bearer 401). The logout leg NEVER revokes the shared minted JWT
(Batch B lesson) -- it claims a throwaway team and revokes THAT session.

cleanup-ledger.ts: add a `stack` entity kind (DELETE /stacks/:slug with
X-Skip-Email-Confirmation so a paid team's two-step flow doesn't strand
the reap behind an undeliverable confirmation email; account cascade is
the backstop).

Safety machinery mirrors live-writes/live-reads EXACTLY (rule 24):
E2E_LIVE=1 gating, assertSafeApiTarget, ledger-before-assert + inline reap
+ afterAll backstop, 503 per-service skips. Brevo/Razorpay contract-only;
no team-tier minting; slow services pinned off (cache hot-pool).

npm run gate green (tsc --noEmit + build + 1115 vitest pass).

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

Author: mastermanas805

e2e/cleanup-ledger.ts

@@ -26,6 +26,14 @@ export type CohortEntityKind =
   | 'deployment'
   | 'team'
   | 'storage-prefix'
+  // A multi-service stack created via POST /stacks/new (Batch C W-STACKS /
+  // W-STACKS-ADV). Reaped via DELETE /stacks/:slug — but a PAID team's plain
+  // DELETE enters the two-step email-confirmed flow (202 pending), which on
+  // prod never resolves because the Brevo sender is unvalidated. So the reaper
+  // sends the X-Skip-Email-Confirmation header for this kind to force immediate
+  // destruction (the SAME header the spec's inline reap uses). The account
+  // cascade (DELETE /internal/e2e/account) is the backstop.
+  | 'stack'
   // A SECONDARY ephemeral cohort account minted via POST /internal/e2e/account
   // (Batch B W-TEAM member-mgmt isolation). It is NOT reapable by a team-scoped
   // bearer DELETE — there is no DELETE /api/v1/team/:id route, and DELETE
@@ -115,6 +123,11 @@ function deletePath(entity: CohortEntity): string {
       return `/api/v1/resources/${entity.id}`
     case 'deployment':
       return `/api/v1/deployments/${entity.id}`
+    case 'stack':
+      // Stacks delete by slug (NOT under /api/v1). The skip-email header is
+      // attached in reapEntities so a paid team's two-step flow doesn't strand
+      // the row behind an undeliverable confirmation email.
+      return `/stacks/${entity.id}`
     case 'team':
       return `/api/v1/team/${entity.id}`
     case 'e2e-account':
@@ -157,6 +170,15 @@ export async function reapEntities(
     } else if (entity.token) {
       headers.Authorization = `Bearer ${entity.token}`
     }
+    if (entity.kind === 'stack') {
+      // Force immediate destruction — a paid team's DELETE /stacks/:slug would
+      // otherwise enter the two-step email-confirmed flow (202 pending), which
+      // never resolves on prod (Brevo sender unvalidated). The 202 would then be
+      // mis-counted as a failed reap (not 2xx/404). The skip-email header makes
+      // teardown synchronous + idempotent. Constant per the no-hardcoded-strings
+      // rule (mirrors deletion_confirm.go SkipEmailConfirmationHeader).
+      headers['X-Skip-Email-Confirmation'] = 'yes'
+    }
     try {
       const resp = await request.fetch(`${entity.apiUrl.replace(/\/$/, '')}${path}`, {
         method: 'DELETE',