Post reviewed Today summaries to a Gitea status thread #1130

Closed
opened 2026-08-19 12:21:32 +00:00 by rockachopa · 0 comments
Member

Evidence

The mobile Today wrap-up already builds a privacy-reviewed summary, but frontend/today-summary.js can only invoke native share or copy to clipboard. Operators must leave Stackchain, locate the correct Gitea thread, and paste manually. The existing authored outbox already durably and idempotently delivers search-reply comments, so the missing product slice is destination selection and admission from the summary review. Historical issue #1090 deliberately ended at native share/clipboard; no open issue, PR, release, or recent commit implements direct posting.

User flow

  1. Review exact worked/tomorrow items, optional actual time, and note.
  2. Choose Post to Gitea, enter and validate an exact owner/repo#number issue or pull request destination, and review the exact destination beside the comment body.
  3. Confirm once. The reviewed comment is durably admitted to the existing authored outbox with a stable operation ID before the private draft is cleared.
  4. Report truthful queued/delivered state; admission failure preserves every choice for retry. Native sharing remains available.

Acceptance tests

  • A canonical visible destination is required and normalized before confirmation.
  • Confirmation enqueues exactly one search-reply with repository, number, target kind, reviewed body, and stable operation ID.
  • The summary draft clears only after durable admission; rejected admission preserves it.
  • Account changes isolate the draft and pending destination.
  • The rendered 320px mobile sheet has no horizontal overflow, 44px controls, wrapped destination text, and reachable sticky actions.
  • Existing native share/clipboard behavior remains unchanged.
  • Focused tests, full suite, and packaged mobile release journey pass.

Non-duplication

All 559 closed issue records and current open issues were reviewed. #1090 covers only privacy-reviewed native sharing/clipboard. Existing preview-comment/outbox code is reusable infrastructure, not this Today-to-status-thread flow.

## Evidence The mobile Today wrap-up already builds a privacy-reviewed summary, but `frontend/today-summary.js` can only invoke native share or copy to clipboard. Operators must leave Stackchain, locate the correct Gitea thread, and paste manually. The existing authored outbox already durably and idempotently delivers `search-reply` comments, so the missing product slice is destination selection and admission from the summary review. Historical issue #1090 deliberately ended at native share/clipboard; no open issue, PR, release, or recent commit implements direct posting. ## User flow 1. Review exact worked/tomorrow items, optional actual time, and note. 2. Choose **Post to Gitea**, enter and validate an exact `owner/repo#number` issue or pull request destination, and review the exact destination beside the comment body. 3. Confirm once. The reviewed comment is durably admitted to the existing authored outbox with a stable operation ID before the private draft is cleared. 4. Report truthful queued/delivered state; admission failure preserves every choice for retry. Native sharing remains available. ## Acceptance tests - A canonical visible destination is required and normalized before confirmation. - Confirmation enqueues exactly one `search-reply` with repository, number, target kind, reviewed body, and stable operation ID. - The summary draft clears only after durable admission; rejected admission preserves it. - Account changes isolate the draft and pending destination. - The rendered 320px mobile sheet has no horizontal overflow, 44px controls, wrapped destination text, and reachable sticky actions. - Existing native share/clipboard behavior remains unchanged. - Focused tests, full suite, and packaged mobile release journey pass. ## Non-duplication All 559 closed issue records and current open issues were reviewed. #1090 covers only privacy-reviewed native sharing/clipboard. Existing preview-comment/outbox code is reusable infrastructure, not this Today-to-status-thread flow.
timmy was assigned by rockachopa 2026-08-19 12:21:32 +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#1130
No description provided.