chore: align lockfile format with main

Author: divitsheth

docs/plans/2026-07-15-cli-telemetry-live-agreement.md

@@ -367,3 +367,25 @@ username. A final force-blocking dashboard run returned all 14 insights without
 error: one product install, ten active installations, four searches across two
 installations, one show, the expected lifecycle outcome rows, and six sanitized
 exceptions affecting four disposable installations.
+
+## Lockfile hygiene review
+
+A final P3 review correctly identified that the telemetry branch had retained a
+revision-2 lockfile generated by local `uv 0.6.16`, while current main uses
+revision 3. The raw `uv.lock` diff was 568 additions and 509 deletions even
+though its normalized dependency change was only PostHog and four transitive
+packages.
+
+Modern `uv` preserves an existing compatible lock revision, so rerunning it on
+the branch's revision-2 file was insufficient. The lock was mechanically seeded
+from current main and regenerated with `uv 0.11.29`. The resulting revision-3
+lock keeps `upload-time` metadata and differs from main by exactly 59 additions,
+with no deletions: `posthog`, `backoff`, `distro`, `requests`, `urllib3`, and the
+two CodeAlmanac PostHog dependency edges.
+
+Both modern and repository-local `uv lock --check` pass. Modern locked sync
+dry-run and local `uv sync --locked` make no changes. The exact lock passes all
+564 tests on Python 3.12.10 and Python 3.13.3, Ruff, 71-page Almanac validation,
+`git diff --check`, and a clean modern-uv sdist/wheel build. No project-wide uv
+pin was added because that is a separate tooling-policy decision; the review
+noise is removed without broadening this telemetry fix.