tasks: tasks.md sync left behind by PR #3 merge #4
Reference in New Issue
Block a user
Delete Branch "tasks-md-phase5-sync"
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?
Small follow-up to PR #3. The PR was merged at
bc02fcb(the drain-test race fix); the tasks.md sync commit3748c2alanded on the branch a few minutes later and didn't make it in.Summary
LatestJobByKindincludes in-flight jobs,ForgetGroupsmulti-group payload,repo.statsenvelope, per-host drain mutex.No code change; tasks.md only.
Test plan
The Phase 5 section had drifted from the convention used by phases 1–4 (single section header carrying ✅, no separate summary block). Collapse to the existing pattern; fold the summary into a blockquote sitting right under the header. While there: P2R-03 and P2R-04 still carried forward-references saying "cadence-driven dispatch lands in P2R-04 / P2R-05". Both should point at P2R-06 (the maintenance ticker), not the next item in the list. Updated descriptions to reflect what actually shipped: LatestJobByKind anchor includes in-flight jobs, ForgetGroups multi-group payload reshape, repo.stats envelope shape, per-host drain mutex.