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

[kantorcodes]

Summary

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

[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 version metadata to 2.0.862.

Updates pyproject.toml, src/codex_plugin_scanner/version.py, and the editable hol-guard entry in uv.lock.

Confidence Score: 5/5

Safe to merge; the change is limited to repository version metadata.

The touched files only align visible package/version state with the released artifact version, with no functional code path changes indicated.

T-Rex Logs

What T-Rex did

• Recorded the baseline environment before the version-sync operation, with hol-guard==2.0.855 and all version metadata reporting 2.0.855.
• Verified the head environment after the version-sync step updated hol-guard to 2.0.862 and all version indicators report 2.0.862.
• Ran the documented head command during uv sync; it exited with code 1 and printed an error about updating [project].version, and the subsequent status/diff command exited with code 0 with no changes to the version file.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails when files are already at the requested version

   • Bug
     • On head, python -m uv sync --frozen && python -m uv run --no-sync python scripts/sync_repo_version.py --version "2.0.862" exits with code 1 and prints Error: Could not update [project].version .... This contradicts the validation contract that the documented command should succeed and leave version files aligned/clean. The files do remain clean and aligned, but the command reports failure instead of treating the already-synchronized state as success.
   • Cause
     • scripts/sync_repo_version.py appears to require _replace_project_version to make a textual replacement; when the target version is already present, _replace_matching_line returns the original line unchanged, project_version_index is never set, and _replace_project_version raises Could not update [project].version.
   • Fix
     • Make the sync script idempotent: when a matching [project].version line is found, record the index even if the replacement text is identical, and return changed=False rather than raising. Apply the same already-current behavior to other version replacements if needed.

   _{Ran code and verified through T-Rex}

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