chore: bump cooklang-language-server to 0.2.3

[dubadub]

Bumps cooklang-language-server 0.2.1 → 0.2.3 to pick up the multi-word ingredient/cookware/timer parsing fix, so cook lsp correctly highlights and shows tooltips for names with spaces or punctuation (e.g. @heavy whipping cream{1%cup}).

Depends on cooklang/cooklang-language-server#8 being released to crates.io first (the Cargo.lock entry will resolve once 0.2.3 is published).

Relates to cooklang/CookVSCode#10

[claude]

Review: chore: bump cooklang-language-server to 0.2.3

The change itself is correct and well-scoped — a one-line version bump with a clear rationale.

One concern before merging:

The PR description notes this depends on 0.2.3 being published to crates.io first. Until that happens, cargo build will fail with a "could not find package" error. Consider either:

• Adding a note to block merge until the crate is confirmed live on crates.io, or
• Merging only after confirming cargo update -p cooklang-language-server resolves to 0.2.3

Otherwise, the change is straightforward and the fix (multi-word ingredient/cookware/timer highlighting) is a worthwhile improvement. ✅

[claude]

Code Review

This is a minimal dependency bump of cooklang-language-server from 0.2.1 → 0.2.3 across Cargo.toml and Cargo.lock. The crate's only public API used in this repo is Backend::new and the Backend struct (src/lsp.rs:3), which are stable across this patch range. No logic changes are introduced.

---

Findings

Stale PR description — Cargo.lock already contains the 0.2.3 entry (with a valid 64-character SHA-256 checksum debf28fc...), which contradicts the description's note that "the Cargo.lock entry will resolve once 0.2.3 is published." Either 0.2.3 was already on crates.io when this was written, or the description wasn't updated after the lock file was committed. Worth correcting to avoid confusion for reviewers wondering whether CI will actually build.

Version skip (0.2.1 → 0.2.3) — 0.2.2 is absent from the lock file. Was 0.2.2 yanked, or was it simply never published? If yanked, it's worth a sentence in the PR body so reviewers aren't left wondering.

---

Everything else looks good

• Cargo.lock checksum is the correct 64-character hex SHA-256 length.
• The dependency tree entry is consistent (same cooklang, tower-lsp, etc. transitive deps).
• The version constraint in Cargo.toml uses the standard caret form ("0.2.3" = >=0.2.3, <0.3), consistent with the rest of the file.
• No security surface area is added; this crate is only invoked on the cook lsp path.