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

Read the current conversation inside mobile Search preview #803

New Issue
Closed
opened 2026-08-14 05:51:05 +00:00 by timmy · 0 comments
timmy commented 2026-08-14 05:51:05 +00:00
Owner
Copy Link

Problem

Mobile Search preview exposes the issue or pull-request description and immediate planning actions, but not the conversation that may contain newer decisions, blockers, or review feedback. Operators can currently queue, defer, start, reopen, or review work from a stale description.

Evidence

  • frontend/dashboard.js fetches and renders /preview, then exposes planning actions without comments.
  • frontend/search-preview.js manages resumable Previous/Next preview navigation but no conversation state.
  • Existing bounded comment paging in src/gitea_proxy.py is restricted to assigned-issue surfaces and cannot serve arbitrary accessible Search results.
  • All 405 historical issue titles, 394 PRs, 393 releases, and recent commits through 2406d24 were checked. Existing conversation work covers My Work/Updates, while Search history #781–#801 covers session restore, paging, filters, sharing, opening work, and planning—not conversation context.

Acceptance criteria

  • Opening an issue or pull request from Search renders its core preview immediately, then progressively loads the newest bounded conversation page.
  • Comments render author, timestamp, and safe Markdown.
  • An older-page control prepends prior comments without duplicates and disappears at the beginning.
  • A failed conversation request leaves preview/planning/navigation usable and offers an in-place retry.
  • Previous/Next ignores stale responses so comments from one result never appear on another.
  • The API validates repository/index, preserves Gitea authorization, and bounds page size.
  • Behavioral tests cover issue and pull conversations, paging, failure/retry, and stale-response isolation.

Implementation must use strict RED→GREEN TDD.

## Problem Mobile Search preview exposes the issue or pull-request description and immediate planning actions, but not the conversation that may contain newer decisions, blockers, or review feedback. Operators can currently queue, defer, start, reopen, or review work from a stale description. ## Evidence - `frontend/dashboard.js` fetches and renders `/preview`, then exposes planning actions without comments. - `frontend/search-preview.js` manages resumable Previous/Next preview navigation but no conversation state. - Existing bounded comment paging in `src/gitea_proxy.py` is restricted to assigned-issue surfaces and cannot serve arbitrary accessible Search results. - All 405 historical issue titles, 394 PRs, 393 releases, and recent commits through `2406d24` were checked. Existing conversation work covers My Work/Updates, while Search history #781–#801 covers session restore, paging, filters, sharing, opening work, and planning—not conversation context. ## Acceptance criteria - Opening an issue or pull request from Search renders its core preview immediately, then progressively loads the newest bounded conversation page. - Comments render author, timestamp, and safe Markdown. - An older-page control prepends prior comments without duplicates and disappears at the beginning. - A failed conversation request leaves preview/planning/navigation usable and offers an in-place retry. - Previous/Next ignores stale responses so comments from one result never appear on another. - The API validates repository/index, preserves Gitea authorization, and bounds page size. - Behavioral tests cover issue and pull conversations, paging, failure/retry, and stale-response isolation. Implementation must use strict RED→GREEN TDD.
timmy self-assigned this 2026-08-14 05:51:05 +00:00
timmy closed this issue 2026-08-14 06:07: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#803
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?