chore(release): sync repository version to 2.0.955 [skip release publish]

[kantorcodes]

Summary

• sync repository version files to 2.0.955 after publish
• keep repo-visible version metadata aligned with the released package artifacts

Testing

• uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.955"

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[greptile-apps]

Greptile Summary

This PR syncs the repository version metadata after release. The main changes are:

• pyproject.toml project version moved to 2.0.955.
• Runtime __version__ moved to 2.0.955.
• uv.lock editable package metadata moved to 2.0.955.

Confidence Score: 5/5

Safe to merge; the changes are limited to version metadata alignment.

The diff only updates repository-visible version values across the project metadata, runtime version module, and lockfile, with no behavioral code changes.

T-Rex Logs

What T-Rex did

• T-Rex ran the version-sync checks for the PR, captured the before and after logs, and observed a PR contract mismatch despite aligned static metadata.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails on already-synced 2.0.955 head

   • Bug
     • On head, repository-visible metadata is aligned at 2.0.955, but the PR Testing command uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.955" exits with status 1. The captured output shows uv sync --frozen succeeds (Checked 104 packages in 0.85ms), then scripts/sync_repo_version.py fails with Error: Could not update [project].version in /tmp/trex-version-head/pyproject.toml. The contract required this documented sync command to succeed cleanly/idempotently for 2.0.955.
   • Cause
     • The sync script treats the already-updated [project].version state in pyproject.toml as an update failure instead of a successful no-op/idempotent state.
   • Fix
     • Update scripts/sync_repo_version.py so setting the same target version is accepted as success, or adjust its pyproject replacement logic to match and rewrite the current [project].version = "2.0.955" line without error. Add a regression test for rerunning the sync command when all version files already contain the requested version.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(release): sync repository version ..." | Re-trigger Greptile}