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

Make Security Center a Back-safe mobile investigation flow #1020

New Issue
Closed
opened 2026-08-17 11:46:45 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 11:46:45 +00:00
Owner
Copy Link

Problem

On phone-sized screens, Security Center is one long unaddressable sheet. Authentication alerts and passkey anomalies explain risk but do not hand the operator to the relevant remediation controls; browser/hardware Back can leave the dashboard; and successful revocation does not refresh Security activity to verify the recorded action.

User flow

Turn Security Center into an Activity → Devices → Passkeys investigation flow with a sticky mobile section rail, alert-to-remediation actions, bounded same-document Back behavior, and post-remediation activity refresh.

Acceptance criteria

  • Activity, Devices, and Passkeys are addressable sections with 44px mobile targets and no horizontal overflow.
  • Opening adds one history layer; section navigation is bounded, and Back unwinds sections before closing the sheet without leaving Stackchain.
  • Authentication alerts can open Devices; counter anomalies can open Passkeys.
  • Successful device/passkey revocation refreshes relevant inventory and Security activity so the audit result is visible.
  • Close/Back restores focus to Active devices; failed actions keep context and verify-before-retry guidance.
  • Focused behavioral tests, full suite, packaged mobile release test, CI, and RC release pass.

Evidence / non-duplication

Current security-center.js only toggles hidden, loads all three sections, and renders alert text. Historical #493/#499/#543/#605/#641 delivered activity, passkey management, alerts, lazy loading, and anomaly guidance, but none provides this mobile investigation/remediation/history flow. No open issue or recent commit covers it.

## Problem On phone-sized screens, Security Center is one long unaddressable sheet. Authentication alerts and passkey anomalies explain risk but do not hand the operator to the relevant remediation controls; browser/hardware Back can leave the dashboard; and successful revocation does not refresh Security activity to verify the recorded action. ## User flow Turn Security Center into an Activity → Devices → Passkeys investigation flow with a sticky mobile section rail, alert-to-remediation actions, bounded same-document Back behavior, and post-remediation activity refresh. ## Acceptance criteria - Activity, Devices, and Passkeys are addressable sections with 44px mobile targets and no horizontal overflow. - Opening adds one history layer; section navigation is bounded, and Back unwinds sections before closing the sheet without leaving Stackchain. - Authentication alerts can open Devices; counter anomalies can open Passkeys. - Successful device/passkey revocation refreshes relevant inventory and Security activity so the audit result is visible. - Close/Back restores focus to Active devices; failed actions keep context and verify-before-retry guidance. - Focused behavioral tests, full suite, packaged mobile release test, CI, and RC release pass. ## Evidence / non-duplication Current `security-center.js` only toggles `hidden`, loads all three sections, and renders alert text. Historical #493/#499/#543/#605/#641 delivered activity, passkey management, alerts, lazy loading, and anomaly guidance, but none provides this mobile investigation/remediation/history flow. No open issue or recent commit covers it.
timmy self-assigned this 2026-08-17 11:46:45 +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#1020
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?