[renovate]

Why

Moves the WillBooster/tree-sitter fork this grammar is developed and tested against from 15.0.0 to 15.5.4: @willbooster/web-tree-sitter (devDependency used by the Wasm tests and the playground) and the willbooster-tree-sitter crate (Rust dev-dependency for the Rust tests and fuzzing; script/runtime-version derives the generator CLI version from it). Proposed by Renovate.

Requirements

• required: not recorded — ask the requester
• required: the committed src/ parser stays what the pinned generator produces, since script/fork-cli picks the CLI version from the willbooster-tree-sitter version Cargo.lock locks.
• chosen: keep Cargo.toml's version = "15.0.0" requirement and move only the lockfile; the caret range already admits 15.5.4 and the crate is a dev-dependency, so published consumers are unaffected.

Customer Summary

No parser change for package users; the README and the Rust crate docs now name 15.5.4 as the tested runtime.

Technical Summary

package.json/bun.lock pin @willbooster/web-tree-sitter 15.5.4; Cargo.lock locks willbooster-tree-sitter 15.5.4. Regenerating with the 15.5.4 CLI produces no diff in src/. README.md and the docs.rs link in bindings/rust/lib.rs name 15.5.4 as the tested runtime version.

Testing

• bun run generate with the 15.5.4 CLI: no changes to generated sources.
• bun run verify passes.
• CI test, multi-OS test, test-rust, and fuzz pass on this head.

Notes

The Renovate PR carried no stated request beyond the dependency update itself, so the request-derived requirement is recorded as not recorded.