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

Explain Following changes before acknowledging review #1322

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

Evidence

Following currently exposes only has_unseen_change, renders every changed card as generic “New activity”, and acknowledges an exact revision from onOpened before its conversation request finishes. A failed conversation request can therefore clear unseen work without showing the operator what changed. Historical title review found no issue covering change context or load-gated acknowledgement.

User flow

Following → changed-first review → see a truthful state/title/activity reason and messages marked “New since last review” → acknowledge only after detail and conversation context load successfully. A conversation failure keeps the revision unseen and offers Retry/Keep for later.

Acceptance

  • API items expose the prior reviewed marker for unseen revisions without exposing encrypted store internals for unchanged items.
  • Cards distinguish closed/reopened/title-changed/activity-only revisions.
  • Conversation comments newer than the reviewed marker are highlighted and counted.
  • Following acknowledgement occurs only after conversation context succeeds; failure leaves the exact revision unseen.
  • Concurrent newer revisions remain unseen.
  • Packaged mobile controls remain at least 44px with no horizontal overflow.
  • Focused and full test suites pass.
## Evidence Following currently exposes only `has_unseen_change`, renders every changed card as generic “New activity”, and acknowledges an exact revision from `onOpened` before its conversation request finishes. A failed conversation request can therefore clear unseen work without showing the operator what changed. Historical title review found no issue covering change context or load-gated acknowledgement. ## User flow Following → changed-first review → see a truthful state/title/activity reason and messages marked “New since last review” → acknowledge only after detail and conversation context load successfully. A conversation failure keeps the revision unseen and offers Retry/Keep for later. ## Acceptance - API items expose the prior reviewed marker for unseen revisions without exposing encrypted store internals for unchanged items. - Cards distinguish closed/reopened/title-changed/activity-only revisions. - Conversation comments newer than the reviewed marker are highlighted and counted. - Following acknowledgement occurs only after conversation context succeeds; failure leaves the exact revision unseen. - Concurrent newer revisions remain unseen. - Packaged mobile controls remain at least 44px with no horizontal overflow. - Focused and full test suites pass.
timmy was assigned by rockachopa 2026-08-23 21:20:42 +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#1322
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?