chore: Cargo.lock out of sync with workspace version (0.1.0 vs 0.1.1) #44

What is affected

Cargo.lock at develop records covecto/covecto-api/covecto-cli at 0.1.0, while the workspace Cargo.toml (version.workspace) is 0.1.1 since release PR #35. The lock update was never committed with the release.

Expected vs actual

• Expected: lockfile matches workspace version on every release commit.
• Actual: fresh git clone + any cargo command rewrites Cargo.lock → dirty working tree out of the box; release builds may resolve differently than CI.

Steps to reproduce

1. git clone git@github.com:codecoradev/covecto && cd covecto
2. cargo metadata >/dev/null (or any cargo build)
3. git status → M Cargo.lock

Suggested fix

One chore: PR: cargo metadata >/dev/null to sync the lock, commit Cargo.lock only. Optional hardening: add --locked to CI cargo check/test/build invocations (or a dedicated cargo metadata --locked job) so this class of drift fails CI instead of silently accumulating.

Found while preparing #43.