Adopt crdt-sync v0.9.0's bundled sync_log signature

sync_log's eleven flat keywords became SyncTarget / LogCodec /
RevisionTracking upstream. Call sites and test doubles follow; the hook's own
pinned crdt-sync moves to v0.9.0 too, so the gate checks against the API the
code actually imports rather than an older tag.

No behaviour change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VCucBhUkHBBHHbsY7bSdGV

.pre-commit-config.yaml

@@ -117,7 +117,7 @@ repos:
         additional_dependencies:
           - pytest
           - gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.7.1#subdirectory=gatelock
-          - crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.6.0#subdirectory=crdt-sync
+          - crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.9.0#subdirectory=crdt-sync
           - mcp>=2,<3
           - pydantic
       - id: pylint
@@ -132,7 +132,7 @@ repos:
         additional_dependencies:
           - pytest
           - gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.7.1#subdirectory=gatelock
-          - crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.6.0#subdirectory=crdt-sync
+          - crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.9.0#subdirectory=crdt-sync
           - mcp>=2,<3
           - pydantic
 

CLAUDE.md

@@ -1,26 +0,0 @@
-do NOT run tests unless specifically instructed to do so or before committing
-If tests fail on the same issue twice in a row, STOP and ask the user how to proceed instead of continuing to fix and retry.
-ALWAYS confirm that the feature you add / bug you fixed behaves as it should by running the program after your changes (not tests!) and inspecting output comparing it with what user wanted, after confirming by yourself ask user if the program behaves as they intended
-After running tests fix all coverage gaps and issues, do not ignore unless specifically instructed to do so
-You are NOT done until you install the new version on the phone itself (flutter install --debug from the workout_app directory, then adb shell monkey -p com.kuhy.workout_app to launch).
-
-## NEVER fail silently
-
-A failure that says nothing is a bug. The PC's workout sync did nothing for
-weeks because a missing token `return`ed `[]` and real errors only logged at
-`INFO` — nobody could tell "nothing to do" from "it broke".
-
-- **Swallowed exceptions must say why, loudly.** Every `except` must either
-  re-`raise` or log at `warning`/`error`/`exception`/`critical` with the
-  concrete reason. `debug`/`info` do NOT count — an invisible log is a silent
-  failure with extra steps. Enforced by `scripts/check_silent_failures.py`
-  (pre-commit hook `no-silent-failures`); ruff's `S110` only catches
-  `except: pass`, which is the rare case.
-- **Guard clauses that abort work must log too.** `if token is None: return`
-  is a silent no-op. Say what was missing and what it means.
-- **Return something meaningful.** Prefer a typed result (e.g.
-  `_manual_push.PushResult(pushed, record_count, reason)`) over a bare
-  `None`/`[]`/`False`, so the caller can react instead of guessing. `reason`
-  should read like a sentence a human can act on.
-- **No escape hatch** — `# noqa` is banned repo-wide. If a failure really is
-  benign, log it at `warning` and move on.

CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

pyproject.toml

@@ -8,7 +8,7 @@ requires-python = ">=3.10"
 # also used by diet_guard; here for phone-workout GitHub sync (Workstream C)
 dependencies = [
     "gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.7.1#subdirectory=gatelock",
-    "crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.7.0#subdirectory=crdt-sync",
+    "crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.9.0#subdirectory=crdt-sync",
 ]
 
 [project.scripts]

requirements.txt

@@ -3,7 +3,7 @@
 bandit>=1.7.0
 codespell>=2.2.0
 coverage>=7.4.0
-crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.7.0#subdirectory=crdt-sync
+crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.9.0#subdirectory=crdt-sync
 gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.7.1#subdirectory=gatelock
 mcp>=2,<3
 mypy>=1.8.0

screen_locker/_manual_push.py

@@ -32,9 +32,12 @@ from crdt_sync import (
     GitHubSyncClient,
     GitHubSyncError,
     Hlc,
+    LogCodec,
     Record,
     RemoteSyncError,
     RepoNotFoundError,
+    RevisionTracking,
+    SyncTarget,
     sync_log,
 )
 
@@ -193,14 +196,20 @@ def push_pc_workouts(log_file: Path) -> PushResult:
     try:
         with_sync_retry(
             lambda: sync_log(
-                client=client,
+                SyncTarget(
-                device_id=identity.device_id,
+                    client=client,
-                legacy_device_id=identity.legacy_id,
+                    device_id=identity.device_id,
-                path_prefix=_DEVICES_PREFIX,
+                    legacy_device_id=identity.legacy_id,
-                local_log=log,
+                    path_prefix=_DEVICES_PREFIX,
-                encode=_encode_log,
+                ),
-                decode=_decode_log,
+                log,
-                state_store=FileSyncStateStore(SYNC_STATE_FILE),
+                LogCodec(
+                    decode=_decode_log,
+                    encode=_encode_log,
+                ),
+                RevisionTracking(
+                    state_store=FileSyncStateStore(SYNC_STATE_FILE),
+                ),
             ),
             description="push PC workouts",
         )

screen_locker/tests/test_manual_push_part2.py

@@ -164,5 +164,6 @@ class TestPushPcWorkouts:
             patch.object(_manual_push, "sync_log", MagicMock()) as fake_sync,
         ):
             push_pc_workouts(log_file)
-        pushed = fake_sync.call_args.kwargs["local_log"]
+        # local_log is the second positional arg since crdt-sync v0.9.0.
+        pushed = fake_sync.call_args.args[1]
         assert "runnerup_verified:2026-07-12" in pushed