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

[kantorcodes]

Summary

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

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

• Updates the package version in pyproject.toml.
• Updates the runtime __version__ constant.
• Updates the editable package version in uv.lock.

Confidence Score: 5/5

Safe to merge with minimal risk.

The diff only changes consistent version metadata in expected files. No executable logic, schema, API, or dependency behavior changes were introduced.

No files require special attention.

T-Rex Logs

What T-Rex did

• The baseline state shows base commit version sources all equal to 2.0.967 with internal consistency True.
• After updating to the head, the version sources are all equal to 2.0.968 with internal consistency True.
• The uv sync --frozen command completed successfully in the head state.
• The scripts/sync_repo_version.py --version 2.0.968 attempt failed with an error indicating the project.version could not be updated in the temporary pyproject.toml and the run exited with code 1.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
pyproject.toml	Bumps the project package version from 2.0.967 to 2.0.968; no issues found.
src/codex_plugin_scanner/version.py	Updates the exported __version__ constant to 2.0.968; no issues found.
uv.lock	Synchronizes the editable hol-guard lockfile package version to 2.0.968; no issues found.

Comments Outside Diff (1)

1. General comment

   Version sync command fails when target version is already present

   • Bug
     • The requested head validation command is expected to be idempotent/no-op, but on head uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version 2.0.968 fails after the frozen sync succeeds. The repository files already contain version = "2.0.968", __version__ = "2.0.968", and uv.lock editable package version 2.0.968, yet the sync script exits with Error: Could not update [project].version in .../pyproject.toml instead of reporting no changes.
   • Cause
     • scripts/sync_repo_version.py line 128 only treats a line as found when _replace_matching_line(...) returns different text. When the existing [project].version already equals the requested version, the replacement is identical, so project_version_index remains None and line 134 raises ValueError. This makes already-synchronized versions fail instead of being idempotent.
   • Fix
     • Track whether the [project] version line matches independently from whether its content changed. Set the version-line index whenever PYPROJECT_VERSION_LINE_PATTERN matches, then compute changed by comparing updated text to original. Apply the same found-vs-changed distinction to module and lockfile replacement paths if needed.

   _{Ran code and verified through T-Rex}

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