fix(infra): route staging via host port (drop tunnel network attach)

[LucasSantana-Dev]

Follow-up to #1547. The deploy-staging.sh step that attached lucky-tunnel to the staging network made the nginx service alias ambiguous between prod and staging — a latent risk of misrouting production traffic, and the cause of the staging 502.

Verified the tunnel's network reaches the staging nginx host port directly (100.95.204.103:8093 → HTTP 200), which is collision-free and what docs/STAGING.md already specifies. This drops the network-attach; the tunnel ingress points at the host port instead.

(Prod was confirmed healthy throughout; the tunnel has been disconnected from the staging network.)

---

Summary by cubic

Route staging traffic through the nginx host port instead of attaching lucky-tunnel to the staging Docker network. This removes the prod/staging nginx name collision, fixes the staging 502, and matches docs.

• Bug Fixes
  • Removed lucky-tunnel → staging network connect in scripts/deploy-staging.sh.
  • Staging ingress uses 100.95.204.103:8093 (host port), keeping production isolated.

^{Written for commit af6a2f1. Summary will update on new commits.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
lucky	Ready	Preview, Comment	Jun 23, 2026 6:04pm

[coderabbitai]

Warning

Review limit reached

@LucasSantana-Dev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 28 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 03bd6efd-8ed1-4417-804d-beb0aae684c5

📥 Commits

Reviewing files that changed from the base of the PR and between c15fa38 and af6a2f1.

📒 Files selected for processing (1)

• scripts/deploy-staging.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/staging-routing

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Failed to generate code suggestions for PR

[cubic-dev-ai]

No issues found across 1 file

<sub>Requires human review: This change modifies the staging deployment script which controls production infrastructure routing. Any misconfiguration here could impact production traffic, so it requires human review to ensure correctness.

Re-trigger cubic</sub>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud