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

Require capacity confirmation when adding Week Ahead work to Today #1244

New Issue
Closed
opened 2026-08-22 01:24:58 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-22 01:24:58 +00:00
Member
Copy Link

Evidence

The newly shipped Week Ahead Add to Today flow checks the five-item limit but not Today’s configured minute capacity. frontend/week-plan.js submits immediately, while src/today_store.py::pull_week_item atomically appends even when the imported estimate pushes Today over capacity. The inverse Today-to-Week flow already requires explicit overload consent.

A review of all 624 historical issue titles, open PRs, releases, and recent commits found no existing issue for capacity-aware Week-to-Today pulls. #1242 shipped only the base atomic pull; #811 and #675 cover Search/Find Work admission, not Week Ahead.

User impact

Mobile operators can see the projected load before changing both plans, cancel safely, or explicitly accept an intentional overload. Concurrent/API callers cannot bypass consent.

Acceptance criteria

  • A pull that would exceed a configured Today capacity is rejected atomically unless allow_over_capacity=true.
  • A within-capacity pull remains one tap and preserves capacity/estimates.
  • Week Ahead mobile shows the projected minutes and asks for confirmation only when the pull would overload Today; cancel performs no request.
  • The confirmed request carries explicit overload consent and still uses the idempotent operation ID.
  • Backend, controller, focused mobile rendered checks, full suite, and release Actions pass.
## Evidence The newly shipped Week Ahead **Add to Today** flow checks the five-item limit but not Today’s configured minute capacity. `frontend/week-plan.js` submits immediately, while `src/today_store.py::pull_week_item` atomically appends even when the imported estimate pushes Today over capacity. The inverse Today-to-Week flow already requires explicit overload consent. A review of all 624 historical issue titles, open PRs, releases, and recent commits found no existing issue for capacity-aware Week-to-Today pulls. #1242 shipped only the base atomic pull; #811 and #675 cover Search/Find Work admission, not Week Ahead. ## User impact Mobile operators can see the projected load before changing both plans, cancel safely, or explicitly accept an intentional overload. Concurrent/API callers cannot bypass consent. ## Acceptance criteria - A pull that would exceed a configured Today capacity is rejected atomically unless `allow_over_capacity=true`. - A within-capacity pull remains one tap and preserves capacity/estimates. - Week Ahead mobile shows the projected minutes and asks for confirmation only when the pull would overload Today; cancel performs no request. - The confirmed request carries explicit overload consent and still uses the idempotent operation ID. - Backend, controller, focused mobile rendered checks, full suite, and release Actions pass.
timmy was assigned by rockachopa 2026-08-22 01:24:58 +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#1244
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?