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

[kantorcodes]

Summary

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

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

• pyproject.toml project version updated to 2.0.960.
• src/codex_plugin_scanner/version.py package version updated to 2.0.960.
• uv.lock editable hol-guard package entry updated to 2.0.960.

Confidence Score: 5/5

The changes are limited to repository-visible version metadata and are safe to merge.

The touched files consistently align the package and lockfile version to 2.0.960 with no functional code changes.

T-Rex Logs

What T-Rex did

• T-Rex captured the baseline version-sync state before the attempt, confirming all versions were 2.0.922 and the process exited with code 0.
• T-Rex performed the version-sync step and observed the head at 2.0.960 after the attempt, but the sync command exited with code 1 due to an inability to update the project version in the pyproject.toml file.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails when target version is already present

   • Bug
     • The PR contract says running uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.960" on head should succeed or be a no-op that preserves alignment. In the head worktree, the pre-sync inspection confirmed pyproject.toml, version.py, and uv.lock were all already at 2.0.960, but the documented command exited 1 with Error: Could not update [project].version in .../pyproject.toml.
   • Cause
     • scripts/sync_repo_version.py treats an already-correct [project].version line as not updated because _replace_project_version only records success when the replacement text differs from the original line. When the target version is identical, _replace_matching_line returns the original line, leaving project_version_index unset and raising ValueError.
   • Fix
     • Change _replace_project_version (and any analogous replacement helpers if needed) to record that the version line was found even when the replacement is identical, then return unchanged text with changed=False instead of raising.

   _{Ran code and verified through T-Rex}

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

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• pyproject.toml - version sync to 2.0.960
• src/codex_plugin_scanner/version.py - version sync to 2.0.960
• uv.lock - version sync to 2.0.960

---

_{Reviewed by laguna-m.1-20260312:free · Input: 230.9K · Output: 2.8K · Cached: 139.9K}