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

Review recent activity before posting a Today update #1060

New Issue
Closed
opened 2026-08-18 03:51:43 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-18 03:51:43 +00:00
Member
Copy Link

User problem

The active Today Add update sheet opens directly into an empty composer. On a phone, the operator cannot review the newest teammate response, prior update, or open question before posting, which makes stale or duplicate progress updates likely.

Evidence

  • frontend/index.html defines the progress composer without any conversation context.
  • frontend/today-progress.js restores only the local draft and photos before focusing the editor.
  • The assigned issue and pull conversation endpoints already return bounded newest-page data when page is omitted.
  • Recent #1052-#1059 work covers text, evidence, retry integrity, and dictation, but not read-before-write context. Historical issue and recent commit title review found no equivalent slice.

Acceptance criteria

  • Opening Add update loads the newest 20 messages for the exact active issue or pull request and renders author, timestamp, and safe Markdown in chronological order.
  • Load older prepends one bounded page without duplicates and preserves the reading position.
  • A stale response cannot paint after the active item changes or the sheet closes.
  • Offline/API failure shows an actionable retry while the existing save, dictate, evidence, and post controls remain usable.
  • At 320px width the activity region wraps long content, has no horizontal overflow, and retry/load controls are at least 44px tall.
  • Behavioral tests cover issue/pull routing, stale-response rejection, retry, pagination, and unchanged composer availability.
## User problem The active Today **Add update** sheet opens directly into an empty composer. On a phone, the operator cannot review the newest teammate response, prior update, or open question before posting, which makes stale or duplicate progress updates likely. ## Evidence - `frontend/index.html` defines the progress composer without any conversation context. - `frontend/today-progress.js` restores only the local draft and photos before focusing the editor. - The assigned issue and pull conversation endpoints already return bounded newest-page data when `page` is omitted. - Recent #1052-#1059 work covers text, evidence, retry integrity, and dictation, but not read-before-write context. Historical issue and recent commit title review found no equivalent slice. ## Acceptance criteria - Opening Add update loads the newest 20 messages for the exact active issue or pull request and renders author, timestamp, and safe Markdown in chronological order. - Load older prepends one bounded page without duplicates and preserves the reading position. - A stale response cannot paint after the active item changes or the sheet closes. - Offline/API failure shows an actionable retry while the existing save, dictate, evidence, and post controls remain usable. - At 320px width the activity region wraps long content, has no horizontal overflow, and retry/load controls are at least 44px tall. - Behavioral tests cover issue/pull routing, stale-response rejection, retry, pagination, and unchanged composer availability.
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#1060
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?