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

Dictate, review, and send mobile conversation replies #951

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

Evidence

The mobile New issue flow already supports explicit voice capture and transcript review (frontend/voice-issue-capture.js), while assigned issue, pull-request, and unread-update reply composers in frontend/index.html remain keyboard-only. All 478 historical issue titles and recent commits were checked; existing voice issues #929-#936 cover New issue capture only, and there are no open pull requests.

User impact

Mobile operators can dictate, review, edit, and deliberately append or replace replies before using the existing reliable Post / Comment & next / Reply, mark read & next flows. Dictation never sends or advances automatically.

Acceptance criteria

  • Issue, pull-request, and update composers expose accessible Dictate reply controls on supported browsers.
  • Final speech segments accumulate once and stop into editable transcript review.
  • Users explicitly append to or replace existing drafts, respecting the 10,000-character limit.
  • Pending transcripts are scoped to confirmed account and exact conversation target and survive reload without leaking across targets.
  • Closing or advancing aborts active recognition; permission/error/unsupported paths preserve keyboard entry.
  • Existing online/offline delivery and idempotency behavior remains unchanged after text insertion.
  • Behavioral tests cover the complete flow and the full suite remains green.
## Evidence The mobile New issue flow already supports explicit voice capture and transcript review (`frontend/voice-issue-capture.js`), while assigned issue, pull-request, and unread-update reply composers in `frontend/index.html` remain keyboard-only. All 478 historical issue titles and recent commits were checked; existing voice issues #929-#936 cover New issue capture only, and there are no open pull requests. ## User impact Mobile operators can dictate, review, edit, and deliberately append or replace replies before using the existing reliable Post / Comment & next / Reply, mark read & next flows. Dictation never sends or advances automatically. ## Acceptance criteria - Issue, pull-request, and update composers expose accessible Dictate reply controls on supported browsers. - Final speech segments accumulate once and stop into editable transcript review. - Users explicitly append to or replace existing drafts, respecting the 10,000-character limit. - Pending transcripts are scoped to confirmed account and exact conversation target and survive reload without leaking across targets. - Closing or advancing aborts active recognition; permission/error/unsupported paths preserve keyboard entry. - Existing online/offline delivery and idempotency behavior remains unchanged after text insertion. - Behavioral tests cover the complete flow and the full suite remains green.
timmy self-assigned this 2026-08-16 08:23:06 +00:00
timmy closed this issue 2026-08-16 08:39:35 +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#951
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?