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

[kantorcodes]

Summary

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

[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.863.

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

Confidence Score: 5/5

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

The touched files only align package/version metadata with the released artifact version, with no behavioral code paths changed.

T-Rex Logs

What T-Rex did

• The baseline version-sync state was reviewed and confirmed to be 2.0.855 with hol-guard==2.0.855, establishing the starting point for verification.
• The documented version-sync command was executed, producing diffs in pyproject.toml, version.py, and uv.lock that updated to 2.0.863, and the command exited with code 0.
• The head state after changes was verified as 2.0.863 with hol-guard==2.0.863, uv sync --frozen completed successfully, and the documented sync command later exited with code 1 (Could not update [project].version) while git status and diff remained clean.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Documented version sync command fails on already-synced head

   • Bug
     • The PR contract requires the documented command uv sync --frozen && uv run --no-sync python scripts/sync_repo_version.py --version "2.0.863" to leave head without drift. Although head's visible version metadata is aligned at 2.0.863, the sync script exits with status 1 on head when asked to sync to the version already present, reporting Error: Could not update [project].version in /home/user/repo/trex-worktrees/head/pyproject.toml. This makes the documented release sync command non-idempotent and causes a clean, already-synchronized checkout to fail automation.
   • Cause
     • scripts/sync_repo_version.py treats an unchanged replacement as no matching version line. In _replace_project_version, line 127 calls _replace_matching_line(...), and line 128 only records project_version_index when replaced_line != line. When pyproject.toml already contains the requested version, the regex matches but the returned line is identical, so project_version_index remains None and line 134 raises ValueError.
   • Fix
     • Track whether the version line matched separately from whether the text changed. For example, match PYPROJECT_VERSION_LINE_PATTERN directly inside the [project] table, set project_version_index whenever it matches, and then replace the captured version even if the resulting line is identical. Apply the same idempotency check to module/lockfile replacement paths if they use the same changed-line-as-match sentinel.

   _{Ran code and verified through T-Rex}

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