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

Require explicit authorization for queued issue closures #484

Merged
timmy merged 1 commits from timmy/483-authorize-queued-closures into main 2026-08-10 12:31:00 +00:00
Conversation 0 Commits 1 Files Changed 16 +165 -67
timmy commented 2026-08-10 12:29:27 +00:00
Owner
Copy Link

Closes #483

What changed

  • excludes queued issue closures from automatic foreground and service-worker drains
  • classifies closure intent as awaiting authorization in Delivery Center
  • adds a touch-safe Authorize & close action using the existing target-bound step-up flow
  • preserves the queued intent unless closure is confirmed
  • rolls the offline shell so installed mobile clients receive the corrected delivery contract

Verification

  • RED: automatic foreground flush delivered the closure; closed-app sync also attempted it; Delivery Center called it an ordinary queued delivery
  • GREEN: focused suite: 109 passed
  • full suite: 964 passed
  • Node syntax checks passed for all changed frontend runtime files
Closes #483 ## What changed - excludes queued issue closures from automatic foreground and service-worker drains - classifies closure intent as awaiting authorization in Delivery Center - adds a touch-safe **Authorize & close** action using the existing target-bound step-up flow - preserves the queued intent unless closure is confirmed - rolls the offline shell so installed mobile clients receive the corrected delivery contract ## Verification - RED: automatic foreground flush delivered the closure; closed-app sync also attempted it; Delivery Center called it an ordinary queued delivery - GREEN: focused suite: 109 passed - full suite: 964 passed - Node syntax checks passed for all changed frontend runtime files
timmy added 1 commit 2026-08-10 12:29:28 +00:00
fix: authorize queued issue closures explicitly (Closes #483)
All checks were successful
CI / lint (pull_request) Successful in 1m1s
Details
CI / build-release (pull_request) Successful in 5s
Details
CI / release-candidate (pull_request) Has been skipped
Details
62a0841eb5
timmy merged commit 131848cc43 into main 2026-08-10 12:31:00 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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#484
No description provided.
Delete Branch "timmy/483-authorize-queued-closures"

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?