fix(rivetkit): remove deprecated actor options

Author: NathanFlurry

examples/experimental-durable-streams-ai-agent-vercel/src/actors.ts

@@ -7,7 +7,7 @@
 
 ## Sleep state invariants
 
-- Any mutation that changes a `can_sleep` input must call `ActorContext::reset_sleep_timer()` so the `ActorTask` sleep deadline is re-evaluated. Inputs are: `ready`/`started`, `no_sleep`, `active_http_request_count`, `sleep_keep_awake_count`, `sleep_internal_keep_awake_count`, `pending_disconnect_count`, `conns()`, and `websocket_callback_count`. Missing this call leaves the sleep timer armed against stale state and triggers the `"sleep idle deadline elapsed but actor stayed awake"` warning on the next tick.
+- Any mutation that changes a `can_sleep` input must call `ActorContext::reset_sleep_timer()` so the `ActorTask` sleep deadline is re-evaluated. Inputs are: `ready`/`started`, `active_http_request_count`, `sleep_keep_awake_count`, `sleep_internal_keep_awake_count`, `pending_disconnect_count`, `conns()`, and `websocket_callback_count`. Missing this call leaves the sleep timer armed against stale state and triggers the `"sleep idle deadline elapsed but actor stayed awake"` warning on the next tick.
 - Runtime-owned promises that must drain during shutdown should use `ActorContext::register_task(...)`, not public `wait_until(...)`, so metrics and runtime intent stay distinct. Registered tasks must race user work against `shutdown_deadline_token()` so shutdown cannot hang forever.
 - `ctx.sleep()` and `ctx.destroy()` return `Result<()>`. They error with `ActorLifecycleError::Starting` when called before startup completes and `ActorLifecycleError::Stopping` if the requested flag has already been set this generation (atomic `swap(true, ...)`). Internal idle-timer paths log and suppress the already-requested error.
 - The grace deadline path (`on_sleep_grace_deadline`) aborts the user `run` handle and cancels `shutdown_deadline_token()`. Foreign-runtime adapters running `onSleep` / `onDestroy` must observe that token via `tokio::select!` so SQLite teardown does not race user cleanup work.

examples/experimental-durable-streams-ai-agent/src/index.ts

@@ -74,7 +74,6 @@ pub struct ActorConfig {
 	pub on_migrate_timeout: Duration,
 	pub action_timeout: Duration,
 	pub sleep_timeout: Duration,
-	pub no_sleep: bool,
 	pub sleep_grace_period: Duration,
 	pub sleep_grace_period_overridden: bool,
 	pub connection_liveness_timeout: Duration,
@@ -109,7 +108,6 @@ pub struct ActorConfigInput {
 	pub on_migrate_timeout_ms: Option<u32>,
 	pub action_timeout_ms: Option<u32>,
 	pub sleep_timeout_ms: Option<u32>,
-	pub no_sleep: Option<bool>,
 	pub sleep_grace_period_ms: Option<u32>,
 	pub connection_liveness_timeout_ms: Option<u32>,
 	pub connection_liveness_interval_ms: Option<u32>,
@@ -160,9 +158,6 @@ impl ActorConfig {
 		if let Some(value) = config.sleep_timeout_ms {
 			actor_config.sleep_timeout = duration_ms(value);
 		}
-		if let Some(value) = config.no_sleep {
-			actor_config.no_sleep = value;
-		}
 		if let Some(value) = config.sleep_grace_period_ms {
 			actor_config.sleep_grace_period = duration_ms(value);
 			actor_config.sleep_grace_period_overridden = true;
@@ -224,7 +219,6 @@ impl Default for ActorConfig {
 			on_migrate_timeout: DEFAULT_ON_MIGRATE_TIMEOUT,
 			action_timeout: DEFAULT_ACTION_TIMEOUT,
 			sleep_timeout: DEFAULT_SLEEP_TIMEOUT,
-			no_sleep: false,
 			sleep_grace_period: DEFAULT_SLEEP_GRACE_PERIOD,
 			sleep_grace_period_overridden: false,
 			connection_liveness_timeout: DEFAULT_CONNECTION_LIVENESS_TIMEOUT,