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

Update repeated Week Ahead calendar exports without duplicate blocks #1214

New Issue
Closed
opened 2026-08-21 07:24:25 +00:00 by timmy · 0 comments
timmy commented 2026-08-21 07:24:25 +00:00
Owner
Copy Link

Problem

Repeated Week Ahead calendar exports generate a different event UID whenever the plan revision or scheduled day changes. Calendar clients therefore add duplicate task blocks instead of updating the operator’s existing blocks after a replan.

Product slice

Give each exported work item a stable calendar identity across revisions and moves, while incrementing iCalendar SEQUENCE so clients can apply the newer schedule. Keep separate issues and pull requests distinct even when their numeric IDs overlap.

Acceptance tests

  • Exporting the same work item at different plan revisions and dates emits the same UID.
  • A later plan revision emits a larger SEQUENCE.
  • Issue and pull-request work with overlapping repository/number values emit different UIDs.
  • Existing timed, timezone-aware, opaque event behavior remains intact.
  • Focused tests and the full suite pass.

Evidence / non-duplicate check

frontend/week-calendar.js currently includes both revision and day in UID:week-${revision}-${day}-${stableId(block.id)}@stackchain. All 608 historical issue titles/bodies and recent origin/main commit subjects were searched for stable UID, repeated export, update-existing, and calendar duplication behavior; no matching shipped or open slice was found.

## Problem Repeated Week Ahead calendar exports generate a different event UID whenever the plan revision or scheduled day changes. Calendar clients therefore add duplicate task blocks instead of updating the operator’s existing blocks after a replan. ## Product slice Give each exported work item a stable calendar identity across revisions and moves, while incrementing iCalendar `SEQUENCE` so clients can apply the newer schedule. Keep separate issues and pull requests distinct even when their numeric IDs overlap. ## Acceptance tests - Exporting the same work item at different plan revisions and dates emits the same `UID`. - A later plan revision emits a larger `SEQUENCE`. - Issue and pull-request work with overlapping repository/number values emit different UIDs. - Existing timed, timezone-aware, opaque event behavior remains intact. - Focused tests and the full suite pass. ## Evidence / non-duplicate check `frontend/week-calendar.js` currently includes both revision and day in `UID:week-${revision}-${day}-${stableId(block.id)}@stackchain`. All 608 historical issue titles/bodies and recent origin/main commit subjects were searched for stable UID, repeated export, update-existing, and calendar duplication behavior; no matching shipped or open slice was found.
timmy self-assigned this 2026-08-21 07:24:25 +00:00
timmy closed this issue 2026-08-21 07:39:05 +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#1214
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?