chore: regenerate sdk

[jog1t]

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

[jog1t]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [slop]feat(frontend): enable compute, add historical logs #5059
• chore: regenerate sdk #5036 👈 (View in Graphite)
• feat(frontend): allow creating serverfull instances during onboarding #5035
• feat(frontend): add provider icons #5034
• refactor(forntend): improve providers table #5033
• fix(frontend): missing provider configuration right after adding it #5032
• refactor(frontend): datacenter aware provider configuration #5031
• feat(frontend): allow local->staging tunnel in dev #5030
• refactor(frontend): better gateway errors #5029
• feat(frontend): rbac token notice for the engine #5028
• fix(frontend): build ladle correctly #5027
• feat(frontend): improve runners errors ui #5026
• fix(frontend): 404 navigation issues #5025
• fix(frontend): ns aware navigation #5024
• fix(frontend): navigate only by using actor ids #5023
• feat(frontend): add serverless check when editing the runner config #4961 : 1 other dependent PR (#4964 )
• main

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

[claude]

Code Review: PR 5036

Three small frontend fixes - all targeted and correct.

1. getting-started.tsx - publishable token fallback

Correct fix. usePublishableToken() returns null for Enterprise/OSS deployments without a platform API. Without this fallback, buildRivetAgentInstructionsCode would embed the literal string 'null' into the generated shell snippet. The placeholder '<PUBLISHABLE_TOKEN>' is clear and consistent with other placeholder patterns in the codebase.

2. serverless-connection-check.tsx - new provider labels

Correct fix. Both cloudflare-workers and supabase-functions exist in deployOptions in frontend/packages/shared-data/src/deploy.ts and are part of the Provider union type. Without these arms, the ts-pattern .exhaustive() call would be a compile error (or runtime throw) when either provider was passed. The label strings match the displayName values in deployOptions. No inconsistency.

3. actors-list.tsx - useEffect rowVirtualizer.measure()

Functionally reasonable as a defensive measure to recalculate row sizes after mount.

Minor concern - dependency stability: useVirtualizer returns the same stable object reference across renders (it is a class instance). The [rowVirtualizer] dependency should therefore fire only once on mount, which is the intent. Worth confirming the reference is stable in the version in use; if it is not, this could fire on every render.

Minor concern - intent clarity: If the goal is mount-only, an empty [] dependency array would be more explicit. Using [rowVirtualizer] is not wrong, but it slightly obscures whether this is meant to track instance changes or just run once.

Suggestion: Add a brief comment explaining why an explicit measure() call is needed (e.g. dynamic row heights). Per project conventions, one short line is enough - the why is non-obvious here.

Assessment

All three changes are correct. No security issues, no regressions in error handling, no missing match arms. The only nit is the missing explanatory comment on the useEffect in actors-list.tsx.