chore: lockfile lefthook

[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 , #4654 )
• chore: lockfile lefthook #4647 👈 (View in Graphite)
• 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
• 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: lockfile lefthook

What This PR Does

Adds lockfile validation pre-commit hooks to lefthook.yml, fixes YAML indentation, removes the rivetkit-sqlite-native workspace dependency from Cargo.toml, updates pnpm-lock.yaml (switches @rivetkit/engine-api-full from an external preview URL to workspace:*, registers new sqlite-vfs package), and fixes method-chain indentation in database.rs.

---

Issues Found

High Severity

Cargo.toml - Removing rivetkit-sqlite-native workspace dependency will break the build

The PR removes the workspace declaration for rivetkit-sqlite-native, but rivetkit-typescript/packages/rivetkit-native/Cargo.toml still declares rivetkit-sqlite-native.workspace = true. Removing the workspace entry while the consumer crate still references it via .workspace = true will cause a cargo build failure. Either keep the workspace entry, or update rivetkit-native/Cargo.toml to use a direct path reference instead.

---

Low Severity

lefthook.yml - pnpm-lock hook runs on every commit with no file filter

pnpm install --frozen-lockfile runs on every commit regardless of whether any package.json or lockfile changed. This will add unnecessary delay to commits that only touch Rust, docs, or other non-Node files. Adding a glob field would restrict the hook to commits that actually modify package manifests. The cargo-lock hook (cargo metadata --no-deps) is fast enough that the missing filter is not a concern there.

---

Looks Good

• pnpm-lock.yaml - Switching @rivetkit/engine-api-full from the external pkg.pr.new preview URL to workspace:* is correct and consistent with the root resolutions entry. The new sqlite-vfs importer section looks mechanically correct.
• database.rs - The method-chain indentation fix is correct.
• lefthook.yml comment fix - Converting the hard-tab indentation in the commented block to spaces is the right fix for valid YAML.