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

Lazy-load the mobile issue capture workflow #537

New Issue
Closed
opened 2026-08-11 03:20:12 +00:00 by timmy · 0 comments
timmy commented 2026-08-11 03:20:12 +00:00
Owner
Copy Link

Product problem

The content-addressed PWA runtime now transfers about 100 KiB compressed and every launch parses all 53 page modules, including issue capture and attachment code even when the operator only triages My Work. The existing runtime budget is nearly exhausted.

Vertical slice

Introduce deterministic content-addressed feature chunks and move the complete New issue flow (capture sheet, attachments, and create-and-start integration) behind a single-flight loader. Preserve atomic offline precaching so capture still works from an installed shell. Show an accessible loading/error state and allow retry.

Acceptance criteria

  • Initial dashboard runtime does not contain the issue-capture feature sources.
  • Tapping New loads the capture chunk once, opens the existing sheet, and concurrent triggers share one request.
  • Failed chunk loading reports an accessible retry state; retry can open the workflow without reloading the page.
  • Feature chunk and core runtime URLs are deterministic/content-addressed; changing capture source leaves the core URL stable.
  • The service worker atomically precaches the core and capture chunk so an installed shell can open capture offline.
  • Focused browser/build/service-worker tests and the full suite pass.

Duplicate evidence

No open issue or PR covers runtime partitioning or lazy-loaded capture. Historical work #379 bundled classic requests, #417/#431 compressed the monolith, and #511 content-addressed the complete shell; none split execution into stable feature chunks.

## Product problem The content-addressed PWA runtime now transfers about 100 KiB compressed and every launch parses all 53 page modules, including issue capture and attachment code even when the operator only triages My Work. The existing runtime budget is nearly exhausted. ## Vertical slice Introduce deterministic content-addressed feature chunks and move the complete New issue flow (capture sheet, attachments, and create-and-start integration) behind a single-flight loader. Preserve atomic offline precaching so capture still works from an installed shell. Show an accessible loading/error state and allow retry. ## Acceptance criteria - Initial dashboard runtime does not contain the issue-capture feature sources. - Tapping New loads the capture chunk once, opens the existing sheet, and concurrent triggers share one request. - Failed chunk loading reports an accessible retry state; retry can open the workflow without reloading the page. - Feature chunk and core runtime URLs are deterministic/content-addressed; changing capture source leaves the core URL stable. - The service worker atomically precaches the core and capture chunk so an installed shell can open capture offline. - Focused browser/build/service-worker tests and the full suite pass. ## Duplicate evidence No open issue or PR covers runtime partitioning or lazy-loaded capture. Historical work #379 bundled classic requests, #417/#431 compressed the monolith, and #511 content-addressed the complete shell; none split execution into stable feature chunks.
timmy closed this issue 2026-08-11 03:32:15 +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
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#537
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?