Tom Boucher 00b7e622e1 test(#4457): cover init.new-milestone's project_exists/project_path under an active workstream (#4547) ...

#4457 reports init.progress and init.new-milestone reporting project_exists:false
(and a workstream-scoped project_path) for a root-shared PROJECT.md after a normal
migration. Direct read of current src/init.cts shows this is already fixed on next
by PR #4543 (#4455's self-discovered follow-up): withProjectRoot,
buildInitCompletenessFields, cmdInitProgress's project_exists, and
cmdInitNewMilestone's project_exists/project_path all already resolve PROJECT.md via
the root-aware planningDir(cwd, null).

PR #4543 added parametrized regression coverage for ingest-docs/resume/progress/
new-project (plus a dedicated milestone-op test), but its own comment explicitly
deferred new-milestone's coverage to "#4456's own new-milestone.md
workstream-forwarding work" (PR #4543). PR #4545 (#4456) never added it -- its test
additions only exercised the *workflow's* --ws argv forwarding through a stubbed
gsd_run, never cmdInitNewMilestone's real output. That gap is exactly what #4457's
own acceptance ask requests ("Add a migration-to-init regression test with a root
PROJECT.md and no workstream-local copy").

Folds 'new-milestone' into the existing SUBCOMMANDS loop in
tests/init-manager.test.cjs (it has no manager-style readiness precondition, and
exposes both project_exists and project_path, so it fits the loop's existing
assertion shape without a dedicated test). No production code change.

Co-authored-by: sim <sim@local>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-08 10:19:16 -04:00

65 KiB

Raw Blame History

View Raw