* test(#3581): pin init.progress's frontier to roadmap order over stray artifacts Failing-first regression for #3581: a stray out-of-order phase directory (a phase-9 UAT evidence file while roadmap phase 8 was pending and unscaffolded) made init.progress report next_phase 09, skipping Phase 8 and disagreeing with roadmap.analyze. Rows pin the issue shape, the aligned-tree control, and the all-complete boundary. * fix(#3581): derive init.progress's next_phase from roadmap order, not artifact presence The frontier is re-derived from the sorted phase union after the disk and roadmap loops: the first not-yet-begun, not-roadmap-complete phase wins. Artifacts still feed status and completion per entry, but a stray out-of-order directory can no longer drag the frontier past a pending unscaffolded roadmap phase, and init.progress agrees with roadmap.analyze. * fix(#3581): frontier = first not-complete phase in roadmap order (resume semantics) Review-of-own-control refinement: a begun-but-unfinished phase (in_progress, executed, researched) is the frontier — the next thing to execute is to resume it — so the frontier predicate is simply 'not complete and not roadmap-complete', first in the sorted union. * fix(#3581): preserve the pinned pending-only frontier contract; repair the boundary fixture Review findings: the resume-semantics refinement broke the suite-pinned contract that an in-progress phase is currentPhase's lane, not nextPhase's (tests/init.test.cjs 'multiple phases with mixed statuses') — reverted to first pending-or-not_started; the control row now pins the pure ordering property (roadmap-only pending beats a later pending directory); the boundary fixture gains passing verification reports so disk status reaches complete under the #3168 disk-strict bar. * chore(#3581): add changeset fragment * chore(#3581): backfill changeset pr number --------- Co-authored-by: sim <sim@local>
This commit is contained in:
5
.changeset/sturdy-foxes-gather.md
Normal file
5
.changeset/sturdy-foxes-gather.md
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
type: Fixed
|
||||
pr: 3603
|
||||
---
|
||||
**`init.progress` no longer infers the next phase from stray out-of-order artifacts** — a phase directory created out of order (e.g. a phase-9 UAT evidence file while roadmap phase 8 was still pending and unscaffolded) dragged the reported frontier forward, making `init.progress` skip Phase 8 and disagree with `roadmap.analyze`; the frontier is now derived from roadmap order, with artifacts as corroborating evidence only. (#3581)
|
||||
19
src/init.cts
19
src/init.cts
@@ -3069,6 +3069,25 @@ function cmdInitProgress(cwd: string, raw: boolean, options: Record<string, unkn
|
||||
(a, b) => parseInt(a['number'] as string, 10) - parseInt(b['number'] as string, 10),
|
||||
);
|
||||
|
||||
// #3581: the frontier is ROADMAP ORDER, not artifact presence. The disk loop
|
||||
// above could claim nextPhase from a stray out-of-order artifact directory
|
||||
// (a phase-9 UAT evidence dir while roadmap phase 8 was pending and
|
||||
// unscaffolded), silently skipping 8 — and init.progress then disagreed with
|
||||
// roadmap.analyze on the same tree. Re-derive from the sorted union: the
|
||||
// first phase that has not begun ('pending' | 'not_started') and is not
|
||||
// roadmap-complete wins; artifacts still feed each entry's status and
|
||||
// completion (corroborating evidence) but no longer outrank the ordering.
|
||||
// Aligned trees derive the identical frontier as the loops above; an
|
||||
// all-complete milestone finds none and keeps nextPhase null for the
|
||||
// completion flow.
|
||||
{
|
||||
const frontier = phases.find((p) => {
|
||||
const st = p['status'];
|
||||
return (st === 'pending' || st === 'not_started') && p['roadmap_complete'] !== true;
|
||||
});
|
||||
if (frontier) nextPhase = frontier;
|
||||
}
|
||||
|
||||
let pausedAt: string | null = null;
|
||||
const state = platformReadSync(path.join(planningDir(cwd), 'STATE.md'));
|
||||
if (state !== null) {
|
||||
|
||||
@@ -4480,3 +4480,75 @@ describe('#3171: init execute-phase emits the display name, not the directory sl
|
||||
);
|
||||
});
|
||||
});
|
||||
|
||||
// ─── #3581: init.progress frontier prefers roadmap order over stray artifacts ──
|
||||
describe('#3581: init.progress next_phase prefers the roadmap frontier', () => {
|
||||
function writeProgressFixture(t, { strayNine, completeAll }) {
|
||||
fs.writeFileSync(path.join(tmpDirOf(t), '.planning', 'ROADMAP.md'),
|
||||
['# Roadmap', '', '## Milestone v1.1.0', '', '### Phase 8: Payments', '**Goal:** g', '', '### Phase 9: Compatibility', '**Goal:** g', ''].join('\n'));
|
||||
fs.writeFileSync(path.join(tmpDirOf(t), '.planning', 'STATE.md'), [
|
||||
'---', 'gsd_state_version: 1.0', 'milestone: v1.1.0', 'milestone_name: Active',
|
||||
'status: executing', 'current_phase: 8', 'progress:', ' total_phases: 9',
|
||||
' completed_phases: 7', ' percent: 78', '---', '', '# Project State', '',
|
||||
'## Current Position', '', 'Phase: 8', 'Status: Executing',
|
||||
].join('\n'));
|
||||
if (strayNine) {
|
||||
const nine = path.join(tmpDirOf(t), '.planning', 'phases', '09-live-compatibility-diagnostics');
|
||||
fs.mkdirSync(nine, { recursive: true });
|
||||
fs.writeFileSync(path.join(nine, 'UAT.md'), '# UAT evidence\n');
|
||||
}
|
||||
if (completeAll) {
|
||||
// both phases complete on disk (plans, summaries, PASSING verification —
|
||||
// the #3168 disk-strict bar) + roadmap checkboxes
|
||||
for (const dir of ['08-payments', '09-compatibility']) {
|
||||
const d = path.join(tmpDirOf(t), '.planning', 'phases', dir);
|
||||
fs.mkdirSync(d, { recursive: true });
|
||||
fs.writeFileSync(path.join(d, 'PLAN.md'), '# p\n');
|
||||
fs.writeFileSync(path.join(d, 'SUMMARY.md'), '# s\n');
|
||||
fs.writeFileSync(path.join(d, `${dir.split('-')[0]}-VERIFICATION.md`), '---\nstatus: passed\n---\n\n# V\n');
|
||||
}
|
||||
}
|
||||
}
|
||||
// local alias so the helper reads the same as the suite's own fixtures
|
||||
function tmpDirOf(t) { return t.tmpDir3581 ?? (t.tmpDir3581 = createTempProject('gsd-3581-')); }
|
||||
|
||||
test('#3581: init.progress prefers the roadmap frontier over a stray out-of-order artifact', (t) => {
|
||||
writeProgressFixture(t, { strayNine: true });
|
||||
t.after(() => cleanup(tmpDirOf(t)));
|
||||
const result = runGsdTools(['init', 'progress', '--raw'], tmpDirOf(t));
|
||||
assert.ok(result.success, `init progress failed: ${result.error}`);
|
||||
const out = JSON.parse(result.output);
|
||||
assert.ok(out.next_phase, `next_phase present; got keys ${Object.keys(out)}`);
|
||||
assert.equal(String(out.next_phase.number).replace(/^0+/, ''), '8',
|
||||
`the roadmap's Phase 8 (pending, unscaffolded) must be the frontier — not the stray 09 artifact dir; got ${out.next_phase.number}`);
|
||||
const eight = (out.phases || []).find((p) => String(p.number).replace(/^0+/, '') === '8');
|
||||
assert.ok(eight, 'Phase 8 present in the phases array (roadmap-derived)');
|
||||
assert.equal(eight.directory, null, 'Phase 8 has no directory (corroborating the stray-only-disk shape)');
|
||||
});
|
||||
|
||||
test('#3581 (control): a pending roadmap-only phase outranks a later pending directory', (t) => {
|
||||
writeProgressFixture(t, { strayNine: false });
|
||||
// pure ordering property, no stray artifacts: roadmap-only pending 8 vs a
|
||||
// pending 9 DIRECTORY (empty). The pinned mixed-statuses contract (an
|
||||
// in-progress phase is currentPhase's lane, not nextPhase's) is untouched.
|
||||
const nine = path.join(tmpDirOf(t), '.planning', 'phases', '09-compatibility');
|
||||
fs.mkdirSync(nine, { recursive: true });
|
||||
t.after(() => cleanup(tmpDirOf(t)));
|
||||
const result = runGsdTools(['init', 'progress', '--raw'], tmpDirOf(t));
|
||||
assert.ok(result.success, `init progress failed: ${result.error}`);
|
||||
const out = JSON.parse(result.output);
|
||||
assert.equal(String(out.next_phase.number).replace(/^0+/, ''), '8',
|
||||
'the unscaffolded roadmap Phase 8 is the frontier even against a legitimately-pending 9 directory');
|
||||
});
|
||||
|
||||
test('#3581 (boundary): completed milestone yields no frontier', (t) => {
|
||||
writeProgressFixture(t, { strayNine: false, completeAll: true });
|
||||
fs.writeFileSync(path.join(tmpDirOf(t), '.planning', 'ROADMAP.md'),
|
||||
['# Roadmap', '', '## Milestone v1.1.0', '', '- [x] **Phase 8: Payments**', '- [x] **Phase 9: Compatibility**', ''].join('\n'));
|
||||
t.after(() => cleanup(tmpDirOf(t)));
|
||||
const result = runGsdTools(['init', 'progress', '--raw'], tmpDirOf(t));
|
||||
assert.ok(result.success, `init progress failed: ${result.error}`);
|
||||
const out = JSON.parse(result.output);
|
||||
assert.equal(out.next_phase, null, 'all-complete milestone: no frontier (completion flow owns the answer)');
|
||||
});
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user