cmdInitProgress used planningDir(cwd), which resolves to root .planning when no active workstream and no --ws/GSD_WORKSTREAM is set — regardless of mode:workstream. So /gsd-progress confidently reported a stale root milestone with no signal it was stale. Fail safe: when .planning/workstreams/ has workstreams AND no active workstream is resolved, error with an actionable hint naming the available workstreams and the --ws / `workstream set` fix. Flat mode (no workstreams dir) and --ws <name> are unchanged. Regression in tests/init.test.cjs: errors when workstreams exist but none active (no stale root report); succeeds with --ws; flat mode unchanged. Closes #1912
502 B
502 B
type, pr
| type | pr |
|---|---|
| Fixed | 1918 |
/gsd-progress no longer reports a stale root milestone in workstream mode — in a multi-workstream project with no active workstream set, gsd-tools query init.progress silently fell back to root .planning/STATE.md (often stale) and reported it confidently. It now fails safe with an actionable error naming the available workstreams and the --ws/workstream set fix, so a stale root value is never reported. Flat mode and --ws <name> are unchanged. (#1912)