Skip to content

docs(launch): DNS/email corrections, Preview login, PhonePe note, release packet (S3b–d, S5) - #43

Merged
Satelink-Protocol merged 1 commit into
launch-mvpfrom
docs/s3-launch-runbooks
Nov 10, 2026
Merged

Satelink-Protocol merged 1 commit into
launch-mvpfrom
docs/s3-launch-runbooks

Conversation

@Satelink-Protocol

Copy link
Copy Markdown
Contributor

Docs only (S2.4, S3b, S3c, S3d, S5). No code changes.

File Change
docs/launch/DNS_AND_EMAIL_ROUTING.md S3b. The Vercel records are DNS-only (grey cloud): apex A + www CNAME using the values from Vercel → Settings → Domains, and a www → apex 308 configured in Vercel. The proxied / Full (Strict) / Cloudflare redirect-rule steps are removed. DMARC starts at p=none + rua, with a documented path to quarantine and then reject once real senders align. It now states plainly that Cloudflare Email Routing cannot send or reply from the domain, and lists the real options (Email Sending is Workers Paid beta; Gmail "send as" doesn't align with DMARC; a DKIM-signing provider is recommended). Each claim cites current docs: Vercel set-up-custom-domain and the Vercel KB "Using Cloudflare and other reverse proxies with Vercel" (updated 2026-10-19, "Use DNS-only mode for direct traffic"); Cloudflare Email Service Postmaster known limitations, the email-authentication deployment strategy, and the DNS Google Workspace DMARC guidance.
docs/launch/PREVIEW_LOGIN.md (new) S3c. Two bots: the test bot is bound to strangersmeetup-git-launch-mvp-jakuraa.vercel.app, the production bot to nightlifez.com. Lists the exact env names the code reads (PREVIEW_TELEGRAM_BOT_TOKEN, Preview-scoped TELEGRAM_BOT_USERNAME / TELEGRAM_LOGIN_CLIENT_ID/SECRET, PREVIEW_PUBLIC_SITE_URL, SESSION_SECRET, ADMIN_BOOTSTRAP_TELEGRAM_ID) and the owner steps. Key finding: without PREVIEW_PUBLIC_SITE_URL, the OIDC callback uses the per-deployment VERCEL_URL and can never match the bot's domain.
docs/UPI_PROVIDER_READINESS.md S3d. New §8 recording that the "currency must appear in the provider payload" rule makes PhonePe v1 auto-confirmation impossible by design. If PhonePe ever onboards, derive INR from the signed merchant contract and config, and revisit the rule then. No code change.
docs/launch/PRODUCTION_RELEASE_PACKET.md (new) S5. Migrations 010–020 with the ones that touch existing rows (010 CHECK swap, 012 backfills, 014 UPDATE, 019 tickets backfill) and read-only pre-checks; the Gate 3 procedure; Production env names; release and rollback steps.
docs/PROJECT_STATE.md S2.4. Real SHAs after the #41 consolidation, the superseded-PR table with archive tags, migrations per environment (local 003–020 / Preview 003–020 per the 771f6e1 build log / Production believed 009, unconfirmed), and the owner gates (new: Preview env vars).

🤖 Generated with Claude Code

…ePe currency note, release packet

- DNS_AND_EMAIL_ROUTING: Vercel records DNS-only (grey cloud), apex A +
  www CNAME from Vercel Settings > Domains, www -> apex redirect in
  Vercel; drop proxied/Full (Strict) steps. DMARC starts at p=none with
  rua, then quarantine, then reject. Email Routing is receive/forward
  only; "send as" options stated. Cites current Vercel and Cloudflare docs.
- PREVIEW_LOGIN (new): test bot bound to the launch-mvp branch alias,
  production bot to nightlifez.com; exact env names the code reads.
- UPI_PROVIDER_READINESS: note that the payload-currency rule makes
  PhonePe v1 confirmations impossible by design; revisit if onboarded.
- PRODUCTION_RELEASE_PACKET (new): migrations 010-020 and which touch
  existing rows, Gate 3 procedure, Production env names, release and
  rollback steps.
- PROJECT_STATE: consolidation SHAs, superseded PRs, migrations per
  environment, owner gates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
strangersmeetup Ready Ready Preview Nov 10, 2026 9:58am UTC

@Satelink-Protocol
Satelink-Protocol merged commit 8edb778 into launch-mvp Nov 10, 2026
3 checks passed
@Satelink-Protocol
Satelink-Protocol deleted the docs/s3-launch-runbooks branch November 10, 2026 10:07
Satelink-Protocol added a commit that referenced this pull request Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant