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

Make Today readiness checks demand-driven and latency-bounded #441

New Issue
Closed
opened 2026-08-10 01:29:49 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 01:29:49 +00:00
Owner
Copy Link

User problem

Starting or advancing a Today session currently waits for sequential dependency checks across the whole queue even when the preferred item is ready. A normal five-item queue can issue up to fifteen upstream operations and multiply tail latency before opening the first task.

Scope

  • Inspect the preferred issue first and open it immediately when ready.
  • If it is blocked or unknown, inspect remaining issue candidates concurrently while preserving queue-order selection.
  • Preserve blocker, retry, override, cancellation, pull-request, and offline behavior.
  • Ship the updated module in a newly versioned offline application shell.

Acceptance tests

  • A ready preferred issue causes exactly one inspection.
  • A blocked preferred issue starts remaining checks concurrently and chooses the earliest ready item in queue order, independent of completion order.
  • Superseded checks cannot open stale work or display a stale gate.
  • Non-issue work opens without dependency I/O.
  • Focused and full test suites pass; CI and release workflow are green.
## User problem Starting or advancing a Today session currently waits for sequential dependency checks across the whole queue even when the preferred item is ready. A normal five-item queue can issue up to fifteen upstream operations and multiply tail latency before opening the first task. ## Scope - Inspect the preferred issue first and open it immediately when ready. - If it is blocked or unknown, inspect remaining issue candidates concurrently while preserving queue-order selection. - Preserve blocker, retry, override, cancellation, pull-request, and offline behavior. - Ship the updated module in a newly versioned offline application shell. ## Acceptance tests - A ready preferred issue causes exactly one inspection. - A blocked preferred issue starts remaining checks concurrently and chooses the earliest ready item in queue order, independent of completion order. - Superseded checks cannot open stale work or display a stale gate. - Non-issue work opens without dependency I/O. - Focused and full test suites pass; CI and release workflow are green.
timmy self-assigned this 2026-08-10 01:29:49 +00:00
timmy closed this issue 2026-08-10 01:35:46 +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#441
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?