Close the update nudge gap #4

Merged
Cody Bryant merged 1 commit from docs/close-the-update-nudge-variance into main 2026-08-23 16:34:43 -07:00
Owner

The last entry in "Still open, and NOT justified" is closed: both projects pick the release endpoint by channel and keep one marker per channel.

Records why the two halves have to land together - the marker leak only becomes possible once the candidate endpoint exists - and the trap the port laid, where four tests spelled a channel-derived marker literally and would have failed the next rc cut.

The last entry in "Still open, and NOT justified" is closed: both projects pick the release endpoint by channel and keep one marker per channel. Records why the two halves have to land together - the marker leak only becomes possible once the candidate endpoint exists - and the trap the port laid, where four tests spelled a channel-derived marker literally and would have failed the next rc cut.
docs(variance): close the update nudge gap (both projects now pick the endpoint by channel and keep one marker per channel)
All checks were successful
CI / Shell scripts (pull_request) Successful in 3s
CI / The standard can actually be vendored (pull_request) Successful in 17s
CI / Lint and test the standard's own code (pull_request) Successful in 24s
ab2273b234
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
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
SisyphusMD/project-standard!4
No description provided.