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

Reuse the progressive live snapshot during mobile workspace hydration #1405

New Issue
Closed
opened 2026-08-25 18:52:48 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-25 18:52:48 +00:00
Member
Copy Link

Problem

Mobile startup fetches api/v1/live in progressive-my-work.js, then discards the successful snapshot during handoff. After optional workspace hydration, dashboard.js starts a second poller and immediately performs another revisionless fetch. On constrained links this duplicates transfer/render work and can make My Work jump during hydration.

Vertical slice

Transfer a successful progressive snapshot, its revision tokens, and freshness metadata into the full context poller. Adopt and render it once without fetching again, then schedule revision-conditional revalidation from its freshness deadline. Preserve normal immediate fetch behavior when no valid progressive snapshot exists.

Acceptance tests

  • Progressive handoff exposes a successful live snapshot exactly once alongside selected queue state.
  • The context poller adopts the seed, renders it, stores revisions, and schedules from freshness without a network call.
  • The next automatic request carries context/events/notifications revisions.
  • Failed progressive loading falls back to the existing immediate full-workspace fetch.
  • Packaged throttled mobile bootstrap makes exactly one revisionless live request through hydration.

No historical issue or recent commit covers progressive live-snapshot ownership transfer; #1401 added progressive hydration and #1403 transferred only queue selection.

## Problem Mobile startup fetches `api/v1/live` in `progressive-my-work.js`, then discards the successful snapshot during handoff. After optional workspace hydration, `dashboard.js` starts a second poller and immediately performs another revisionless fetch. On constrained links this duplicates transfer/render work and can make My Work jump during hydration. ## Vertical slice Transfer a successful progressive snapshot, its revision tokens, and freshness metadata into the full context poller. Adopt and render it once without fetching again, then schedule revision-conditional revalidation from its freshness deadline. Preserve normal immediate fetch behavior when no valid progressive snapshot exists. ## Acceptance tests - Progressive handoff exposes a successful live snapshot exactly once alongside selected queue state. - The context poller adopts the seed, renders it, stores revisions, and schedules from freshness without a network call. - The next automatic request carries context/events/notifications revisions. - Failed progressive loading falls back to the existing immediate full-workspace fetch. - Packaged throttled mobile bootstrap makes exactly one revisionless live request through hydration. No historical issue or recent commit covers progressive live-snapshot ownership transfer; #1401 added progressive hydration and #1403 transferred only queue selection.
timmy was assigned by rockachopa 2026-08-25 18:52:48 +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#1405
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?