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

Make mobile My Work usable before optional workspace hydration #1401

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

Problem

The dashboard blocks all mobile My Work initialization on both the Today and planning feature chunks. The mandatory startup path is about 259 KiB gzip; a delay or failure in either optional workflow leaves assigned work unavailable behind a global Workspace unavailable state.

Vertical slice

Load a small blocking work-core bundle for My Work and queue navigation, then hydrate Today and planning independently. Optional chunk failures must remain local and retryable while assigned work stays usable.

Acceptance criteria

  • Core plus blocking work-core is at least 40% smaller than the current 259,135-byte mandatory path and remains within an explicit test budget.
  • My Work renders and queue navigation is actionable before Today and planning chunks settle.
  • Aborting Today or planning loading does not block My Work or produce uncaught errors.
  • Each failed optional chunk can retry single-flight and activate without a page reload.
  • Optional chunks remain cached independently for offline reuse.
  • Existing Today, planning, offline delivery, and packaged mobile journeys remain green.

Evidence / non-duplication

Current frontend/dashboard.js awaits loadWorkspace() before initialization, while frontend/workspace-bootstrap.js groups today-timer and planning in one Promise.all. Historical issues #996, #1116, and #1124 deferred, concurrently fetched, and retried the monolithic workspace respectively; none isolates My Work startup or optional-workflow failures. No current open issue or PR covers progressive My Work activation.

## Problem The dashboard blocks all mobile My Work initialization on both the Today and planning feature chunks. The mandatory startup path is about 259 KiB gzip; a delay or failure in either optional workflow leaves assigned work unavailable behind a global Workspace unavailable state. ## Vertical slice Load a small blocking work-core bundle for My Work and queue navigation, then hydrate Today and planning independently. Optional chunk failures must remain local and retryable while assigned work stays usable. ## Acceptance criteria - Core plus blocking work-core is at least 40% smaller than the current 259,135-byte mandatory path and remains within an explicit test budget. - My Work renders and queue navigation is actionable before Today and planning chunks settle. - Aborting Today or planning loading does not block My Work or produce uncaught errors. - Each failed optional chunk can retry single-flight and activate without a page reload. - Optional chunks remain cached independently for offline reuse. - Existing Today, planning, offline delivery, and packaged mobile journeys remain green. ## Evidence / non-duplication Current `frontend/dashboard.js` awaits `loadWorkspace()` before initialization, while `frontend/workspace-bootstrap.js` groups `today-timer` and `planning` in one `Promise.all`. Historical issues #996, #1116, and #1124 deferred, concurrently fetched, and retried the monolithic workspace respectively; none isolates My Work startup or optional-workflow failures. No current open issue or PR covers progressive My Work activation.
rockachopa self-assigned this 2026-08-25 16:19:16 +00:00
rockachopa removed their assignment 2026-08-25 16:19:55 +00:00
timmy was assigned by rockachopa 2026-08-25 16:19:55 +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#1401
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?