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

Recover conflicted Week-to-Today transfers #1254

New Issue
Closed
opened 2026-08-22 06:54:15 +00:00 by timmy · 0 comments
timmy commented 2026-08-22 06:54:15 +00:00
Owner
Copy Link

Problem

A durable FIFO Week Ahead → Today transfer that receives a 409 is preserved at the queue head, but mobile users only see “Saved pull needs review.” There is no action to rebase it against current plans or discard only that intent, so every later queued transfer remains blocked.

Product slice

Expose a mobile recovery review for the conflicted head transfer. Users can Add using current plans (rebase against current Today/Week revisions, retaining the operation identity and capacity decision) or Keep in Week Ahead (discard only that local intent). Already-resolved intents clear safely; subsequent FIFO entries continue.

Acceptance

  • Conflict survives reload and exposes item/source/current-plan context.
  • Rebase uses fresh revisions and drains subsequent entries exactly once.
  • Discard mutates no server plan and advances only the local FIFO head.
  • Already moved/removed work is cleared without duplication or queue deadlock.
  • Recovery actions are accessible, >=44px, and do not overflow at 320×568 and 390×844.
  • Focused behavioral tests, packaged mobile test, and full suite pass.

Historical title and recent-commit audit found no duplicate; adjacent #1242, #1244, #1246, and #1249 delivered transfer, capacity confirmation, durability, and FIFO—not conflict recovery.

## Problem A durable FIFO Week Ahead → Today transfer that receives a 409 is preserved at the queue head, but mobile users only see “Saved pull needs review.” There is no action to rebase it against current plans or discard only that intent, so every later queued transfer remains blocked. ## Product slice Expose a mobile recovery review for the conflicted head transfer. Users can **Add using current plans** (rebase against current Today/Week revisions, retaining the operation identity and capacity decision) or **Keep in Week Ahead** (discard only that local intent). Already-resolved intents clear safely; subsequent FIFO entries continue. ## Acceptance - Conflict survives reload and exposes item/source/current-plan context. - Rebase uses fresh revisions and drains subsequent entries exactly once. - Discard mutates no server plan and advances only the local FIFO head. - Already moved/removed work is cleared without duplication or queue deadlock. - Recovery actions are accessible, >=44px, and do not overflow at 320×568 and 390×844. - Focused behavioral tests, packaged mobile test, and full suite pass. Historical title and recent-commit audit found no duplicate; adjacent #1242, #1244, #1246, and #1249 delivered transfer, capacity confirmation, durability, and FIFO—not conflict recovery.
timmy self-assigned this 2026-08-22 06:54:15 +00:00
timmy closed this issue 2026-08-22 07:28:13 +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
timmy
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#1254
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?