fix(rivetkit): remove deprecated actor options

[NathanFlurry]

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

[NathanFlurry]

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

• fix(rivetkit): preserve internal bridge errors #4993
• fix(rivetkit): remove deprecated actor options #4992 👈 (View in Graphite)
• fix(rivetkit): fix default spawn engine behavior #4989
• chore: fix compile warnings #4988
• fix: compile wasm vs native features with custom cfg to prevent dupe features #4982
• chore: remove setPreventSleep #4981
• main

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

[claude]

Code Review: fix(rivetkit): remove deprecated actor options

Overview

This PR removes deprecated actor options (noSleep, onDestroyTimeout, waitUntilTimeout) across the full stack — Rust core, NAPI bridge, WASM bridge, TypeScript schemas, JSON artifact, examples, and test fixtures. It replaces noSleep: true with the scoped c.keepAwake(promise) API.

The removal is clean and consistent across all layers. Overall this is a straightforward, well-executed cleanup.

---

Issues

start-stop-race.ts: noSleep: true replaced with sleepTimeout: 60_000 is a fragile substitute

noSleep: true was semantically never sleep. The replacement just defers sleep to 60 seconds, meaning any test that runs longer than that will see unexpected onSleep/onWake calls and potentially flake. The correct replacement is c.keepAwake(...) inside the actor body (e.g. a never-resolving promise in onWake), not a wall-clock workaround. At minimum this deserves a comment explaining the intent so the next person does not just bump the timeout when it flakes.

actor-config.json is missing a trailing newline

The diff ends with no newline at end of file. The artifact should be regenerated with a final newline for consistency.

WasmServeConfig additions are unrelated to this PR's stated purpose

Five new fields (envoy_key, dev_serverless_url, dev_serverless_manual, dev_serverless_drain_timeout, dev_serverless_request_timeout) were added to WasmServeConfig in rivetkit-wasm/src/lib.rs. These have nothing to do with removing deprecated actor options. They add public API surface without documentation or tests in this diff. If they are needed because this branch is stacked on other work, they should be called out in the PR description.

---

Minor nits

• The PR checklist is blank. This removes previously-deprecated but still-functional API surface, so the Breaking change box should be checked.
• The CanSleep::NoSleep variant removal in sleep.rs is correct. The CLAUDE.md update dropping no_sleep from the can_sleep inputs list is consistent with the removal.

---

Positives

• All layers are updated atomically: Rust core, NAPI, WASM, TypeScript schema, JSON artifact, examples, and driver fixtures. No dangling references.
• The new rejects removed actor option test correctly verifies that passing old option names throws at parse time rather than being silently ignored.
• The keepAwake migration in the AI agent examples is correct. c.keepAwake(consumeStream(c)) properly registers the async operation to block sleep for the lifetime of the stream consumer.
• Removing the warnDeprecatedShutdownTimeoutKeys runtime warning path is a clean finish to the deprecation cycle.