fix(rivetkit): configure inspector protocol versions

[NathanFlurry]

No description provided.

[NathanFlurry]

Stack for rivet-dev/rivet

• #5452 refactor(rivetkit): expose schedule intervals as durations
• #5450 perf(rivetkit): index named queue reads
• #5449 refactor(rivetkit): use unitless schedule duration names
• #5451 perf(rivetkit): bound queue reads and history pruning
• #5448 refactor(rivetkit): collapse unpublished internal schema
• #5446 refactor(rivetkit): centralize internal sqlite storage
• #5445 test(rivetkit): simplify sqlite efficiency coverage
• #5443 perf(rivetkit): verify and optimize internal sqlite queries
• #5427 fix(rivetkit): clean up cron history efficiently
• #5439 docs(rivetkit): remove redundant overdue schedule note
• #5440 docs(rivetkit): use scheduling code snippets
• #5442 fix(rivetkit): configure inspector protocol versions 👈
• #5441 feat(rivetkit): add actor scheduling
• main

Get stack: forklift get 5442
Push local edits: forklift submit
Merge when ready: forklift merge 5442

_{change kupzounm}

[claude]

Review

Small, well-scoped fix. I traced the negotiation logic end-to-end (Rust inspector_ws.rs, TS client.browser.ts, actor-inspector-context.tsx, and the driver test) and it's internally consistent:

• Rust inspector_wire_mode_from_path treats a missing protocol_version query param as LegacyEmbeddedV5 (pinned to v5, embedded-in-payload framing) and a present param as Negotiated { version } (out-of-band version, no embedded header). LEGACY_INSPECTOR_VERSION = 5 matches MIN_RIVETKIT_VERSION_SCHEDULES / MIN_RIVETKIT_VERSION_INSPECTOR_NEGOTIATION both being 2.3.4 in the frontend, so schedules (v6) and negotiation land together and the legacy path correctly gates out SchedulesUpdated/SchedulesResponse/etc. via supports_schedules().
• The driver test previously built the WS URL without protocol_version and used serializeWithEmbeddedVersion/deserializeWithEmbeddedVersion, which would have driven the server into the legacy v5 path. Switching to protocol_version: String(INSPECTOR_PROTOCOL_VERSION) on the URL plus plain serialize/deserialize(payload, INSPECTOR_PROTOCOL_VERSION) now exercises the negotiated path at the current protocol version (6), matching what the frontend already does when usesNegotiatedInspectorProtocol() is true. This looks like the correct fix rather than a workaround.
• The new comments in inspector_ws.rs and actor-inspector-context.tsx accurately describe the compatibility rationale and follow the repo's comment style (complete sentences, no em dashes).

No bugs found. One optional, non-blocking thought: the Rust side already has unit tests for both the negotiated and legacy-embedded-v5 paths (negotiated_frames_use_the_out_of_band_version, legacy_frames_remain_embedded_v5, parses_inspector_protocol_query_parameter), so the driver test likely does not need to also cover the legacy path — just flagging it in case an end-to-end regression test for old deployed runtimes talking to a new dashboard has value.

Nothing else stands out on security, performance, or test coverage grounds. The diff is comments plus a mechanical test alignment, with no runtime behavior change outside the test.