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

Lazy-load the complete pull request workspace #541

New Issue
Closed
opened 2026-08-11 04:49:06 +00:00 by timmy · 0 comments
timmy commented 2026-08-11 04:49:06 +00:00
Owner
Copy Link

Problem

The content-addressed dashboard runtime on origin/main is 100,717 bytes gzip, only 1,683 bytes below its 100 KiB budget. Every launch downloads and parses pull-request and review-sheet code even when the operator only triages issues, Today, Later, or unread updates. Read-only audit measured that removing only pull-sheet.js and review-sheet.js reduces core gzip by 4,697 bytes before extracting their orchestration from dashboard.js.

Vertical slice

Lazy-load one content-addressed pull-workflow chunk when an assigned pull, requested review, saved offline pull, or direct pull/review route is opened. Concurrent opens share one load. A failed chunk leaves My Work usable and offers an accessible retry. The service worker precaches the exact chunk so installed offline review remains available.

Acceptance criteria

  • Core runtime is no more than 95 KiB gzip and excludes pull/review helpers.
  • Pull/review entry points load the feature once and then preserve existing read, comment, review, merge, routing, and offline behavior.
  • Load failure is bounded, announced accessibly, retryable without reload, and does not disable My Work.
  • The exact feature revision is precached for cold-offline installed use.
  • Changing feature-only source leaves the core runtime URL unchanged while changing feature and shell revisions.
  • Focused behavioral tests and the full suite pass.

Non-duplication evidence

All 273 historical issue titles and recent commits through 3605c42 were reviewed. No prior issue implements a pull/review workflow chunk. #537 lazy-loads mobile issue capture only; #217, #355, #445, #517, and #521 concern pull/review behavior rather than runtime partitioning.

## Problem The content-addressed dashboard runtime on `origin/main` is 100,717 bytes gzip, only 1,683 bytes below its 100 KiB budget. Every launch downloads and parses pull-request and review-sheet code even when the operator only triages issues, Today, Later, or unread updates. Read-only audit measured that removing only `pull-sheet.js` and `review-sheet.js` reduces core gzip by 4,697 bytes before extracting their orchestration from `dashboard.js`. ## Vertical slice Lazy-load one content-addressed pull-workflow chunk when an assigned pull, requested review, saved offline pull, or direct pull/review route is opened. Concurrent opens share one load. A failed chunk leaves My Work usable and offers an accessible retry. The service worker precaches the exact chunk so installed offline review remains available. ## Acceptance criteria - Core runtime is no more than 95 KiB gzip and excludes pull/review helpers. - Pull/review entry points load the feature once and then preserve existing read, comment, review, merge, routing, and offline behavior. - Load failure is bounded, announced accessibly, retryable without reload, and does not disable My Work. - The exact feature revision is precached for cold-offline installed use. - Changing feature-only source leaves the core runtime URL unchanged while changing feature and shell revisions. - Focused behavioral tests and the full suite pass. ## Non-duplication evidence All 273 historical issue titles and recent commits through `3605c42` were reviewed. No prior issue implements a pull/review workflow chunk. #537 lazy-loads mobile issue capture only; #217, #355, #445, #517, and #521 concern pull/review behavior rather than runtime partitioning.
timmy self-assigned this 2026-08-11 04:49:06 +00:00
timmy closed this issue 2026-08-11 04:55:20 +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#541
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?