Lock SwiftFlow stable v1 release scope

[aliihsaad]

What changed

• froze the canonical stable-v1 scope as Instagram-only engagement automation on Vercel + managed Supabase
• replaced the stale transformation roadmap and feature matrix
• added a release checklist and managed-operations runbook
• added GitHub Actions gates for tests, lint, and production build
• removed a stale HTTP-node claim and cleared the existing lint-warning baseline

Why

The product implementation is complete enough to enter release closure, but the repository still described removed Facebook, publishing, scheduling, billing, and self-hosting paths and did not enforce release gates in CI.

Validation

• npm run test:ci — 78 files, 554 tests passed
• npm run lint — zero errors and warnings
• npm run build — passed with Next.js 16.2.12
• npm run setup:check — repository checks passed; external completion still requires the project-owner Supabase CLI session and local INVITE_EMAIL_FROM

Impact

No new product feature is added. This PR creates the stable-v1 feature freeze and makes the remaining clean deployment, production acceptance, recovery rehearsal, and seven-day soak explicit and measurable.

Summary by CodeRabbit

• Documentation

  • Defined the stable v1 product scope, supported deployment model, feature matrix, and release criteria.
  • Added operational guidance for monitoring, incident response, token recovery, backups, credential rotation, and rollback procedures.
  • Updated supported automation capabilities to focus on Instagram engagement workflows.

• Chores

  • Added automated validation for pull requests and master branch changes, including tests, linting, and production builds.
  • Improved linting feedback for unused variables while allowing intentionally ignored identifiers.
  • Removed obsolete internal configuration.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
social-media-manager-ai	Ready	Preview	Aug 14, 2026 10:57am

[coderabbitai]

Warning

Review limit reached

@aliihsaad, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 89a8d995-6f2a-4d17-b7dd-45b5ff736e13

📥 Commits

Reviewing files that changed from the base of the PR and between 6427a33 and a45b93a.

⛔ Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• app/api/webhooks/instagram/route.ts
• docs/release/stable-v1-release-checklist.md
• package.json

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 7f186639-9ee0-42c4-b219-96fdcea355e7

📥 Commits

Reviewing files that changed from the base of the PR and between 623745a and 6427a33.

📒 Files selected for processing (8)

• .github/workflows/ci.yml
• README.md
• docs/release/stable-v1-operations.md
• docs/release/stable-v1-release-checklist.md
• docs/superpowers/plans/2026-07-28-automation-first-managed-supabase-roadmap.md
• docs/transformation/stable-v1-feature-matrix.md
• eslint.config.mjs
• supabase/functions/sync-analytics/index.ts

---

📝 Walkthrough

Walkthrough

The change locks the stable-v1 product scope and deployment model, adds release and operations documentation, introduces CI validation, updates ESLint rules, and removes unused analytics declarations.

Changes

Stable-v1 release

Layer / File(s)	Summary
Stable-v1 product contract docs/transformation/stable-v1-feature-matrix.md, docs/superpowers/plans/..., README.md	Defines the locked Instagram-only scope, supported Vercel and managed Supabase deployment, architecture, capabilities, exclusions, and release-change policy.
Release closure and operations docs/release/stable-v1-release-checklist.md, docs/release/stable-v1-operations.md, docs/superpowers/plans/...	Defines deployment rehearsal, production acceptance, recovery, rollback, monitoring, soak, and final release gates.
CI and code-quality checks .github/workflows/ci.yml, eslint.config.mjs, supabase/functions/sync-analytics/index.ts	Adds pull request and master CI runs for installation, tests, linting, and builds. Configures unused-variable warnings and removes unused Meta Graph declarations.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Merge Risk: ⚪ Minimal · up to 6427a

This PR documents the stable-v1 scope and adds release controls without introducing a product feature; no actionable merge-blocking risk remains after normal checks and review.

---

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 Pro by visiting https://app.coderabbit.ai/login.

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