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

Defer the mobile workspace bundle behind an offline-safe bootstrap #996

New Issue
Closed
opened 2026-08-17 00:51:49 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-17 00:51:49 +00:00
Member
Copy Link

User problem

Mobile Home currently parser-blocks on an 85+ KiB gzip workspace aggregate before the core runtime can start, even though the shell can paint independently. On constrained phones this delays first feedback and couples optional workflow delivery to initial navigation.

Evidence

src/frontend_bundle.py injects feature-today-timer as an eager script and precaches it in the required shell. Current build output is about 187 KiB gzip across the two parser-blocking scripts. Historical issue/commit review found prior feature chunking, but no issue that removes this remaining eager feature script or provides a truthful bootstrap failure state.

Acceptance

  • Ship exactly one parser-blocking content-addressed runtime script.
  • Single-flight load the workspace feature before dashboard controllers initialize.
  • A workspace load failure keeps the rendered shell available and announces actionable retry guidance.
  • Cache the workspace as an optional, failure-isolated offline feature rather than a required install dependency.
  • Initial parser-blocking JavaScript remains at or below 100 KiB gzip.
  • Focused tests, full unit suite, and packaged mobile Home/Insights browser journey pass.
## User problem Mobile Home currently parser-blocks on an 85+ KiB gzip workspace aggregate before the core runtime can start, even though the shell can paint independently. On constrained phones this delays first feedback and couples optional workflow delivery to initial navigation. ## Evidence `src/frontend_bundle.py` injects `feature-today-timer` as an eager script and precaches it in the required shell. Current build output is about 187 KiB gzip across the two parser-blocking scripts. Historical issue/commit review found prior feature chunking, but no issue that removes this remaining eager feature script or provides a truthful bootstrap failure state. ## Acceptance - Ship exactly one parser-blocking content-addressed runtime script. - Single-flight load the workspace feature before dashboard controllers initialize. - A workspace load failure keeps the rendered shell available and announces actionable retry guidance. - Cache the workspace as an optional, failure-isolated offline feature rather than a required install dependency. - Initial parser-blocking JavaScript remains at or below 100 KiB gzip. - Focused tests, full unit suite, and packaged mobile Home/Insights browser journey pass.
timmy was assigned by rockachopa 2026-08-17 00:51:49 +00:00
timmy closed this issue 2026-08-17 02:52:40 +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#996
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?