T-XU99-task-work-sync-relevance-edits-to-worktree
Status: closed/done · Impact: medium · Complexity: small
/sdlc:task-work Step 2’s relevance check often produces body edits on the task file
in main (e.g. fixing path drift in ## Today / ## Files to touch after an upstream
merge). There is no automated way to push those edits into the active worktree so
/sdlc:task-ensure-ready sees the same body before stamping readiness. Today’s manual
cp is error-prone and leaves the two checkouts drifting in lock-step with no guard.
Step 2’s relevance check (post-#69 path drift) had no mechanism to atomically bundle the body edits into the existing flow. Today the only path is: edit the file on main, manually cp to the worktree, ensure-ready commits on the worktree, start_task.py re-bundles on main, rebase. Gap: a Step 2.5 helper that says ‘your relevance edits are in main; sync them to the worktree and stage in both checkouts’ would remove the manual cp.
— from 2026-05-20-ontogen-ts-entity-field-type-closure in
git@github.com:sksizer/rust-ontogen.git.
TBD — receiver to fill before promoting from planning/draft.
Proposed
Section titled “Proposed”TBD — receiver to fill before promoting from planning/draft.
Approach
Section titled “Approach”TBD — receiver to fill before promoting from planning/draft.
Files to touch
Section titled “Files to touch”TBD — receiver to fill before promoting from planning/draft.
Acceptance criteria
Section titled “Acceptance criteria”TBD — receiver to fill before promoting from planning/draft.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”Spawned by /sdlc:cross-repo-task-pr on 2026-05-23 UTC from
2026-05-20-ontogen-ts-entity-field-type-closure in git@github.com:sksizer/rust-ontogen.git.