Skip to content

Fix notification time and history contracts - #305

Closed
hamzamerzic wants to merge 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/notification-time-contracts-20260728
Closed

Fix notification time and history contracts#305
hamzamerzic wants to merge 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/notification-time-contracts-20260728

Conversation

@hamzamerzic

Copy link
Copy Markdown
Collaborator

Summary

  • restore UTC offsets on notification timestamps at the response boundary
  • use a stable timestamp-and-id cursor and reject invalid cursors
  • refresh relative time labels while the view stays open
  • accept same-origin absolute notification targets without weakening target validation

Testing

  • pytest tests/test_notifications_unread.py
  • notification model and service-worker target tests
  • production frontend build

Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
@hamzamerzic hamzamerzic added area: backend Server and API behavior bug Something isn't working labels Jul 28, 2026
@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Closing as fully superseded: after refreshing this branch onto current main, GitHub reports a zero-file diff and the branch tree is byte-identical to main. The reviewed notification-time/history work is already present through #304 (with the navigation/offline follow-up in #326), so merging this history-only duplicate would add no code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: backend Server and API behavior bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant