Skip to content

Fix session retry and statistics release blockers - #18

Merged
Eoic merged 2 commits into
developmentfrom
fix/release-progress-review
Oct 10, 2026
Merged

Eoic merged 2 commits into
developmentfrom
fix/release-progress-review

Conversation

@Eoic

@Eoic Eoic commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

Preserve reading-session positions and device type in the activity ledger and serialize retry lookup before generating timestamps. Correct half-open statistics boundaries and calculate the current streak independently of the reporting period.

Adds regressions for concurrent retries, conflicting metadata, persisted/grouped metadata, midnight boundaries, point sessions and month-spanning streaks. The race regression fails against the previous locking order. Focused progress/sync/projection tests pass, as do Ruff and Mypy. Optional JSON activity fields require no additional database migration; the client mapper is updated alongside the release.

Streak calculation unions complete-day ranges and partial boundary days, so cost depends on activity count rather than the age/duration of an activity. Tests cover overlapping intervals, midnight boundaries, future clipping and a year-1-to-present interval with a bounded number of calendar operations.

Review disposition: the suggested pre-upgrade metadata fallback does not apply to this release. Published 0.0.1 (88ab3a1) has no persisted activity ledger: its POST session route returns a generated response, and GET returns example data. The ledger and retry IDs are introduced by the still-unpublished 0.0.2 promotion. Preserve strict conflict detection for this current contract instead of adding a legacy fallback prohibited by the repository style guide.

Copilot AI balanced review requested due to automatic review settings October 10, 2026 22:44

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-10T22:47:05.978936Z 3daea7c PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3daea7c2e0

ℹ️ 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".

Comment thread papyrus/services/progress.py
Comment thread papyrus/services/progress.py Outdated
@Eoic
Eoic merged commit e9662b6 into development Oct 10, 2026
1 check passed
@Eoic
Eoic deleted the fix/release-progress-review branch October 13, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants