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

[kantorcodes]

Summary

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

[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

Syncs repository-visible version metadata to 2.0.859.

Updates the package version in pyproject.toml.

Updates the exported runtime __version__ value in src/codex_plugin_scanner/version.py.

Updates the editable hol-guard package entry in uv.lock.

Confidence Score: 5/5

Version metadata changes are limited and appear safe to merge.

The changed files only synchronize package/version metadata and lockfile metadata with the released version; no runtime behavior or interfaces are changed.

T-Rex Logs

What T-Rex did

• T-Rex ran the requested verification, but its local artifact references were not uploaded.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version-sync validation command fails on the synced head checkout

   • Bug
     • The PR validation claim says uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.859" should complete successfully on head. On the requested head commit, the repository-visible versions are already 2.0.859, but running the documented command exits 1 with Error: Could not update [project].version in /tmp/trex-version-sync/head/pyproject.toml. This makes the advertised validation command non-idempotent and failing on the normal already-synced checkout.
   • Cause
     • The version sync script treats an already-correct [project].version line as not updated because _replace_project_version only records success when the replacement line differs from the original line. Since the changed pyproject.toml line is already version = "2.0.859", the replacement is identical, project_version_index remains unset, and the script raises instead of accepting the matching line.
   • Fix
     • Make the sync script consider a matching version line as found even if the replacement text is identical, so rerunning the documented command with the current version succeeds without modifying files. For example, set the found index whenever the project version pattern matches, and separately track whether text changed.

   _{Ran code and verified through T-Rex}

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