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

[kantorcodes]

Summary

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

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

• pyproject.toml project version updated to 2.0.966.
• src/codex_plugin_scanner/version.py runtime __version__ updated to 2.0.966.
• uv.lock editable package version updated to 2.0.966.

Confidence Score: 5/5

Safe to merge with minimal risk.

The diff only aligns version metadata across the expected files, and all changed values consistently use 2.0.966. No functional code paths, APIs, schemas, or security-sensitive behavior are modified.

No files require special attention.

T-Rex Logs

What T-Rex did

• Inspected the version-sync baseline by reviewing trex-artifacts/version-sync-01-before.log and confirmed base versions were pyproject.project.version=2.0.963, codex_plugin_scanner.version.__version__=2.0.963, and uv.lock hol-guard version=2.0.963 with alignment True.
• Ran the version-sync and reviewed trex-artifacts/version-sync-02-after.log, noting head versions updated to 2.0.966 and alignment remained True.
• Observed that the documented sync process reached dependency installation but then failed with Could not update [project].version in /tmp/trex-version-sync/head/pyproject.toml and exited with code 1.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
pyproject.toml	Updates the project package version from 2.0.963 to 2.0.966; no issues found.
src/codex_plugin_scanner/version.py	Updates the runtime __version__ constant to 2.0.966; no issues found.
uv.lock	Updates the editable package entry version to 2.0.966; no issues found.

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails when metadata is already at 2.0.966

   • Bug
     • On the head commit, the repository-visible metadata is aligned to 2.0.966, but the PR-described command uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.966" fails after uv sync --frozen succeeds. The script exits with Error: Could not update [project].version in .../pyproject.toml even though [project].version exists and is already set to the requested version. This means the documented sync command cannot maintain the already-aligned state as requested.
   • Cause
     • scripts/sync_repo_version.py treats "no textual change because the value is already correct" as "version line not found". In _replace_project_version, line 128 only records project_version_index when _replace_matching_line(...) returns text different from the original line, so an already-correct version = "2.0.966" line leaves project_version_index as None and line 134 raises.
   • Fix
     • Update the replacement logic to distinguish a matched line from a changed line, and record that [project].version was found even when the replacement text is identical. Apply the same idempotency pattern to module/lock updates if they have the same match-vs-change coupling, then verify the documented command exits 0 with no diff.

   _{Ran code and verified through T-Rex}

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