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

Lazy-load active devices and security activity #605

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

Problem

The complete Active Devices, passkey management, and Security Activity renderer is shipped in the critical session runtime even though it is only used after opening Active devices. The core gzip bundle has effectively no budget headroom, so optional security-center changes invalidate the entire startup asset and share a blast radius with session expiry and revocation enforcement.

Vertical slice

Move the optional security-center presentation into a content-addressed lazy feature chunk while keeping session enforcement and its API boundary eager. Opening Active devices must single-flight load the chunk, preserve the existing device/passkey/activity flow, and expose retryable accessible failure guidance. The feature remains precached for offline shell availability.

Acceptance

  • Core startup excludes the security-center renderer and gains at least 1 KiB gzip headroom under 96 KiB.
  • Active devices opens through one single-flight feature request and retains device, passkey, pagination, enrollment, and revocation behavior.
  • Chunk failure is accessible and retryable from the same control.
  • Security-center-only changes leave the core runtime digest unchanged.
  • Feature chunk is immutable and included in the atomic service-worker precache.
  • Focus returns correctly when the sheet closes.
  • Full test suite and Gitea Actions pass.

No historical issue or recent commit implements this split; prior lazy-loading work covers issue capture and pull workflows only.

## Problem The complete Active Devices, passkey management, and Security Activity renderer is shipped in the critical session runtime even though it is only used after opening Active devices. The core gzip bundle has effectively no budget headroom, so optional security-center changes invalidate the entire startup asset and share a blast radius with session expiry and revocation enforcement. ## Vertical slice Move the optional security-center presentation into a content-addressed lazy feature chunk while keeping session enforcement and its API boundary eager. Opening Active devices must single-flight load the chunk, preserve the existing device/passkey/activity flow, and expose retryable accessible failure guidance. The feature remains precached for offline shell availability. ## Acceptance - Core startup excludes the security-center renderer and gains at least 1 KiB gzip headroom under 96 KiB. - Active devices opens through one single-flight feature request and retains device, passkey, pagination, enrollment, and revocation behavior. - Chunk failure is accessible and retryable from the same control. - Security-center-only changes leave the core runtime digest unchanged. - Feature chunk is immutable and included in the atomic service-worker precache. - Focus returns correctly when the sheet closes. - Full test suite and Gitea Actions pass. No historical issue or recent commit implements this split; prior lazy-loading work covers issue capture and pull workflows only.
timmy closed this issue 2026-08-12 01:03:14 +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#605
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?