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

Fetch the mobile workspace concurrently with the core runtime #1116

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

User problem

On a cold mobile launch, the core runtime must finish downloading and execute before the mandatory Today workspace chunk is requested. This serial transfer delays My Work, Today controls, queues, and recovery even though the workspace is content-addressed and safe to fetch early.

Evidence and non-duplication

  • frontend/dashboard.js begins workspace startup only after the core runtime executes.
  • frontend/workspace-bootstrap.js then requests the today-timer chunk.
  • src/frontend_bundle.py emits metadata for that chunk but no preload hint.
  • #996 intentionally moved the workspace out of blocking HTML and mandatory offline installation. This issue preserves deferred execution while parallelizing only its network fetch; it is a distinct follow-up.
  • No open issue or PR covers preload/concurrent workspace transfer.

Acceptance criteria

  • Emit exactly one non-render-blocking script preload for the content-addressed today-timer chunk.
  • Keep workspace execution deferred and keep the chunk outside blocking scripts and mandatory service-worker shell assets.
  • Enforce explicit gzip budgets for the core and mandatory workspace chunks.
  • In a packaged mobile browser test, hold the core response and prove the workspace request begins before core completion; afterward, Home is functional and the workspace transfers once.
  • Focused and full suites pass.
## User problem On a cold mobile launch, the core runtime must finish downloading and execute before the mandatory Today workspace chunk is requested. This serial transfer delays My Work, Today controls, queues, and recovery even though the workspace is content-addressed and safe to fetch early. ## Evidence and non-duplication - `frontend/dashboard.js` begins workspace startup only after the core runtime executes. - `frontend/workspace-bootstrap.js` then requests the `today-timer` chunk. - `src/frontend_bundle.py` emits metadata for that chunk but no preload hint. - #996 intentionally moved the workspace out of blocking HTML and mandatory offline installation. This issue preserves deferred execution while parallelizing only its network fetch; it is a distinct follow-up. - No open issue or PR covers preload/concurrent workspace transfer. ## Acceptance criteria - Emit exactly one non-render-blocking script preload for the content-addressed `today-timer` chunk. - Keep workspace execution deferred and keep the chunk outside blocking scripts and mandatory service-worker shell assets. - Enforce explicit gzip budgets for the core and mandatory workspace chunks. - In a packaged mobile browser test, hold the core response and prove the workspace request begins before core completion; afterward, Home is functional and the workspace transfers once. - Focused and full suites pass.
timmy was assigned by rockachopa 2026-08-19 06:22:42 +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#1116
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?