chore(sqlite-vfs): remove wasm sqlite packages and workspace wiring

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

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• 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
• chore(sqlite-vfs): remove wasm sqlite packages and workspace wiring #4641 👈 (View in Graphite)
• 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: chore(sqlite-vfs): remove wasm sqlite packages and workspace wiring

Overview

This PR removes the WASM SQLite VFS package and its associated workspace wiring. The deleted surface includes:

• rivetkit-typescript/packages/sqlite-vfs/ -- approx 2,300 lines of WASM VFS implementation (vfs.ts, kv.ts, pool.ts, schemas, scripts)
• rivetkit-typescript/packages/sqlite-vfs-test/ -- approx 790 lines of tests
• Three internal design docs (DYNAMIC_ACTOR_SQLITE_PROXY_SPEC.md, SQLITE_VFS.md, sqlite-batch-atomic-write.md)
• COPY steps from all three frontend Dockerfiles
• @rivetkit/sqlite-wasm from workspace resolutions and the sandbox example

The intent aligns with the design direction in the deleted spec: move to host-side native SQLite rather than in-isolate WASM.

Issues

Unintentional pnpm-lock.yaml override (likely a bug)

The @rivetkit/engine-api-full workspace override was changed from workspace:* to a pkg.pr.new PR preview URL. This pins CI and developers to an ephemeral commit build on an external service. If that URL expires or the package is removed this will silently break installs. This looks like it was included by accident and should be reverted before merge.

PR description is empty

All checklist boxes are unchecked and there is no summary. It is worth noting which downstream consumers depended on @rivetkit/sqlite-wasm and confirming they have been migrated or are intentionally left without SQLite support until the native path lands.

Test coverage removed without replacement

Approx 790 lines of tests are deleted, including:

• pool.test.ts -- WASM pool lifecycle, sticky assignment, bin-packing, poisoned-short-name isolation, double-destroy idempotency, shutdown guard
• sqlite-vfs.test.ts -- persistence across VFS instances, chunk-boundary payloads, unaligned overwrites
• sqlite-lock-repro.test.ts -- Node.js SQLite locking regression test

The lock-repro test covers a property of the Node.js runtime rather than the WASM library, and could be relevant to the native path too. Consider whether it should be migrated.

kv.ts key layout reference is now gone

CLAUDE.md states the native Rust VFS and the WASM TypeScript VFS must match 1:1, and lists rivetkit-typescript/packages/sqlite-vfs/src/kv.ts as the authoritative TypeScript side. With kv.ts deleted, the native VFS (rivetkit-typescript/packages/sqlite-native/src/kv.rs) has lost its paired reference. Consider either moving the key-layout constants to a shared spec or updating CLAUDE.md to remove the now-stale file reference.

docs-internal/engine/NATIVE_SQLITE_DATA_CHANNEL.md not updated

CLAUDE.md references this file as the full spec for native/WASM VFS parity. Deleting the WASM implementation without updating that spec may leave it referencing a package that no longer exists.

Minor observations

• Sandbox example version pin change to * is correct per CLAUDE.md workspace conventions.
• Rust Cargo.lock bumps (anyhow, bitflags, bumpalo) are minor and look benign.
• Dockerfile COPY removals are clean and correct.

Summary

The removal is well-scoped and directionally correct. The blocking concern is the @rivetkit/engine-api-full pkg.pr.new pin in pnpm-lock.yaml -- that should not land on main. The test deletion and missing doc updates are worth addressing before or immediately after merge.