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

Batch queued Today and Later planning edits #375

New Issue
Closed
opened 2026-08-09 05:55:06 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 05:55:06 +00:00
Member
Copy Link

Product gap

Today and Later reconnect drains currently perform one initial GET followed by one PATCH per queued edit. Fifty offline edits therefore require 51 dashboard requests, 51 upstream identity confirmations, and 50 SQLite write transactions, delaying mobile convergence on intermittent connections.

Vertical slice

Accept bounded ordered batches (maximum 50 operations) on the Today and Later PATCH APIs, apply each batch in one SQLite transaction after one confirmed identity lookup, and return the authoritative snapshot with accepted, duplicate, and rejected operation IDs. Clients submit pending batches directly, delete only explicit receipts, and drain work queued in flight in a later batch.

Acceptance

  • Up to 50 queued Today or Later edits drain with one PATCH per batch and no preliminary GET.
  • One batch uses one account confirmation and one SQLite transaction.
  • Full and partial replay is idempotent and revisions do not increment twice.
  • A Today capacity conflict rejects only that operation while later valid operations continue in order.
  • Failure before commit acknowledges nothing and leaves the durable client queue intact.
  • Edits queued during an in-flight batch are preserved and subsequently drained.
  • Batch size, operation schema, CSRF, and account isolation are enforced.

This behavior is absent from all 190 historical issue titles and recent planning-sync commits through #374.

## Product gap Today and Later reconnect drains currently perform one initial GET followed by one PATCH per queued edit. Fifty offline edits therefore require 51 dashboard requests, 51 upstream identity confirmations, and 50 SQLite write transactions, delaying mobile convergence on intermittent connections. ## Vertical slice Accept bounded ordered batches (maximum 50 operations) on the Today and Later PATCH APIs, apply each batch in one SQLite transaction after one confirmed identity lookup, and return the authoritative snapshot with accepted, duplicate, and rejected operation IDs. Clients submit pending batches directly, delete only explicit receipts, and drain work queued in flight in a later batch. ## Acceptance - Up to 50 queued Today or Later edits drain with one PATCH per batch and no preliminary GET. - One batch uses one account confirmation and one SQLite transaction. - Full and partial replay is idempotent and revisions do not increment twice. - A Today capacity conflict rejects only that operation while later valid operations continue in order. - Failure before commit acknowledges nothing and leaves the durable client queue intact. - Edits queued during an in-flight batch are preserved and subsequently drained. - Batch size, operation schema, CSRF, and account isolation are enforced. This behavior is absent from all 190 historical issue titles and recent planning-sync commits through #374.
timmy was assigned by rockachopa 2026-08-09 05:55:06 +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#375
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?