fix(client): flatten skipReadyWait option

[NathanFlurry]

Stack Context

This stack updates the RivetKit client API and docs around gateway readiness bypass behavior.

Why?

The skip ready wait option was documented as a nested per-call gateway option. This PR flattens the per-call shape to skipReadyWait: true and updates docs, examples, and tests to match.

[NathanFlurry]

• fix(pegboard): align drain grace defaults with stop threshold #4958 : 2 dependent PRs (#4960 , #4966 )
• fix(rivetkit): preserve bridge error messages #4959
• fix(rivetkit): fire abort signal on shutdown finalize #4957
• fix(rivetkit): use startup kv preload #4956
• fix(client): flatten skipReadyWait option #4955 👈 (View in Graphite)
• ci(publish): add manual preview publish flow #4954
• fix(depot): add ltx decode diagnostics #4953
• fix(universaldb): preserve plain set values #4952
• fix(universaldb): align versionstamp operand encoding #4951
• fix(rivetkit): export database provider types #4950
• wip: kitchen sink agentic loop finish #4949
• chore(rivetkit): note duplicate admission logic #4948
• test(rivetkit): cover bypass fetch header forwarding #4947
• feat(kitchen-sink): add actor probe controls #4946
• fix(gateway): split actor response wait errors #4945
• fix(guard): handle bypass preflight before query parse #4944
• feat(kitchen-sink): add mock agent event log copy #4943
• fix(kitchen-sink): default mock agent to local endpoint #4942
• test(rivetkit): enable driver lifecycle regressions #4941
• test(rivetkit): verify cached websocket db refs exceed grace #4940
• fix(rivetkit-core): keep sleeping actors reachable during grace #4939
• test(rivetkit): cover async websocket close db access #4938
• fix(rivetkit): keep actors awake until keepAwake work finishes #4937
• fix(rivetkit): persist native onSleep state on errors #4936
• fix(rivetkit-core): allow dispatch during sleep grace #4935
• fix(rivetkit): make duplicate sleep requests idempotent #4934
• main

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

[claude]

PR Review: fix(client): flatten skipReadyWait option

Summary: This PR renames bypassConnectable to skipReadyWait throughout the stack and flattens the per-call option from nested gateway.skipReadyWait to top-level skipReadyWait. The change touches Rust guard routing, TypeScript client options, wire headers/protocols, docs, and tests.

---

Positives

• Better naming. bypass_connectable was an internal implementation detail; skip_ready_wait describes the user-visible behavior accurately.
• Improved header validation. The old code treated header presence as true; the new read_skip_ready_wait_header parses true/false/1/0 and returns a typed guard.invalid_header error for anything else.
• TODO resolved. The ParsedActorPath::Direct arm previously hardcoded false with a // TODO: comment. It now calls read_skip_ready_wait_for_path_based correctly.
• isPathOrQuery fix. canUseDirectBypassPath used strict equality and would miss /connect?room=lobby. The new helper handles query-string paths.
• Token in WebSocket protocols. buildWebSocketProtocols had an unused _runConfig param; the fix threads the token into protocols when a target is present. A new test exercises this.
• Comprehensive rename. Wire headers, WebSocket subprotocols, query params, TypeScript consts, Rust field names, docs, and examples are all updated consistently.

---

Issues

1. Missing trailing newline in artifact file

engine/artifacts/errors/guard.invalid_header.json is missing a trailing newline. Other files in that directory end with a newline.

2. Breaking wire-protocol change

The HTTP header, WebSocket subprotocol, and query param are all renamed. Old clients talking to new servers (or vice versa) will silently lose the flag. If mixed deployments are possible, reading both names in the guard during a transitional window would be safer.

3. Redundant type aliases

After the change, ActorConnectOptions, ActorWebSocketOptions, and ActorGatewayOptions are all structurally identical. Worth a conscious decision on whether distinct names add clarity.

4. ActorFetchInit extra key in RequestInit contexts

The new type ActorFetchInit = RequestInit & ActorGatewayOptions is correct for destructuring in actor-handle.ts. However, consumers passing an ActorFetchInit where a plain RequestInit is expected will carry an extra skipReadyWait key. Mostly harmless but worth noting.

---

Nits

• parse_skip_ready_wait_bool in pegboard_gateway/mod.rs overlaps with the parse_query_bool helper inside extract_rvt_params. Consider consolidating.
• If .agent/notes/driver-test-progress.md tracked the old test file gateway-bypass-client.test.ts, update it to match the renamed file.

---

Verdict

Clean and well-executed. Fix the missing trailing newline in the JSON artifact, and add a note in the PR description about the wire-protocol break for operators doing rolling deployments.