[v0.7] Deadline Center

[JUhalt]

Goal

Provide one focused place to see and act on deadlines across the entire manuscript library.

Scope

• Build on the v0.2 reminder/deadline engine rather than creating duplicate reminder semantics.
• Aggregate revision deadlines, proofs, journal follow-ups, and user reminders.
• Upcoming, overdue, and completed/snoozed views where supported by the v0.2 model.
• Sort/filter by urgency, manuscript, journal, and reminder type.
• Direct navigation back to the relevant manuscript/submission.
• Clear approaching/overdue indicators.

Acceptance

• Deadline Center derives its state from the canonical v0.2 reminder data.
• The same dates produce deterministic urgency/status results.
• No duplicate reminder records are created merely by opening the Center.
• A disabled notification system does not reduce Deadline Center functionality.
• Aggregation and urgency calculations are automated-testable.

Roadmap alignment

The v0.7 roadmap also includes readiness/submission obligations from #25/#26 and reviewer-response work from #27.

• Define how explicitly dated obligations from those records enter the existing canonical reminder engine, without adding a parallel scheduler or fabricating deadlines for undated work.
• Each entry links back to the authoritative manuscript, submission/revision round, readiness item, or reviewer-response item that owns it.
• Source edits and supported completion/snooze changes agree across the Center and originating record; journal follow-ups remain active until explicitly cleared or changed.
• Aggregation does not duplicate the same obligation, and missing dates remain visibly undated.

This extends tracking to promises already in the roadmap; it does not establish that these inputs are already implemented.

Release placement

Moved from v0.6 to v0.7 on September 26, 2026, when v0.6 became the Workspace UI release. The Deadline Center takes over the Reminders page in the v0.6 single-window navigation (#54). User-initiated publication checks (#61) can contribute review items. Scope and acceptance above are unchanged.

[JUhalt]

Planning for v0.7 is in draft PR #78, with a design mockup of the Deadlines page linked there.

How this issue's scope maps onto the plan:

• Canonical engine: the Deadlines page reads the same reminder engine as today, and opening it creates no records. Postpone changes the date on the owning record (submission follow-up, decision revision deadline, or reminder), so there is no parallel scheduler or snooze field.
• Readiness and reviewer-response obligations: revision rows show comment progress from the decision that set the deadline. Undated work (a revision without a deadline, a prepared packet with open checklist items) stays visible in a No date group rather than getting an invented date.
• Views and navigation: Overdue, Today, Next 7 days, Later, No date, and Done groups; kind filters and search; each row opens the exact tab and submission it came from.
• Notifications: Windows notifications keep reading the same dated items; turning them off doesn't affect the page.

Slices A (engine) and B (page) cover this issue.

[JUhalt]

Released in v0.7.0 (PR #78, PR #81). Certification: #79.