T-EYC2-reread-touched-files-against-branch-base

Status: closed/superseded · Impact: medium · Complexity: small

Goal

This task closes a /sdlc:task-work gap surfaced downstream in markdown-contract: the branch base can move between task pickup and the Step 5b reset, leaving files an implementer read at pickup stale against the actual base. Originating from T-SQFB-document-moon-runinci-dedicated-workflow in git@github.com:sksizer/markdown-contract.git.

In /sdlc:task-work the branch base can move between task pickup (the Step 2 relevance read) and the Step 5b reset to current origin/main — e.g. a touched file is flipped by parallel work merged onto main — so a file read at pickup goes stale and the implementer can edit against the wrong base; only a manual re-read caught it. A pre-implementation re-read of touched files against the actual post-reset branch base (not the pickup-time snapshot) would make this a non-event. Distinct from: T-61OI-check-ancestry-flags-stale-base (#284) which detects stale-base diff contamination at Step 9 push-time; T-XU99-task-work-sync-relevance-edits-to-worktree (#111) which syncs main-side relevance edits into the worktree; and T-R8JD-task-work-reresolve-moved-touchpoints (#602) which re-resolves moved touchpoint paths at pickup — this bullet asks for an implementation-time content re-read of the touched files against the reset base.

— from T-SQFB-document-moon-runinci-dedicated-workflow in git@github.com:sksizer/markdown-contract.git