fix(frontend): getRivetRunUrl import

[abcxff]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-5176 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
ladle	✅ Success (View Logs)	Web	Jun 5, 2026 at 8:49 pm
frontend-cloud	✅ Success (View Logs)	Web	Jun 5, 2026 at 8:49 pm
kitchen-sink	❌ Build Failed (View Logs)	Web	Jun 5, 2026 at 8:48 pm
mcp-hub	✅ Success (View Logs)	Web	Jun 5, 2026 at 8:48 pm
website	✅ Success (View Logs)	Web	Jun 5, 2026 at 8:48 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Jun 5, 2026 at 8:47 pm

[abcxff]

• fix(frontend): getRivetRunUrl import #5176 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Code Review

Summary: This PR fixes a missing import for getRivetRunUrl that would have caused a ReferenceError at runtime. The ternary reformatting is also a nice readability improvement.

Issue: Duplicate import from the same module

The new import uses a relative path while the existing import from the same file already uses the @/ alias. Both resolve to the same file (frontend/src/lib/env.ts). The fix should consolidate these into a single import:

Existing: import { cloudEnv } from "@/lib/env";
New: import { getRivetRunUrl } from "../lib/env";

Should be: import { cloudEnv, getRivetRunUrl } from "@/lib/env";

This matches the @/ alias convention used by every other import in this file and avoids two separate imports from the same module.

Everything else looks good - the bug fix is real (missing import would throw at runtime) and the ternary reformatting improves readability with no behavior change.