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

[kantorcodes]

Summary

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

[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 to 2.0.961. The main changes are:

• Updates pyproject.toml project version.
• Updates src/codex_plugin_scanner/version.py package version constant.
• Updates the editable hol-guard package version in uv.lock.

Confidence Score: 5/5

Safe to merge with minimal risk.

The PR only changes consistent version metadata across three files and does not alter runtime behavior, APIs, dependencies, or security-sensitive code.

No files require special attention.

T-Rex Logs

What T-Rex did

• Reviewed the pre-sync artifact to verify baseline metadata, confirming project.version and __version__ both show 2.0.922 and that all_aligned is true.
• Observed the after-state initial head metadata for the sync was aligned at 2.0.961.
• Executed the version-sync step uv sync --frozen and noted it completed with exit code 0.
• Noted that the overall sync command exited with code 1 due to an error and that there is no tracked version diff or status output in the after state.
• Verified that the final metadata remained aligned at 2.0.961.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
pyproject.toml	Updates the project package version from 2.0.922 to 2.0.961.
src/codex_plugin_scanner/version.py	Updates the scanner package __version__ constant to 2.0.961.
uv.lock	Updates the editable hol-guard package version in the lockfile to 2.0.961.

Comments Outside Diff (1)

1. General comment

   Version sync command fails when rerun on already-synced 2.0.961 head

   • Bug
     • The PR contract says the release sync command for version 2.0.961 should be reproducible and leave head unchanged. In the head worktree, uv sync --frozen completed successfully, but uv run --no-sync python scripts/sync_repo_version.py --version "2.0.961" exited with code 1 and printed Error: Could not update [project].version in /tmp/trex-version-sync/head/pyproject.toml. The repository-visible metadata remains aligned at 2.0.961 after the failed command, but the command itself is not idempotently successful on the already-synced release commit.
   • Cause
     • The sync script appears to treat the absence of a textual replacement in pyproject.toml as an error, so rerunning it with the same version as already present fails instead of recognizing the file is already at the requested version.
   • Fix
     • Make scripts/sync_repo_version.py --version 2.0.961 idempotent: if pyproject.toml, version.py, and uv.lock already contain the requested version, exit 0 without modifying tracked files.

   _{Ran code and verified through T-Rex}

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