PhaseAdvance.maybeUpdateReviewState repeats the PhaseMergedCard shape instead of calling PhaseMergedCard.update #612

Closed
opened 2026-09-22 22:11:46 +00:00 by claude · 1 comment
Member

Found in IW-606 phase 1.

PhaseAdvance.maybeUpdateReviewState builds the phase-merged card by hand. It repeats the shape that PhaseMergedCard.update already owns. A change to the merged card (for example the owned-badge supersede from IW-606) must be made in two places, and nothing catches a miss.

PROPOSED FIX. Make PhaseAdvance call PhaseMergedCard.update. This also changes needs_attention and the CI-wait fields that phase-advance writes, so it needs its own change and its own tests.

Found in IW-606 phase 1. `PhaseAdvance.maybeUpdateReviewState` builds the phase-merged card by hand. It repeats the shape that `PhaseMergedCard.update` already owns. A change to the merged card (for example the owned-badge supersede from IW-606) must be made in two places, and nothing catches a miss. PROPOSED FIX. Make `PhaseAdvance` call `PhaseMergedCard.update`. This also changes `needs_attention` and the CI-wait fields that `phase-advance` writes, so it needs its own change and its own tests.
Author
Member

Intake: agent-ready
Workflow: waterfall
Reason: all gates passed
Analysis: project-management/issues/IW-612/analysis.md on branch IW-612

Intake: agent-ready Workflow: waterfall Reason: all gates passed Analysis: project-management/issues/IW-612/analysis.md on branch IW-612
mph closed this issue 2026-10-07 07:31:30 +00:00
Sign in to join this conversation.
No milestone
No project
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
iterative-works/iw-cli#612
No description provided.