chore: fix bad rivetkit merge

[MasterPtato]

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

[MasterPtato]

This change is part of the following stack:

• chore: fix bad rivetkit merge #4404 ◀

_{Change managed by git-spice.}

[railway-app]

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

Service	Status	Web	Updated (UTC)
website	🕒 Building (View Logs)	Web	Mar 11, 2026 at 7:35 pm
frontend-inspector	🕒 Building (View Logs)	Web	Mar 11, 2026 at 7:35 pm
frontend-cloud	🕒 Building (View Logs)	Web	Mar 11, 2026 at 7:35 pm
ladle	🕐 Initializing (View Logs)	Web	Mar 11, 2026 at 7:35 pm
mcp-hub	🕐 Initializing (View Logs)	Web	Mar 11, 2026 at 7:35 pm