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

[kantorcodes]

Summary

• sync repository version files to 2.0.954 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.954"

[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 now reports 2.0.954.
• The exported scanner __version__ now reports 2.0.954.
• The editable hol-guard lockfile entry now reports 2.0.954.

Confidence Score: 5/5

Safe to merge; the change is limited to repository version metadata and the lockfile entry for the editable package.

The touched files only align visible package version values to the released artifact version, with no behavioral code paths changed.

T-Rex Logs

What T-Rex did

• T-Rex validated the baseline state with base versions aligned at 2.0.922 and exit code 0.
• T-Rex updated the head to 2.0.954 and completed package installation via uv sync --frozen.
• T-Rex attempted to update the repository version with scripts/sync_repo_version.py --version 2.0.954, but the command failed with an update error and exit code 1.
• T-Rex performed post-failure checks via git status and git diff, which were clean, indicating the failure arose from the idempotent same-version path rather than a real version mismatch.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails when repository is already at 2.0.954

   • Bug
     • On the head commit, the repo-visible metadata is aligned to 2.0.954, but the documented workflow uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.954" exits with status 1. The captured output shows Error: Could not update [project].version in /tmp/trex-head/pyproject.toml immediately after uv sync --frozen succeeds. This violates the PR contract that the frozen uv workflow should leave the repository aligned at 2.0.954 without a mismatch or unexpected failure.
   • Cause
     • The sync script treats an already-correct version line as if the [project].version line could not be found/updated. In _replace_project_version, it only sets project_version_index when _replace_matching_line(...) changes the line. When the requested version is identical to the existing version = "2.0.954", the matching line is unchanged, project_version_index remains None, and the script raises ValueError.
   • Fix
     • Update the replacement helpers to distinguish 'matched line found' from 'text changed'. For example, detect the version line with the regex first, record that it was found, replace it even if the resulting text is identical, and return changed=False for idempotent runs instead of raising.

   _{Ran code and verified through T-Rex}

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