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

Add a mobile Following queue for watched issues #1293

New Issue
Closed
opened 2026-08-23 03:35:32 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 03:35:32 +00:00
Owner
Copy Link

Problem

Mobile Search can now watch an unassigned issue, but the confirmed action is a dead end: users cannot revisit a quiet watched issue without remembering and searching for it again. The mobile Queues sheet has no Following destination, and Updates only shows new activity.

Evidence

  • frontend/search-preview.js confirms watch state but only promises future activity in Updates.
  • frontend/index.html lists all mobile queues but has no watched-work collection.
  • Current issue/PR history contains only #1290/#1291 for the per-issue Watch action; no issue, PR, release, or recent commit implements a Following collection.
  • Current open issues are assigned to other humans/agents; none is eligible or overlaps this flow.

Vertical slice

Complete discover → watch → revisit → open → stop watching with an encrypted, account-scoped, bounded Following registry synchronized across signed-in devices. Confirmed Gitea subscription mutations update the registry; a mobile Following queue lists canonical issue details and opens the existing Search Preview. Following remains read-first and must not affect Work recommendations or active-queue urgency.

Acceptance criteria

  • A Gitea-confirmed Watch adds one canonical issue to the signed-in account's Following collection; repeated Watch is idempotent.
  • A Gitea-confirmed Stop watching removes it; failed/unconfirmed mutations preserve prior state.
  • Following is account-isolated, encrypted at rest, revisioned, and bounded.
  • Mobile Queues exposes Following with an accurate count without recommending it as actionable work.
  • Following renders repository, issue number, title, state, and update time; opening an item reuses Search Preview.
  • The 320×568 mobile layout has no horizontal overflow and all controls are at least 44px.
  • Behavioral API/controller tests, rendered mobile test, and the full suite pass.
## Problem Mobile Search can now watch an unassigned issue, but the confirmed action is a dead end: users cannot revisit a quiet watched issue without remembering and searching for it again. The mobile Queues sheet has no Following destination, and Updates only shows new activity. ## Evidence - `frontend/search-preview.js` confirms watch state but only promises future activity in Updates. - `frontend/index.html` lists all mobile queues but has no watched-work collection. - Current issue/PR history contains only #1290/#1291 for the per-issue Watch action; no issue, PR, release, or recent commit implements a Following collection. - Current open issues are assigned to other humans/agents; none is eligible or overlaps this flow. ## Vertical slice Complete **discover → watch → revisit → open → stop watching** with an encrypted, account-scoped, bounded Following registry synchronized across signed-in devices. Confirmed Gitea subscription mutations update the registry; a mobile Following queue lists canonical issue details and opens the existing Search Preview. Following remains read-first and must not affect Work recommendations or active-queue urgency. ## Acceptance criteria - A Gitea-confirmed Watch adds one canonical issue to the signed-in account's Following collection; repeated Watch is idempotent. - A Gitea-confirmed Stop watching removes it; failed/unconfirmed mutations preserve prior state. - Following is account-isolated, encrypted at rest, revisioned, and bounded. - Mobile Queues exposes Following with an accurate count without recommending it as actionable work. - Following renders repository, issue number, title, state, and update time; opening an item reuses Search Preview. - The 320×568 mobile layout has no horizontal overflow and all controls are at least 44px. - Behavioral API/controller tests, rendered mobile test, and the full suite pass.
timmy self-assigned this 2026-08-23 03:35:32 +00:00
timmy closed this issue 2026-08-23 04:57: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#1293
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?