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
• 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

Note: This is a draft PR targeting chore/remove-wasm-sqlite-native-only (part of a stacked PR workflow).

Summary

Clean removal of the @rivetkit/sqlite-vfs WASM SQLite package (~8,600 lines), its test suite, internal specs, and all workspace wiring. The intent is clear and the scope is well-contained.

---

Issues

🔴 @rivetkit/engine-api-full changed to a PR preview URL in pnpm-lock.yaml

The diff shows @rivetkit/engine-api-full override changed to a pkg.pr.new ephemeral preview URL. These URLs are tied to a specific CI run and expire -- this should not be merged as-is. The override needs to point to a stable workspace reference or pinned version.

🟡 WASM/native VFS parity (CLAUDE.md requirement)

CLAUDE.md states the native Rust VFS and the WASM TypeScript VFS must match 1:1. This PR removes the WASM TypeScript VFS. Confirm the native side is being removed or replaced in the parent branch (chore/remove-wasm-sqlite-native-only), or update/remove the parity note in CLAUDE.md if the constraint no longer applies after the full stack lands.

🟡 examples/sandbox/pnpm-lock.yaml deleted

The sandbox lock file is removed but the package still exists in the workspace. Confirm pnpm resolves sandbox dependencies correctly from the root lock file -- deleting a self-contained lock file without verifying root-level resolution can cause silent install failures.

---

Observations

Ladle Dockerfile removes platform-specific packages not in this diff

Lines removing sqlite-vfs-linux-arm64 and sqlite-vfs-linux-x64 COPY commands reference packages not in this diff. Are they removed in the parent branch, or were they already absent from the repo?

DYNAMIC_ACTOR_SQLITE_PROXY_SPEC.md deleted

This spec describes the replacement architecture (host-side SQLite bridge via sqliteExec/sqliteBatch RPC). If that replacement has not been implemented yet, deleting the spec loses design context. Worth confirming the deletion is intentional.

Cargo.lock churn in rivetkit-rust/Cargo.lock

405 additions / 420 deletions of Rust dependency versions look like incidental version bumps unrelated to the WASM SQLite removal. Worth confirming they are intentional and not accidentally carried from another branch.

---

Verdict

The cleanup is correct and well-scoped. The blocking item is the pkg.pr.new URL in pnpm-lock.yaml which must be resolved before merging. The WASM/native parity concern and lock file deletion are worth a quick confirmation before the stack lands. Also worth adding a one-line description to the PR body for future git archaeology.