chore: flatten runtime config

[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

[railway-app]

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

Service	Status	Web	Updated (UTC)
frontend-cloud	😴 Sleeping (View Logs)	Web	Feb 28, 2026 at 8:56 pm
website	😴 Sleeping (View Logs)	Web	Feb 28, 2026 at 8:44 pm
frontend-inspector	😴 Sleeping (View Logs)	Web	Feb 27, 2026 at 11:55 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 27, 2026 at 11:48 pm
ladle	❌ Build Failed (View Logs)	Web	Feb 27, 2026 at 11:47 pm

[MasterPtato]

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: bump rivetkit protocol version #4329
• fix(udb): add txn tagging #4328
• fix(api): make actor destroy wait for ack #4327
• chore: flatten runtime config #4326 👈 (View in Graphite)
• chore: deploy patch #4324
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

[claude]

Code Review

This PR flattens the nested Worker and Gasoline sub-structs within Runtime into a flat structure with prefixed field names. The refactoring is clean and all logic is correctly preserved. A few things worth flagging:

Breaking Change (needs documentation)

This is a breaking configuration change for anyone using the runtime.worker.* or runtime.gasoline.* config keys. The migration required is:

# Before
runtime:
  worker:
    cpu_max: 2000
    shutdown_duration: 60
  gasoline:
    prune_eligibility_duration: 604800

# After
runtime:
  worker_cpu_max: 2000
  worker_shutdown_duration: 60
  gasoline_prune_eligibility_duration: 604800

The PR description checklist item for "Breaking change" is unchecked, and there's no migration note. Since serde(deny_unknown_fields) is present on the struct, old configs will fail to deserialize silently rather than giving a helpful error message.

Docs Not Updated

Per CLAUDE.md, config changes should update website/src/content/docs/self-hosting/configuration.mdx. If the runtime config structure is documented there, it should reflect the new flat field names. (Grep shows no current references to worker/gasoline in that file, so this may be a non-issue if those fields aren't documented yet, but worth verifying.)

Minor: Field Visibility Consistency

worker_cpu_max is pub while worker_load_shedding_curve and worker_shutdown_duration are private — this mirrors the original Worker struct where cpu_max was the only pub field. The access pattern in gasoline/src/db/kv/mod.rs uses self.config.runtime.worker_cpu_max directly. This is consistent with prior behavior, but it's slightly odd to have only one public field when the others follow the accessor method pattern. Not a blocker, just a note.

PR Description

The PR description is empty — no summary of motivation or testing notes. Would help reviewers understand why flattening is preferred here over the nested approach.

---

Overall the implementation is correct and the refactoring is complete (no stale references to the old paths remain). Main ask is to document the breaking change for existing self-hosters.

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• example-elysia
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4326

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4326

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4326

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4326

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4326

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4326

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4326

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4326

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4326

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4326

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4326

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4326

commit: 044fcdb

[MasterPtato]

This change is part of the following stack:

• chore: deploy patch #4324
  • chore: flatten runtime config #4326 ◀
    • fix(api): make actor destroy wait for ack #4327
      • fix(udb): add txn tagging #4328
        • chore: bump rivetkit protocol version #4329

_{Change managed by git-spice.}