test(rivetkit): remove wasm sqlite-only fixtures and coverage

[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]

• chore(engine): publish engine bases in ci #4649 : 3 dependent PRs (#4650 , #4652 , #4666 )
• chore: lockfile lefthook #4647
• fix(rivetkit): surface native sqlite kv errors to callers #4645
• fix(rivetkit): prevent sleep races during disconnect and db work #4644
• fix(rivetkit): isolate engine envoys and propagate startup failures #4643
• test(rivetkit): remove wasm sqlite-only fixtures and coverage #4642 👈 (View in Graphite)
• chore(sqlite-vfs): remove wasm sqlite packages and workspace wiring #4641
• chore(rivetkit): remove wasm sqlite runtime #4614
• fix(sqlite-native): restore native startup kv preload #4639
• fix(sqlite-native): delete metadata before chunk range #4638
• fix(sqlite-native): keep truncate cache coherent #4637
• fix(sqlite-vfs): use delete range for truncate cleanup #4636
• fix(sqlite-native): restore kv error hook #4635
• perf(sqlite-native): avoid cloning cached read chunks #4634
• perf(sqlite-native): gate kv operation labels #4633
• perf(sqlite-native): reuse read cache for partial writes #4632
• perf(sqlite-native): remove delete file existence probe #4631
• fix(sqlite-native): gate native read cache behind env var #4630
• fix(pegboard): isolate runner config dc lookup failures #4625 : 1 other dependent PR (#4626 )
• docs(pegboard): note runner config upsert split write risk #4624
• fix(pegboard): unpack global runner config keys correctly #4623
• fix(pegboard-gateway): enforce tunnel message state #4622
• fix(pegboard-runner): clear terminal tunnel routes #4621
• fix(pegboard): skip protocol version keys in runner pool backfill #4620
• fix(pegboard): create missing normal runner configs #4619
• fix(epoxy): reuse cached optimistic value #4618
• main

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

[claude]

PR Review: test(rivetkit): remove wasm sqlite-only fixtures and coverage

This PR cleanly removes WASM SQLite test fixtures, test suites, and related infrastructure as part of the broader move to native-only SQLite via @rivetkit/rivetkit-native. The deletions are net -1,192 lines and the changes are well-scoped. A few things worth considering:

---

Removed resilience tests may still apply to native SQLite

In actor-db-stress.ts, the "KV Channel Resilience" block was guarded by skipIf(!nativeAvailable), meaning these two tests only ran with the native backend:

• recovers from forced WebSocket disconnect during DB writes
• handles disconnect during active write operation

Removing them entirely means there is no test coverage for native SQLite resilience during WebSocket disconnection. If the KV channel itself is being removed (not just WASM), this is fine — but if the native backend still uses a WebSocket channel internally, these tests should be preserved or replaced rather than dropped.

---

Data migration / compatibility story

cross-backend-vfs.ts was the only place that verified WASM-written data is readable by the native backend and vice versa. Removing it without a note in ACTOR_KV_STRUCTURE.md or a migration guide means any production deployment that was using WASM SQLite has no documented upgrade path. If migration is handled elsewhere in the stack, a pointer here would help.

---

ACTOR_KV_STRUCTURE.md: missing note on legacy key space

The sqlite (8)/ KV namespace section was removed entirely. If old actor data was ever written under that key space (by WASM actors), it still sits on disk in existing deployments. A one-line note about what happens to that data on upgrade (e.g., "data written by the WASM VFS under sqlite (8)/ is not read or cleaned up by the native runtime") would help operators reason about upgrades.

---

Limits doc removal looks correct

preloadMaxSqliteBytes (768 KiB) was removed from limits.mdx. As long as that config key is also gone from engine/packages/config/ in a companion PR, this is correct. Worth a quick grep to confirm no reference remains.

---

Minor

• sleep-db.ts removing the sleepWsRawDbAfterClose actor is correct — the "poisoned KV produces disk I/O error" test only made sense with the KV-backed VFS.
• CLAUDE.md updates follow the one-liner convention correctly.
• utils.ts reformatting to multi-line is a no-op, no concerns.

---

Overall: The cleanup is well-executed for what it is. The main open question is whether the native SQLite WebSocket resilience tests should be replaced rather than dropped. Everything else looks intentional and correctly scoped to the WASM removal.