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

Open progressive mobile My Work in-app before workspace hydration #1413

New Issue
Closed
opened 2026-08-25 23:20:13 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-25 23:20:13 +00:00
Member
Copy Link

Evidence

Progressive My Work renders before optional workspace hydration, but each early card is still an external anchor (frontend/progressive-my-work.js), so tapping assigned work exits the dashboard while the canonical in-app issue/pull workspace is still loading. The existing live snapshot already contains the work item and the dashboard already has issue/pull detail flows after hydration.

This is distinct from #1401/#1403/#1405/#1411, which delivered early list rendering, queue-state handoff, snapshot reuse, and live recovery but retained external card navigation. A scan of all 709 historical issue titles and recent commits found no progressive pre-hydration in-app detail flow. No eligible open issue is assigned to timmy or unassigned; all eight open issues belong to other humans.

Slice

Open an accessible, mobile-safe read-first sheet from progressive My Work without leaving the dashboard. Render snapshot title/context/reason safely, preserve an explicit validated Gitea link, restore focus on close, and transfer the open item through the existing progressive handoff so hydrated code can adopt it.

Acceptance

  • Tapping a progressive card stays on the dashboard and opens the read-first sheet.
  • User-controlled title/context/reason are escaped; unsafe or missing external URLs never become links.
  • Close and Escape restore focus to the originating card.
  • Controls are at least 44px and the sheet fits a 320px viewport with safe-area padding and no horizontal overflow.
  • Handoff exposes the open work identity exactly once for canonical hydrated adoption while preserving the existing selected-filter and live-snapshot handoffs.
  • Focused tests, full suite, and Gitea Actions pass.
## Evidence Progressive My Work renders before optional workspace hydration, but each early card is still an external anchor (`frontend/progressive-my-work.js`), so tapping assigned work exits the dashboard while the canonical in-app issue/pull workspace is still loading. The existing live snapshot already contains the work item and the dashboard already has issue/pull detail flows after hydration. This is distinct from #1401/#1403/#1405/#1411, which delivered early list rendering, queue-state handoff, snapshot reuse, and live recovery but retained external card navigation. A scan of all 709 historical issue titles and recent commits found no progressive pre-hydration in-app detail flow. No eligible open issue is assigned to timmy or unassigned; all eight open issues belong to other humans. ## Slice Open an accessible, mobile-safe read-first sheet from progressive My Work without leaving the dashboard. Render snapshot title/context/reason safely, preserve an explicit validated Gitea link, restore focus on close, and transfer the open item through the existing progressive handoff so hydrated code can adopt it. ## Acceptance - Tapping a progressive card stays on the dashboard and opens the read-first sheet. - User-controlled title/context/reason are escaped; unsafe or missing external URLs never become links. - Close and Escape restore focus to the originating card. - Controls are at least 44px and the sheet fits a 320px viewport with safe-area padding and no horizontal overflow. - Handoff exposes the open work identity exactly once for canonical hydrated adoption while preserving the existing selected-filter and live-snapshot handoffs. - Focused tests, full suite, and Gitea Actions pass.
timmy was assigned by rockachopa 2026-08-25 23:20:13 +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#1413
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?