fix(frontend): build ladle correctly

[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

• chore: regenerate sdk #5036
• 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 👈 (View in Graphite)
• 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]

PR Review

What the PR does: Adds missing COPY of rivetkit-wasm package to all three frontend Dockerfiles (cloud, inspector, ladle) and sets SKIP_WASM_BUILD=1 to avoid invoking wasm-pack (which needs a Rust toolchain not present in these images).

Assessment: Fix is correct and minimal. SKIP_WASM_BUILD is properly consumed in rivetkit-wasm/scripts/build.mjs — it checks for '1' or 'true' and exits early. Since no pre-built pkg/ artifacts are committed, the build logs 'skipped', which is fine because Vite/esbuild does not run tsc type-checking; the package just needs to be present for pnpm install to succeed. The change is applied consistently across all three Dockerfiles, SKIP_WASM_BUILD=1 is correctly placed before pnpm install, and the variable is already in turbo.json passthrough env so cache keys include it.

No blocking issues.

Minor notes:

• PR title says 'build ladle correctly' but all three Dockerfiles are changed. A more accurate title: fix(frontend): add rivetkit-wasm to docker build contexts.
• Dockerfile comment style: uses a semicolon to join two sentences. Per CLAUDE.md, separate sentences with a period.
• SKIP_NAPI_BUILD is not needed here because rivetkit-napi is not COPY'd into these images. This is correct.

Conclusion: Good, targeted fix. Safe and consistent across all three images.