chore: bump version to 0.2.2

[prom3theu5]

Bumps Cargo.toml / Cargo.lock to 0.2.2 to release the indexing progress-bar fix merged in #9 (live parse bar + per-file resolve-phase counters).

The version bump was missed in #9 itself (added after merge), so this is a small follow-up. No code change beyond the version.

[qodo-code-review]

Review Summary by Qodo

Bump version to 0.2.2

Walkthroughs

Description

• Bump version from 0.2.1 to 0.2.2
• Release indexing progress-bar improvements

Diagram

flowchart LR
  A["Cargo.toml<br/>version 0.2.1"] -- "bump version" --> B["Cargo.toml<br/>version 0.2.2"]

Loading

File Changes

1. Cargo.toml ⚙️ Configuration changes +1/-1

Update package version to 0.2.2

• Update package version from 0.2.1 to 0.2.2
• Release indexing progress-bar fix from PR #9

Cargo.toml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Cargo.lock not updated 🐞 Bug ☼ Reliability

Description

Cargo.toml bumps synapse to 0.2.2 but Cargo.lock still records the root package as 0.2.1, making
the lockfile inconsistent with the manifest. CI/release workflows use --locked, so Cargo will fail
with “lock file needs to be updated but --locked was passed”.

Code

Cargo.toml[3]

Evidence

The manifest shows version 0.2.2 while the lockfile still lists the synapse package as 0.2.1. The
CI and release workflows explicitly use --locked, which requires the lockfile to be in sync with
the manifest, otherwise those jobs will fail.

Cargo.toml[1-4]
Cargo.lock[1989-2026]
.github/workflows/ci.yml[43-46]
.github/workflows/release.yml[62-66]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`Cargo.toml` was updated to version 0.2.2, but `Cargo.lock` still contains the root package entry for `synapse` at 0.2.1. Since CI/release runs Cargo with `--locked`, the build/test will fail if the lockfile is considered out-of-date.

## Issue Context
The repo’s CI (`cargo test --locked`) and release workflow (`cargo build --locked`) require a lockfile that matches the manifest.

## Fix Focus Areas
- Cargo.lock[1989-2026]
- .github/workflows/ci.yml[43-46]
- .github/workflows/release.yml[62-66]

## Recommended fix
1. Regenerate/update the lockfile after the version bump (e.g., run `cargo generate-lockfile` or run a normal `cargo build` once to let Cargo rewrite the lockfile).
2. Commit the resulting `Cargo.lock` changes so `--locked` workflows pass.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Cargo.lock not updated 🐞 Bug ☼ Reliability

Cargo.toml bumps synapse to 0.2.2 but Cargo.lock still records the root package as 0.2.1, making
the lockfile inconsistent with the manifest. CI/release workflows use --locked, so Cargo will fail
with “lock file needs to be updated but --locked was passed”.

Agent Prompt

## Issue description
`Cargo.toml` was updated to version 0.2.2, but `Cargo.lock` still contains the root package entry for `synapse` at 0.2.1. Since CI/release runs Cargo with `--locked`, the build/test will fail if the lockfile is considered out-of-date.

## Issue Context
The repo’s CI (`cargo test --locked`) and release workflow (`cargo build --locked`) require a lockfile that matches the manifest.

## Fix Focus Areas
- Cargo.lock[1989-2026]
- .github/workflows/ci.yml[43-46]
- .github/workflows/release.yml[62-66]

## Recommended fix
1. Regenerate/update the lockfile after the version bump (e.g., run `cargo generate-lockfile` or run a normal `cargo build` once to let Cargo rewrite the lockfile).
2. Commit the resulting `Cargo.lock` changes so `--locked` workflows pass.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools