Repository navigation
Add active reading timer synchronization through PowerSync - #61
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bb47e3e75
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Active reading timers can now move between signed-in devices through PowerSync. The server accepts the first valid transition from a known version, acknowledges stale offline branches, and commits a saved timer together with its reading activities and optional book progress. Durable terminal states prevent retries from recording the session twice.
reading_timersmodel, additive Alembic migration, owned replication stream, and publication/source-role setup.docs/reading-timer-sync.md.Validation:
tools/papyrus check serverpassed (Ruff and Mypy). All 18 focused timer, migration, replication-config, and sync-service tests passed against the isolated test database.Deploy the migration, publication/grants, API, and PowerSync config before releasing the companion client. No production deployment was performed. Live multi-device acceptance remains separate from the database tests.
Closes #60. Related requirement: FR-5_3 (PapyrusReader/docs#36). Companion client PR: PapyrusReader/client#124.