Carry mobile review feedback into the authenticated Gitea handoff #129

Closed
opened 2026-08-06 18:49:44 +00:00 by timmy · 0 comments
Owner

User problem

The mobile requested-review sheet lets reviewers inspect and mark files reviewed, but it cannot capture per-file observations or carry an overall decision into the existing authenticated Gitea handoff. Reviewers must reconstruct feedback from memory after leaving the dashboard.

Evidence

  • frontend/index.html exposes changed files, progress, and an "Open in Gitea" link but no feedback draft controls.
  • frontend/review-sheet.js persists only reviewed filenames by repository, PR, and head SHA.
  • Historical issue/PR title review through #128 and recent origin/main history show no shipped review-note or decision-draft workflow.

Acceptance criteria

  • Persist per-file notes, overall summary, and intended decision for the exact repository/PR/head SHA.
  • Restore the draft after closing/reloading; a new head SHA starts a fresh draft.
  • Copy structured Markdown containing non-empty notes in file order and the summary/decision before opening the authenticated Gitea PR.
  • Clipboard failure keeps feedback available in a selectable fallback and does not navigate away.
  • Controls remain usable on a 320px-wide phone with 44px touch targets.
  • Keep the dashboard read-only: introduce no Gitea mutation endpoint.
  • Add behavioral tests and keep the complete suite green.
## User problem The mobile requested-review sheet lets reviewers inspect and mark files reviewed, but it cannot capture per-file observations or carry an overall decision into the existing authenticated Gitea handoff. Reviewers must reconstruct feedback from memory after leaving the dashboard. ## Evidence - `frontend/index.html` exposes changed files, progress, and an "Open in Gitea" link but no feedback draft controls. - `frontend/review-sheet.js` persists only reviewed filenames by repository, PR, and head SHA. - Historical issue/PR title review through #128 and recent `origin/main` history show no shipped review-note or decision-draft workflow. ## Acceptance criteria - Persist per-file notes, overall summary, and intended decision for the exact repository/PR/head SHA. - Restore the draft after closing/reloading; a new head SHA starts a fresh draft. - Copy structured Markdown containing non-empty notes in file order and the summary/decision before opening the authenticated Gitea PR. - Clipboard failure keeps feedback available in a selectable fallback and does not navigate away. - Controls remain usable on a 320px-wide phone with 44px touch targets. - Keep the dashboard read-only: introduce no Gitea mutation endpoint. - Add behavioral tests and keep the complete suite green.
timmy self-assigned this 2026-08-06 18:49:44 +00:00
timmy closed this issue 2026-08-06 18:57:14 +00:00
Sign in to join this conversation.
No Milestone
No project
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#129
No description provided.