[Programcode]

What

The Rollback section said "promote the previous known-good Vercel deployment" but not how. It now gives:

• the Vercel project name (debate-navigator);
• how to see the live deployment and the earlier ones (vercel inspect, vercel ls);
• the rollback command (vercel rollback <url> --yes), about 10 seconds;
• the one-command helper on Adam's VPS (~/ops/rollback/rollback vercel debate-navigator);
• the catch: after a rollback Vercel stops auto-promoting main until a deployment is promoted with vercel promote;
• a reminder that a frontend rollback leaves Supabase as it is.

Checks

• node scripts/check-docs.mjs passes.
• vercel-status dry run of the helper shows the live and previous production deployments correctly. No rollback was executed.

Docs only; no code or config changes.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified frontend rollback steps, including how to inspect deployments and roll back to a previous one.
  • Noted that a rollback must be followed by promoting a deployment before new changes go live, and does not undo Supabase changes.

[vercel]

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

Project	Deployment	Actions	Updated
debate-navigator	Ready	Preview	Oct 2, 2026 2:36pm UTC

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: c1be173b-50bf-44c4-944a-432fb465c82c

📥 Commits

Reviewing files that changed from the base of the PR and between d68e9c8 and 8ba6d26.

📒 Files selected for processing (1)

• docs/operations.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The frontend rollback instructions now include Vercel deployment commands and explain how rollback affects future deployments and Supabase.

Changes

Frontend rollback

Layer / File(s)	Summary
Vercel rollback guidance docs/operations.md	The guide adds commands to inspect, list, and roll back Vercel deployments. It states that a deployment must be promoted before new main deployments go live, and that frontend rollback does not revert Supabase changes.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Architecture Summary

Architecture risk: 🔵 Low · up to 8ba6d

The change affects 1 system.

Changed systems: docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — docs (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in docs/operations.md: The frontend rollback guidance adds Vercel inspection, listing, rollback, and VPS helper commands; it also states that after rollback a deployment must be promoted to resume live main deployments, and that rolling back the frontend leaves Supabase unchanged.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

_{Comment @coderabbitai help to get the list of available commands.}