ghostguild-org/docs/LAUNCH_READINESS.md

Launch Readiness

Status as of 2026-04-20. Target launch: before 2026-05-01.

Single source of truth for work remaining before cutover. P0 blocks launch; P1 is strongly preferred but survivable. Completed items are archived — see ~/.claude/projects/-Users-jennie-Sites-ghostguild-org/memory/project_launch_readiness_archive.md. Post-launch backlog lives in docs/TODO.md.

---

Current state

• Vitest snapshot 2026-04-25 ~18:23 local: 703 passing / 8 failing / 2 skipped (713 total). The previously-flagged 6 helcim-payment failures are now green. The 8 current failures are in tests/server/api/auth-verify.test.js and tests/server/api/cancel-subscription.smoke.test.js, both belonging to in-flight Phase 5 fixes (#10 and #9) being landed by parallel impl subagents — they will resolve as those branches merge.
• All launch code is on local main: Helcim plan consolidation, contribution-amount redesign, cadence UX unification, and receipts Phase 1. Not pushed — site is not on Netlify yet.
• Helcim plan consolidation migration ran against prod 2026-04-18 (Monthly plan id 50302, Annual plan id 50303).
• Contribution-amount migration has NOT yet been run against prod.
• Receipts Phase 1 code is shipped; remaining work is deploy-time only (see Deploy checklist).

---

P0 — Must fix before launch

None outstanding.

---

P1 — Strongly preferred before launch

None outstanding.

---

Deploy checklist

Applies when the site is connected to Netlify / production hosting. Nothing here is actionable until that connection exists; kept here so nothing gets forgotten at cutover.

• Push local main to origin/main.
• Run node scripts/migrate-contribution-amount.cjs --apply against prod Mongo BEFORE the new code serves traffic. Idempotent; dry-run on local counted 34 members. Requires MONGODB_URI in env. The script writes contributionAmount (Number) derived from existing contributionTier (String) on every Member doc; the old field is left intact for a window.
• Set NUXT_HELCIM_MONTHLY_PLAN_ID=50302 in production env.
• Set NUXT_HELCIM_ANNUAL_PLAN_ID=50303 in production env.
• Run node scripts/reconcile-helcim-payments.mjs --apply against prod Mongo AFTER the new code serves traffic to backfill Payment records for pre-existing members. Idempotent (unique helcimTransactionId); safe to re-run as a nightly reconciliation job post-launch.
• Prod audit for pre-fix series-pass bypass registrations. Fixed in f34b062 + 4e1888a (2026-04-20). Before that, child events of pass-only series (tickets.requiresSeriesTicket=true && tickets.allowIndividualEventTickets=false) accepted drop-in registrations from non-pass-holders. For every such series, list its child-event registrations where the registrant is not in the parent series' pass-holder list, filter to registeredAt < 2026-04-20, and decide per-case: grandfather (keep + notify), refund + unregister, or silently unregister. Local Mongo was scrubbed of 2 such rows on 2026-04-20; prod was intentionally untouched.
• Helcim dashboard: disable the default payment-confirmation email for plans 50302 + 50303. We send our own CRA-safe confirmation via Resend (server/emails/paymentConfirmation.js) triggered from upsertPaymentFromHelcim; leaving Helcim's default on = duplicate emails.
• Run one real test charge on staging via the cloudflared tunnel and verify (a) a Payment doc in Mongo with amount, paymentType, status: 'success', and (b) exactly one CRA-compliant confirmation email (charity name + "not an official donation receipt" disclaimer; no banned assertive phrasing).
• Rotate HELCIM_API_TOKEN in the Helcim merchant portal and update the prod env var. The token was previously exposed in window.__NUXT__ payload until today's deploy.
• Set NUXT_RECONCILE_TOKEN in production env (any 32+ char random string). Used as shared secret between Netlify scheduled function and the internal reconcile route.
• Verify Netlify scheduled function reconcile-payments is enabled in the Netlify dashboard. Schedule: daily.

Env vars required in production (reference):

• MONGODB_URI
• JWT_SECRET (or NUXT_JWT_SECRET — the NUXT_ variant wins)
• RESEND_API_KEY
• HELCIM_API_TOKEN
• NUXT_HELCIM_MONTHLY_PLAN_ID
• NUXT_HELCIM_ANNUAL_PLAN_ID
• SLACK_BOT_TOKEN
• BASE_URL
• OIDC_COOKIE_SECRET
• NUXT_PUBLIC_HELCIM_PORTAL_URL
• NUXT_RECONCILE_TOKEN

---

Fixed 2026-04-25

Day-of-launch security and correctness audit. All commit shas TBD until Phase 5.

CRITICAL (security)

• Fix #1 — HELCIM_API_TOKEN removed from public runtime config + dead useHelcim.js deleted. Token must be rotated post-deploy (was previously exposed via window.__NUXT__).
• Fix #2 — /api/helcim/customer gated with origin check + per-IP/email rate limit + magic-link email verification (replaces unauthenticated setAuthCookie).
• Fix #3 — /api/events/[id]/payment deleted (dead code with auth bypass). processHelcimPayment stub + eventPaymentSchema removed.
• Fix #4 — /api/helcim/initialize-payment re-derives ticket amount server-side via calculateTicketPrice; new series_ticket metadata type.
• Fix #5 — /api/helcim/customer upgrades existing status:guest members in place rather than rejecting with 409.

HIGH (correctness)

• Fix #6 — Recurring reconciliation: Netlify scheduled function calls /api/internal/reconcile-payments daily. Requires NUXT_RECONCILE_TOKEN env var.
• Fix #7 — validateBeforeSave: false added to event subdoc saves (waitlist endpoints) to dodge legacy location validators.
• Fix #8 — Series-pass purchase always creates a guest Member when caller is unauthenticated, mirroring event-ticket flow.
• Fix #9 — cancel-subscription leaves status active (per ratified bylaws); adds lastCancelledAt audit field.
• Fix #10 — /api/auth/verify uses validateBody with .strict() Zod schema.
• Fix #11 — Added 8 vitest cases for cancel-subscription.post.js (was uncovered).

Side-quests

• Visual audit Phase 4 changes (events/series surface)
• Per-fix branch verification: see docs/superpowers/specs/2026-04-25-fix-*.md

---

Manual browser tests still needed

None outstanding. All launch-blocking flows verified via local dev or cloudflared tunnel with real Helcim test card + real email (see archive for the full log). The one remaining browser verification is the staging test charge bundled into the Deploy checklist above.

---

Bylaws decoupling — follow-ups (added 2026-04-18)

Context: bylaws are being amended to remove automatic termination for nonpayment. Membership status will be fully decoupled from payment status; failed payments trigger committee outreach, not status change. Copy + UI access gates already aligned in useMemberStatus.js and account.vue (2026-04-18). Server-side status gating shipped as B2 (see archive). The behavioral changes below remain.

Not blocking launch — the amendment hasn't passed yet, and the user-visible copy/UI is already consistent. Pick up once the amendment is ratified.

B1. cancel-subscription flips status to pending_payment

• server/api/members/cancel-subscription.post.js:31,48
• When a member cancels their paid subscription, status is set to pending_payment and contribution amount to 0. Under the new model, cancelling a payment plan moves the member to the $0 contribution — status should stay active.
• Fix: change status: 'pending_payment' → status: 'active' in both the findByIdAndUpdate payload (line 31) and the response (line 48). Comment at line 26 also needs updating ("(not cancelled) so member can re-subscribe" → reflect new framing).
• Add coverage in tests/server/api/cancel-subscription.test.js if it doesn't already exist.

B3. Vestigial pending_payment status

• Once payment is fully decoupled, pending_payment no longer gates anything and is functionally equivalent to active. Consider removing it from the enum (server/models/member.js:38, server/utils/schemas.js:299) and treating new signups as active from the moment of account creation.
• Touches: signup flow (helcim/customer.post.js:34, invite/accept.post.js:48), admin filter UI (app/pages/admin/members/index.vue:45,382,499,1145, [id].vue:69,286), admin alerts (server/utils/adminAlerts.js:22,100-116, server/models/adminAlertDismissal.js:6), and a data migration to flip existing pending_payment rows to active.
• Larger refactor — break out into its own ticket once B1 lands.

B4. Admin "Pending Payment" filter label (cosmetic)

• app/pages/admin/members/index.vue:45,499, [id].vue:69 show pending_payment as "Pending Payment". If B3 removes the status entirely, this disappears too. If we keep pending_payment for now, rename in admin UI to "Payment setup incomplete" so admins also stop conflating it with membership state.

---

Post-launch backlog

See docs/TODO.md for:

• Button minimum target size (WCAG AAA 2.5.5).
• /oidc/interaction/[uid] routing quirk.
• Admin layout migration from guild-* tokens to zine spec.
• Admin dashboard quick-action button contrast.
• Members table NAME column clipping.
• OWASP ASVS L1 Phase 4 (file-upload validation pipeline, granular RBAC, credential encryption).
• tickets/available.get.js:115 memberSavings block reports $0 saved for inactive members — cosmetic; suppress comparison block when !hasMemberAccess(member) if it ever surfaces in UI.

Known gotchas worth addressing post-launch

• Subscription cache fed wrong field on CREATE. subscription.post.js and update-contribution.post.js read subscription.nextBillingDate from Helcim's CREATE response, but Helcim returns dateBilling. The lazy refresh in subscription.get.js masks this (handles both shapes), so next-charge rendering works — but the cache starts empty. Fix at the CREATE sites so the cache is correct from first write.
• Admin edit does not sync Helcim recurringAmount. /admin/members/[id] PUT writes contributionAmount direct to Mongo by design. Admins must PATCH Helcim manually. Worth surfacing in admin UI or docs.
• Cadence switch rejected on active subscriptions. update-contribution.post.js:184-189 refuses cadence changes mid-subscription; no UI toggle exists on /member/account. Adding cadence switch would require a Helcim subscription replacement flow, not a plain update.
• SeriesPassPurchase.vue doesn't auto-refresh after purchase. (Observed 2026-04-21 during Phase 4 series-pass functional tests.) Component's local $fetch to /api/series/{id}/tickets/available fires on mount + userEmail watch, but isn't re-invoked after a successful purchase — the "already registered" state only appears on next navigation. Parent page calls refreshNuxtData() but the component doesn't participate in it. Fix: call fetchPassInfo() after the success toast in handleSubmit, or lift the fetch to useAsyncData so it can be refreshed from outside.
• S2 test fixture id/slug inconsistency. (Local dev only.) Seeded S2 series has id: 'test-s2-drop-in-allowed' but slug: 'test-s2-drop-in-allowed-series'. Doesn't affect prod — fix the seed script if anyone re-runs fixtures and is confused why id-based Mongo queries return empty.

Events-surface visual audit — deferred items (2026-04-21)

Context: Phase 4 audit against docs/specs/events-visual-audit-findings.md fixed all critical phantom-palette, rounded-corner, CTA-mismatch, and input-styling issues across EventTicketCard, EventTicketPurchase, EventSeriesTicketCard, SeriesPassPurchase. Items below were explicitly deferred or out of reach.

• Success-state color convention (4 instances). "You're Registered!" blocks use --candle (gold) instead of --green. Touches EventSeriesTicketCard.vue:186-196 (still uses phantom candlelight-* classes — preserved byte-for-byte pending decision) and registered-state wrappers in SeriesPassPurchase.vue. Needs a UX call on whether success should render gold (zine-consistent) or green (semantic). Once decided, finish the phantom-palette removal on those 4 lines.
• Sidebar breakpoint unverified. app/layouts/default.vue:89 hides the sidebar at ≤1024px per spec. Browser resize_window tool refused viewport changes during the audit, so the actual crossover and any layout shift at 1023–1025px was never visually confirmed. Do a manual responsive check before declaring the sidebar pattern shipped.
• EventTicketPurchase.vue:469 magic padding. .consent-hint { padding-left: 24px; } is a hardcoded offset to align the hint under the checkbox text. Cosmetic; swap for a gap/grid approach when touching the consent block next.
• Toast API rename unverified. Nuxt UI v4 may have renamed toast.add({ timeout }) → { duration }. Current SeriesPassPurchase.vue toasts still pass timeout. No visible breakage, but worth confirming against current Nuxt UI docs.
• .section-label extraction candidate. Several audited files repeat the same uppercase/letter-spaced small label pattern inline. Low-priority refactor into a utility class in main.css.
• Past-events toggle component. Existing, untouched this pass; noted in findings doc as a future consistency check.

Contribution-amount redesign — cosmetic cleanup (naming only, not behavior)

• Rename admin members column header "Tier" → "Contribution" (app/pages/admin/members/index.vue:265).
• Delete dead app/components/TierPicker.vue.
• Update stale tier comment in app/composables/useMemberPayment.js:59.
• Update error log message referencing "tier" in server/api/members/update-contribution.post.js:221.
• Rename handleUpdateTier handler in app/pages/member/account.vue.