fix(rivetkit-napi): remove stale HttpRequestBodyStream test after envoy v6 revert

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/actors

• #5605 fix(workflow-engine): mark completed inner-loop iterations v …
• #5603 fix(rivetkit): expose engine ray IDs on errors for debug
• #5601 fix(frontend): submit Vercel drain grace period
• #5604 fix(rivetkit-napi): remove stale HttpRequestBodyStream test … 👈
• main

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

_{change rlmrkmtk}

[railway-app]

🚅 Deployed to the actors-pr-5604 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
kitchen-sink	😴 Sleeping (View Logs)	Web	Aug 25, 2026 at 7:39 pm
frontend-cloud	😴 Sleeping (View Logs)	Web	Aug 25, 2026 at 7:38 pm
frontend-inspector	😴 Sleeping (View Logs)	Web	Aug 25, 2026 at 7:34 pm
ladle	✅ Success (View Logs)	Web	Aug 25, 2026 at 7:30 pm
mcp-hub	✅ Success (View Logs)	Web	Aug 25, 2026 at 7:28 pm
website	❌ Build Failed (View Logs)	Web	Aug 25, 2026 at 7:27 pm

[claude]

Review

Small, correct cleanup. Verified via repo-wide grep that HttpRequestBodyStream no longer exists anywhere in the codebase (napi crate or rivetkit-core), so cancelling_http_request_body_drops_core_receiver would not compile after the envoy v6 revert removed the type — deleting it is the right call rather than trying to keep it alive with a shim.

Code quality: Good. The now-unused imports (HttpRequestBodyStream, CoreHttpRequestBodyStream, tokio::sync::{mpsc, watch}) are removed alongside the test, and the remaining imports (Mutex, RivetErrorSchema, MacroMarker, Level, MakeWriter, parse_bridge_rivet_error, etc.) are still used by the other tests in the file, so nothing is left dangling.

Test coverage: This does remove the only coverage for "cancelling an in-flight HTTP request body stream drops the core-side receiver." Since that's a real behavior worth protecting against regressions, if the underlying HttpRequestBodyStream type/functionality comes back in a future change (e.g. envoy v6 re-lands), it'd be worth re-adding an equivalent test at that point rather than letting the coverage gap persist silently.

Bugs/security/performance: None applicable — this is a pure test deletion with no production code changes.

No blocking issues; looks good to merge.