stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Retire completed work from the synced Today plan #359

New Issue
Closed
opened 2026-08-09 01:10:28 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 01:10:28 +00:00
Owner
Copy Link

Problem

An authoritative fully-paginated My Work refresh prunes completed or otherwise ineligible Today identities only from local storage. The synced server plan retains them, so the next sync restores invisible stale work and can keep one of the five Today slots occupied.

User impact

Completing an issue, review, or unread-update task should retire it from Today on every device and immediately free its slot, including when the retirement is first observed offline.

Acceptance criteria

  • An authoritative complete My Work reconciliation reports retired Today identities and queues idempotent synced removals before dropping them locally.
  • Partial, paginated, stale, or degraded snapshots never retire unseen Today work.
  • Offline retirement remains queued and converges on reconnect; repeated reconciliation does not create duplicate effective removals.
  • A second device sees the reduced server plan and can use the freed slot without a 409.
  • No extra writes occur when every Today identity remains eligible.
  • Focused behavioral tests and the full suite pass.
## Problem An authoritative fully-paginated My Work refresh prunes completed or otherwise ineligible Today identities only from local storage. The synced server plan retains them, so the next sync restores invisible stale work and can keep one of the five Today slots occupied. ## User impact Completing an issue, review, or unread-update task should retire it from Today on every device and immediately free its slot, including when the retirement is first observed offline. ## Acceptance criteria - An authoritative complete My Work reconciliation reports retired Today identities and queues idempotent synced removals before dropping them locally. - Partial, paginated, stale, or degraded snapshots never retire unseen Today work. - Offline retirement remains queued and converges on reconnect; repeated reconciliation does not create duplicate effective removals. - A second device sees the reduced server plan and can use the freed slot without a 409. - No extra writes occur when every Today identity remains eligible. - Focused behavioral tests and the full suite pass.
timmy closed this issue 2026-08-09 01:18:42 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#359
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?