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

Preserve Search-planned work details in offline Week Ahead #1220

New Issue
Closed
opened 2026-08-21 11:52:11 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-21 11:52:11 +00:00
Member
Copy Link

Problem

Planning an issue from Search persists its Week Ahead date and estimate, but not the canonical title/repository metadata used by the confirmed offline overview. A cold offline reopen therefore renders Work details unavailable for newly planned work even after the week save succeeded.

Evidence on origin/main (ba50784): search-week-plan.js and search-batch-plan.js place and flush canonical items, while week-plan.js only refreshes confirmed metadata when Week Ahead opens online. All 611 historical issue titles and recent commits were checked; #1194/#1196 add Search planning and #1218 adds offline metadata, but none connects these flows.

Acceptance

  • Single and batch Search planning stage bounded canonical work metadata with the account-bound pending week.
  • Pending metadata survives a cold reload and is promoted only after the matching week receipt succeeds.
  • Confirmed offline Week Ahead renders title, repository, kind, number, date, and estimate.
  • Failed batch assignments do not cache metadata.
  • Week API requests never contain metadata; arbitrary fields and oversized strings are excluded/bounded.
  • Metadata for unchanged planned work is retained and removed work is pruned.
  • Focused and full suites pass.

Implementation will use strict RED-GREEN TDD and close this issue from one deterministic branch/PR.

## Problem Planning an issue from Search persists its Week Ahead date and estimate, but not the canonical title/repository metadata used by the confirmed offline overview. A cold offline reopen therefore renders `Work details unavailable` for newly planned work even after the week save succeeded. Evidence on `origin/main` (`ba50784`): `search-week-plan.js` and `search-batch-plan.js` place and flush canonical items, while `week-plan.js` only refreshes confirmed metadata when Week Ahead opens online. All 611 historical issue titles and recent commits were checked; #1194/#1196 add Search planning and #1218 adds offline metadata, but none connects these flows. ## Acceptance - Single and batch Search planning stage bounded canonical work metadata with the account-bound pending week. - Pending metadata survives a cold reload and is promoted only after the matching week receipt succeeds. - Confirmed offline Week Ahead renders title, repository, kind, number, date, and estimate. - Failed batch assignments do not cache metadata. - Week API requests never contain metadata; arbitrary fields and oversized strings are excluded/bounded. - Metadata for unchanged planned work is retained and removed work is pruned. - Focused and full suites pass. Implementation will use strict RED-GREEN TDD and close this issue from one deterministic branch/PR.
timmy was assigned by rockachopa 2026-08-21 11:52:11 +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#1220
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?