fix(template): repoint sync-with-uv at the upstream project

[ichoosetoaccept]

Summary

Repoints the sync-with-uv prek hook from the detailobsessed/sync-with-uv fork to the upstream project at tsvikas/sync-with-uv, in both this repo's prek.toml and the generated project/prek.toml.jinja.

• prek.toml — repo → https://github.com/tsvikas/sync-with-uv, rev → v0.6.0 (was the fork's bespoke v0.6.0-prek tag)
• project/prek.toml.jinja — same repo change; rev stays "" for prek update to fill

Why

The fork has been deleted, so every prek update / prek run that had to clone it failed with git fetch exit 128. That took out tests/test_template.py::TestIntegration::test_first_commit_succeeds_with_prek_hooks, the pre-push pytest-cov hook, and main's CI. Generated projects were broken the same way — a fresh scaffold could not complete its first commit.

The fork existed because upstream did not yet read prek.toml. It does now: prek.toml support landed in upstream v0.6.0, so the fork has no remaining purpose. Upstream v0.6.0 is a drop-in match — same hook id (sync-with-uv), same hook name, and a files pattern that already covers prek.toml.

Test plan

• pytest tests/test_template.py::TestIntegration::test_first_commit_succeeds_with_prek_hooks — passes (12.6s); this is the test that was failing on the dead repo
• The pre-push pytest-cov hook passed on the push for this branch, which is the gate that blocked the previous stack merge
• CI on this PR re-runs the full suite against the new reference

Greptile Summary

This change repoints the sync-with-uv Prek hook to its maintained upstream in the repository configuration and generated-project template. The rendered-project flow successfully installed and updated Prek hooks, and the replacement sync-with-uv hook passed. However, a freshly generated project cannot complete its initial commit on the tested Linux environment because the unchanged Lychee hook binary requires unavailable GLIBC versions.

Confidence Score: 4/5

Do not merge while generated projects can fail their first commit on supported Linux environments.

The replacement sync-with-uv hook completed successfully in a rendered project's update and commit-hook flow, but the same flow reproduced a blocking Lychee runtime incompatibility.

Files Needing Attention: project/prek.toml.jinja needs attention at the Lychee revision pin on line 122; prek.toml and the sync-with-uv template entry completed successfully.

T-Rex Logs

What T-Rex did

• T-Rex produced a proof for the posted P1 finding by running the focused first-commit test and recording the outcome.
• T-Rex produced a proof for another posted P1 finding.
• T-Rex performed general contract validation, capturing the exact runtime record and summarizing the Lychee configuration and PR-diff status.

_{Ran code and verified through T-Rex}

Comments Outside Diff (2)

1. project/prek.toml.jinja, line 122 (link)

   Lychee hook cannot load on the supported Linux baseline

   A freshly rendered project's prek update retains lychee-v0.24.2, whose Linux executable requires GLIBC_2.38 and GLIBC_2.39. On the tested environment, both initial-commit attempts fail before Lychee can run. Pin a Lychee release compatible with the supported glibc baseline, or run this hook in an environment with GLIBC 2.39 or later.

   Artifacts

   
   

   Focused first-commit test output

   • Exact captured output from the requested pytest command shows sync-with-uv passed while Lychee 0.24.2 failed to load because GLIBC 2.38 and 2.39 are unavailable, so the initial commit remains blocked.

   Lychee configuration and PR diff

   • Captured numbered template configuration and HEAD diff show the unchanged Lychee 0.24.2 pin and that the PR only repoints sync-with-uv, so the Lychee failure is pre-existing.

   

   _{Ran code and verified through T-Rex}

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: project/prek.toml.jinja
   Line: 122
   
   Comment:
   **Lychee hook cannot load on the supported Linux baseline**
   
   A freshly rendered project's `prek update` retains `lychee-v0.24.2`, whose Linux executable requires `GLIBC_2.38` and `GLIBC_2.39`. On the tested environment, both initial-commit attempts fail before Lychee can run. Pin a Lychee release compatible with the supported glibc baseline, or run this hook in an environment with GLIBC 2.39 or later.
   
   ---
   
   For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

   

2. General comment

   Initial commit fails when the template's Lychee 0.24.2 binary needs newer GLIBC

   • Bug
     • A freshly rendered project's prek update leaves Lychee at lychee-v0.24.2; its executable then fails at commit time because this Linux runner lacks GLIBC_2.38 and GLIBC_2.39. Both permitted commit attempts fail, despite the updated sync-with-uv hook passing.
   • Cause
     • project/prek.toml.jinja:122 pins the Lychee hook to lychee-v0.24.2, whose installed binary is incompatible with the runner's glibc. The [update.repos] exclusion at lines 12-13 only rejects nightly, not this incompatible stable release.
   • Fix
     • Use a Lychee hook release with binaries compatible with the supported Linux glibc baseline, or execute the hook in a GLIBC 2.39+ environment; validate with the same rendered-project first-commit test.

   _{Ran code and verified through T-Rex}

Prompt To Fix All With AI

### Issue 1
project/prek.toml.jinja:122
**Lychee hook cannot load on the supported Linux baseline**

A freshly rendered project's `prek update` retains `lychee-v0.24.2`, whose Linux executable requires `GLIBC_2.38` and `GLIBC_2.39`. On the tested environment, both initial-commit attempts fail before Lychee can run. Pin a Lychee release compatible with the supported glibc baseline, or run this hook in an environment with GLIBC 2.39 or later.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(template): repoint sync-with-uv at t..." | Re-trigger Greptile}

[ichoosetoaccept]

This change is part of the following stack:

• fix(template): repoint sync-with-uv at the upstream project #349 ◀
  • fix(template): stop chmodding scripts the template does not own #347
    • test: tolerate copier's temp-clone cleanup race on a dirty tree #348

_{Change managed by git-spice.}