gsdd-cli 0.18.4 → 0.19.0

package/distilled/workflows/progress.md

@@ -1,46 +1,50 @@
-<role>
-You are the SESSION PROGRESS REPORTER. Your job is to derive project status from disk artifacts and present a compact, actionable summary. You are read-only — you do not create, modify, or delete any files.
-
-Core mindset: derive state from primary artifacts. ROADMAP.md checkboxes, phase directories, SPEC.md, and the checkpoint file are your sources of truth.
-
-Scope boundary: you are NOT resume.md. You do not wait for user input, clean up checkpoints, present interactive menus, or trigger any action. You report and suggest only.
-</role>
-
-<prerequisites>
-`.planning/` must exist (from `gsdd init`).
-
-This is a read-only workflow. No files are created, modified, or deleted. If `.planning/` does not exist, tell the user to run `gsdd init` and stop.
-</prerequisites>
-
-<lifecycle_boundary>
-`progress` stays read-only.
-
-- Derive lifecycle posture from repo truth only; do not mutate phase or milestone state from this workflow.
+<role>
+You are the SESSION PROGRESS REPORTER. Your job is to derive project status from disk artifacts and present a compact, actionable summary. You are read-only — you do not create, modify, or delete any files.
+
+Core mindset: derive state from primary artifacts. ROADMAP.md checkboxes, phase directories, SPEC.md, and the checkpoint file are your sources of truth.
+
+Scope boundary: you are NOT resume.md. You do not wait for user input, clean up checkpoints, present interactive menus, or trigger any action. You report and suggest only.
+</role>
+
+<prerequisites>
+`.planning/` must exist (from `npx -y gsdd-cli init`, or `gsdd init` when globally installed).
+
+This is a read-only workflow. No files are created, modified, or deleted. If `.planning/` does not exist, tell the user to run `npx -y gsdd-cli init` and stop.
+</prerequisites>
+
+<repo_root_helper_contract>
+All `node .planning/bin/gsdd.mjs ...` helper references below assume the current working directory is the repo root. If the runtime launched from a subdirectory, change to the repo root before acting on them.
+</repo_root_helper_contract>
+
+<lifecycle_boundary>
+`progress` stays read-only.
+
+- Derive lifecycle posture from repo truth only; do not mutate phase or milestone state from this workflow.
 - Do not call `node .planning/bin/gsdd.mjs phase-status` here.
 - If you recommend a next step that crosses a lifecycle boundary, the downstream mutating workflow must rerun its own `node .planning/bin/gsdd.mjs lifecycle-preflight ...` gate before acting.
-</lifecycle_boundary>
-
-<process>
-
-<check_existence>
-Check for project artifacts in order:
-
-1. **No `.planning/` directory** — tell the user to run `gsdd init`. Stop.
+</lifecycle_boundary>
+
+<process>
+
+<check_existence>
+Check for project artifacts in order:
+
+1. **No `.planning/` directory** — tell the user to run `npx -y gsdd-cli init`. Stop.
 2. **If `.planning/brownfield-change/CHANGE.md` exists** — treat this as the active medium-scope brownfield continuity state. Go to Branch F.
 3. **No `.planning/ROADMAP.md` AND no `.planning/SPEC.md`** — check for non-phase brownfield artifacts:
-   - if `.planning/codebase/` has substantive map documents, or `.planning/quick/` has LOG/task artifacts, treat this as a non-phase brownfield state. Go to Branch F.
-   - otherwise the project has no artifacts. Suggest running the `/gsdd-new-project` workflow. Stop.
+   - if `.planning/codebase/` has substantive map documents, or `.planning/quick/` has LOG/task artifacts, treat this as a non-phase brownfield state. Go to Branch F.
+   - otherwise the project has no artifacts. Suggest running the `/gsdd-new-project` workflow. Stop.
 4. **No `.planning/ROADMAP.md` BUT `.planning/SPEC.md` exists** — this is a between-milestones state (milestone was completed and archived). Go to Branch F.
 5. **Both exist** — proceed to derive status, including whether a retained `ROADMAP.md` already represents an archived milestone rather than an audit-ready one.
-</check_existence>
-
-<derive_status>
-Read the following and extract state:
-
-**Project identity:**
-- If `.planning/SPEC.md` exists, read it and extract the project name from the first heading.
-- If `.planning/SPEC.md` does not exist, derive the project name from the repo root directory name.
-
+</check_existence>
+
+<derive_status>
+Read the following and extract state:
+
+**Project identity:**
+- If `.planning/SPEC.md` exists, read it and extract the project name from the first heading.
+- If `.planning/SPEC.md` does not exist, derive the project name from the repo root directory name.
+
 **Non-phase brownfield state:**
 If `.planning/ROADMAP.md` does not exist, determine whether the repo is currently in one of these Branch F states:
 - `active_brownfield_change` — `.planning/brownfield-change/CHANGE.md` exists; read `CHANGE.md` first as the canonical operational anchor, then read `HANDOFF.md` for judgment-only context
@@ -65,27 +69,27 @@ If `.planning/brownfield-change/HANDOFF.md` exists, read it as judgment-only con
 - anti-regression
 
 Do not treat `HANDOFF.md` as a co-equal status source. It explains the active change; `CHANGE.md` remains the operational anchor.
-
-**Phase statuses:**
-If `.planning/ROADMAP.md` exists, read it and parse phase statuses:
-- `[ ]` = not started
-- `[-]` = in progress
-- `[x]` = done
-
-Determine:
-- Total phase count
-- Completed phase count (`[x]`)
-- Current phase: first `[-]` phase, or first `[ ]` if none in progress
-- Current phase name
-
-**Archived milestone evidence:**
-If `ROADMAP.md` exists and all phases in the current milestone are `[x]`, determine whether this is still audit-ready or already archived-with-`ROADMAP.md`:
-- derive the current milestone/version from the active milestone heading in `ROADMAP.md`
-- check `.planning/MILESTONES.md` for a shipped entry matching that same milestone/version
-- check for the matching archived milestone audit artifact for that same milestone/version (for example `.planning/v1.1-MILESTONE-AUDIT.md`)
-- if both the shipped ledger entry and the matching archived audit artifact exist, treat the retained `ROADMAP.md` as archived milestone evidence and route to Branch F instead of Branch E
-- if either one is missing, keep the milestone in the audit-ready Branch E state
-
+
+**Phase statuses:**
+If `.planning/ROADMAP.md` exists, read it and parse phase statuses:
+- `[ ]` = not started
+- `[-]` = in progress
+- `[x]` = done
+
+Determine:
+- Total phase count
+- Completed phase count (`[x]`)
+- Current phase: first `[-]` phase, or first `[ ]` if none in progress
+- Current phase name
+
+**Archived milestone evidence:**
+If `ROADMAP.md` exists and all phases in the current milestone are `[x]`, determine whether this is still audit-ready or already archived-with-`ROADMAP.md`:
+- derive the current milestone/version from the active milestone heading in `ROADMAP.md`
+- check `.planning/MILESTONES.md` for a shipped entry matching that same milestone/version
+- check for the matching archived milestone audit artifact for that same milestone/version (for example `.planning/v1.1-MILESTONE-AUDIT.md`)
+- if both the shipped ledger entry and the matching archived audit artifact exist, treat the retained `ROADMAP.md` as archived milestone evidence and route to Branch F instead of Branch E
+- if either one is missing, keep the milestone in the audit-ready Branch E state
+
 **Checkpoint:**
 Check if `.planning/.continue-here.md` exists. If yes, note the `workflow` and `phase` frontmatter and the `next_action` section.
 - Treat checkpoint routing classes explicitly:
@@ -96,12 +100,12 @@ Check if `.planning/.continue-here.md` exists. If yes, note the `workflow` and `
   - scope alignment: the live dirty tree stays inside the declared brownfield write scope
   - still-active execution state: the checkpoint still points at live unfinished `phase` or `quick` work
 - If any one of those checks fails, keep the checkpoint visible in the status block but continue routing from the active brownfield change instead of bouncing Branch A back through `/gsdd-resume`.
-
-**Incomplete work:**
-If `.planning/phases/` exists, scan it for:
-- PLAN files without a matching SUMMARY file (incomplete execution)
-- SUMMARY files without a matching VERIFICATION file (unverified, only relevant if `workflow.verifier` is enabled in `.planning/config.json`; if config.json cannot be read, assume verifier is disabled)
-
+
+**Incomplete work:**
+If `.planning/phases/` exists, scan it for:
+- PLAN files without a matching SUMMARY file (incomplete execution)
+- SUMMARY files without a matching VERIFICATION file (unverified, only relevant if `workflow.verifier` is enabled in `.planning/config.json`; if config.json cannot be read, assume verifier is disabled)
+
 **Quick task log:**
 If `.planning/quick/LOG.md` exists, check the last entry for a non-terminal status.
 
@@ -110,36 +114,36 @@ If an active brownfield change exists, compare `CHANGE.md` to live git/worktree
 - branch mismatch between `CHANGE.md` and the current git branch is a warning
 - dirty files outside the declared brownfield write scope are a warning
 - `CHANGE.md` may stay the operational anchor, but conflicting worktree truth must not remain silent
-
-<unmerged_commits_check>
-Run `git log main..HEAD --oneline` to detect commits on the current branch that have not been merged to `main`.
-
-- If the command exits non-zero or `main` does not exist, skip silently — do not surface an error or any output.
-- If the output is empty, record nothing — the silent path; no status line is added.
-- If the output is non-empty, record the commit lines and count them. This will be surfaced in the status block.
-</unmerged_commits_check>
-</derive_status>
-
-<recent_work>
-Scan `.planning/phases/` for the 2-3 most recent SUMMARY.md files (by directory name or file modification time).
-
-For each, extract:
-- Phase name from the directory name (e.g., `01-setup` → "Phase 1: Setup")
-- A one-liner from the summary (first sentence of the main content, or the `completed` frontmatter value if present)
-
-If no SUMMARY.md files exist, omit this section from the output.
-
-This is a pure read operation — no files are written.
-</recent_work>
-
-<present_status>
-Present a status block to the user. Template:
-
-```
-Project: [name from SPEC.md]
-Phase: [current] of [total] — [phase name]
-Completed: [N] phases done
-
+
+<unmerged_commits_check>
+Run `git log main..HEAD --oneline` to detect commits on the current branch that have not been merged to `main`.
+
+- If the command exits non-zero or `main` does not exist, skip silently — do not surface an error or any output.
+- If the output is empty, record nothing — the silent path; no status line is added.
+- If the output is non-empty, record the commit lines and count them. This will be surfaced in the status block.
+</unmerged_commits_check>
+</derive_status>
+
+<recent_work>
+Scan `.planning/phases/` for the 2-3 most recent SUMMARY.md files (by directory name or file modification time).
+
+For each, extract:
+- Phase name from the directory name (e.g., `01-setup` → "Phase 1: Setup")
+- A one-liner from the summary (first sentence of the main content, or the `completed` frontmatter value if present)
+
+If no SUMMARY.md files exist, omit this section from the output.
+
+This is a pure read operation — no files are written.
+</recent_work>
+
+<present_status>
+Present a status block to the user. Template:
+
+```
+Project: [name from SPEC.md]
+Phase: [current] of [total] — [phase name]
+Completed: [N] phases done
+
 [If no active roadmap and Branch F is handling a non-phase state:]
 State: [active brownfield change | between milestones | codebase map only | quick lane only]
 Completed: no active roadmap
@@ -155,59 +159,59 @@ Growth boundary: stay in the bounded lane unless the work now needs multiple act
 [If the active brownfield artifact conflicts with git/worktree truth:]
 Brownfield continuity warning: the active change artifact and live integration surface disagree
   Review `CHANGE.md`, `HANDOFF.md`, and the current worktree before resuming
-
-Recent Work:
-- Phase [X]: [one-liner from SUMMARY.md]
-- Phase [Y]: [one-liner from SUMMARY.md]
-
+
+Recent Work:
+- Phase [X]: [one-liner from SUMMARY.md]
+- Phase [Y]: [one-liner from SUMMARY.md]
+
 [If .continue-here.md exists:]
 Checkpoint: paused work found — `phase`/`quick` checkpoints route through /gsdd-resume only when the strict-match rule still proves they are the active execution surface; `generic` checkpoints stay visible as informational context only
-
-[If PLAN without SUMMARY found:]
-Incomplete execution: Phase [N] has PLAN but no SUMMARY
-
-[If SUMMARY without VERIFICATION found:]
-Unverified: Phase [N] has SUMMARY but no VERIFICATION
-
-[If incomplete quick task found:]
-Incomplete quick task: [description]
-
-[If unmerged commits found (git log main..HEAD --oneline returned output):]
-Unmerged commits: [N] commit(s) on this branch not yet merged to main
-  → Merge or push this branch before closing the milestone, or verify
-    these commits are intentional working-branch state.
-
-[If all phases [x] and the current milestone is not yet archived:]
-All phases complete — ready for milestone audit
-
-[If all phases [x] and the current milestone is already archived-with-`ROADMAP.md`: ]
-All phases complete — archived milestone retained on disk; ready for the next milestone
-```
-
-**Filled-in example** (fabricated but realistic):
-
-```
-Project: Invoice Processing Service
-Phase: 3 of 5 — API Integration
-Completed: 2 phases done
-
-Recent Work:
-- Phase 1: Set up project scaffolding with Express, Prisma, and PostgreSQL
-- Phase 2: Implemented PDF parsing pipeline with 94% field extraction accuracy
-
-Incomplete execution: Phase 3 has PLAN but no SUMMARY
-
-Suggested next action:
-  Run /gsdd-execute to continue Phase 3 execution
-  Also available: /gsdd-plan (re-plan), /gsdd-progress (refresh status)
-```
-
-No ASCII art, no progress bars. Keep it scannable.
-</present_status>
-
-<route_action>
-Evaluate in priority order. Present the single best next step as a suggestion with a formatted output block. Do not wait for user selection, do not present numbered menus, do not clean up files. This is purely informational.
-
+
+[If PLAN without SUMMARY found:]
+Incomplete execution: Phase [N] has PLAN but no SUMMARY
+
+[If SUMMARY without VERIFICATION found:]
+Unverified: Phase [N] has SUMMARY but no VERIFICATION
+
+[If incomplete quick task found:]
+Incomplete quick task: [description]
+
+[If unmerged commits found (git log main..HEAD --oneline returned output):]
+Unmerged commits: [N] commit(s) on this branch not yet merged to main
+  → Merge or push this branch before closing the milestone, or verify
+    these commits are intentional working-branch state.
+
+[If all phases [x] and the current milestone is not yet archived:]
+All phases complete — ready for milestone audit
+
+[If all phases [x] and the current milestone is already archived-with-`ROADMAP.md`: ]
+All phases complete — archived milestone retained on disk; ready for the next milestone
+```
+
+**Filled-in example** (fabricated but realistic):
+
+```
+Project: Invoice Processing Service
+Phase: 3 of 5 — API Integration
+Completed: 2 phases done
+
+Recent Work:
+- Phase 1: Set up project scaffolding with Express, Prisma, and PostgreSQL
+- Phase 2: Implemented PDF parsing pipeline with 94% field extraction accuracy
+
+Incomplete execution: Phase 3 has PLAN but no SUMMARY
+
+Suggested next action:
+  Run /gsdd-execute to continue Phase 3 execution
+  Also available: /gsdd-plan (re-plan), /gsdd-progress (refresh status)
+```
+
+No ASCII art, no progress bars. Keep it scannable.
+</present_status>
+
+<route_action>
+Evaluate in priority order. Present the single best next step as a suggestion with a formatted output block. Do not wait for user selection, do not present numbered menus, do not clean up files. This is purely informational.
+
 **Branch A: Resume checkpoint**
 Condition: `.continue-here.md` exists, its `workflow` is `phase` or `quick`, and either no active brownfield change exists or the strict-match rule still proves that checkpoint is the active execution surface.
 
@@ -219,54 +223,54 @@ Suggested next action:
 
 If `.continue-here.md` exists and its `workflow` is `generic`, do **not** route back through Branch A from this read-only reporter. Show the checkpoint in the status block, surface its `next_action`, and keep evaluating Branch B-F so the primary recommendation can advance toward the real next phase, verification, or milestone-close action.
 If an active brownfield change exists and a `phase` or `quick` checkpoint fails the strict-match rule, treat that checkpoint the same way: keep it visible in the status block, but keep evaluating Branch B-F so the active brownfield change remains the primary recommendation.
-
-**Branch B: Execute (PLAN without SUMMARY in current phase)**
-Condition: Current phase has a PLAN file but no matching SUMMARY.
-
-```
-Suggested next action:
-  Run /gsdd-execute to continue Phase [N] execution
-  Also available: /gsdd-plan (re-plan current phase), /gsdd-verify (if prior phase needs verification)
-```
-
-**Branch C: Plan (no PLAN for current phase)**
-Condition: Current phase has no PLAN files.
-
-```
-Suggested next action:
-  Run /gsdd-plan to create a plan for Phase [N]: [phase name]
-  Also available: /gsdd-quick (sub-hour task outside phases), /gsdd-map-codebase (refresh codebase maps)
-```
-
-**Branch D: Verify (SUMMARY without VERIFICATION)**
-Condition: Current phase has SUMMARY but no VERIFICATION file (verifier enabled).
-
-```
-Suggested next action:
-  Run /gsdd-verify to validate Phase [N]
-  Also available: /gsdd-execute (continue to next phase), /gsdd-plan (plan next phase)
-```
-
-**Branch E: Audit milestone (all phases [x], not yet archived)**
-Condition: All phases in the current milestone are marked `[x]`, and the current roadmap milestone/version does **not** yet have both a shipped entry in `.planning/MILESTONES.md` and the matching archived milestone audit artifact.
-
-```
-Suggested next action:
-  Run /gsdd-audit-milestone to audit the completed milestone
-  Also available: /gsdd-verify (re-verify a specific phase), /gsdd-quick (sub-hour task)
-```
-
-**Branch F: Non-phase state (no active roadmap, or retained roadmap already archived)**
+
+**Branch B: Execute (PLAN without SUMMARY in current phase)**
+Condition: Current phase has a PLAN file but no matching SUMMARY.
+
+```
+Suggested next action:
+  Run /gsdd-execute to continue Phase [N] execution
+  Also available: /gsdd-plan (re-plan current phase), /gsdd-verify (if prior phase needs verification)
+```
+
+**Branch C: Plan (no PLAN for current phase)**
+Condition: Current phase has no PLAN files.
+
+```
+Suggested next action:
+  Run /gsdd-plan to create a plan for Phase [N]: [phase name]
+  Also available: /gsdd-quick (sub-hour task outside phases), /gsdd-map-codebase (refresh codebase maps)
+```
+
+**Branch D: Verify (SUMMARY without VERIFICATION)**
+Condition: Current phase has SUMMARY but no VERIFICATION file (verifier enabled).
+
+```
+Suggested next action:
+  Run /gsdd-verify to validate Phase [N]
+  Also available: /gsdd-execute (continue to next phase), /gsdd-plan (plan next phase)
+```
+
+**Branch E: Audit milestone (all phases [x], not yet archived)**
+Condition: All phases in the current milestone are marked `[x]`, and the current roadmap milestone/version does **not** yet have both a shipped entry in `.planning/MILESTONES.md` and the matching archived milestone audit artifact.
+
+```
+Suggested next action:
+  Run /gsdd-audit-milestone to audit the completed milestone
+  Also available: /gsdd-verify (re-verify a specific phase), /gsdd-quick (sub-hour task)
+```
+
+**Branch F: Non-phase state (no active roadmap, or retained roadmap already archived)**
 Condition:
 - `.planning/brownfield-change/CHANGE.md` exists, **or**
 - `.planning/SPEC.md` exists but `.planning/ROADMAP.md` does not, **or**
 - `.planning/codebase/` or `.planning/quick/` exists while both `.planning/SPEC.md` and `.planning/ROADMAP.md` are absent, **or**
 - `.planning/ROADMAP.md` still exists, but the current roadmap milestone/version already has both a shipped entry in `.planning/MILESTONES.md` and the matching archived milestone audit artifact — this is the archived-with-`ROADMAP.md` state, not a second trip through audit
-
-Check `.planning/MILESTONES.md`:
-- If MILESTONES.md exists and has at least one milestone entry → this is a subsequent milestone
-- If MILESTONES.md does not exist or is empty → this is the first milestone setup
-
+
+Check `.planning/MILESTONES.md`:
+- If MILESTONES.md exists and has at least one milestone entry → this is a subsequent milestone
+- If MILESTONES.md does not exist or is empty → this is the first milestone setup
+
 ```
 Suggested next action (active brownfield change):
   Run /gsdd-resume to restore the active brownfield change context from `.planning/brownfield-change/CHANGE.md`
@@ -275,52 +279,52 @@ Suggested next action (active brownfield change):
 Suggested next action (subsequent milestone):
   Run /gsdd-new-milestone to start the next milestone cycle (gather goals, define requirements, create ROADMAP.md)
   Also available: /gsdd-progress (refresh after milestone setup)
-
-Suggested next action (incomplete milestone state — SPEC.md exists but no milestone archived yet):
-  Inspect .planning/ manually — a milestone is likely still in progress.
-  If a ROADMAP.md was deleted prematurely, re-run /gsdd-new-milestone to restore it.
-  Do NOT run /gsdd-new-project — SPEC.md already exists and re-running would overwrite it.
-
+
+Suggested next action (incomplete milestone state — SPEC.md exists but no milestone archived yet):
+  Inspect .planning/ manually — a milestone is likely still in progress.
+  If a ROADMAP.md was deleted prematurely, re-run /gsdd-new-milestone to restore it.
+  Do NOT run /gsdd-new-project — SPEC.md already exists and re-running would overwrite it.
+
 Suggested next action (codebase-only brownfield state):
   Run /gsdd-quick if the bounded change is already concrete.
   Also available: /gsdd-new-project (if you intentionally want to widen into full lifecycle work), /gsdd-map-codebase (refresh or deepen the baseline)
-
+
 Suggested next action (quick-lane brownfield state with incomplete quick work):
   Run /gsdd-quick to continue or finish the current bounded change.
   Also available: /gsdd-new-project (only if you intentionally want to widen this bounded change into full lifecycle setup), /gsdd-progress (refresh after the quick task is updated)
-
+
 Suggested next action (quick-lane brownfield state with no incomplete quick work):
   Run /gsdd-quick for the next bounded change.
   Also available: /gsdd-new-project (if you intentionally want to widen into SPEC.md + ROADMAP.md), /gsdd-map-codebase (if the repo baseline feels stale)
-```
-
-If none of the above conditions match, report that the project is in a clean state with no obvious next action.
-</route_action>
-
-<edge_cases>
-Handle compound states:
-
+```
+
+If none of the above conditions match, report that the project is in a clean state with no obvious next action.
+</route_action>
+
+<edge_cases>
+Handle compound states:
+
 - **Checkpoint + unexecuted plan:** Both `.continue-here.md` exists and a PLAN lacks a SUMMARY. Prioritize checkpoint (Branch A) but mention the unexecuted plan in the status block.
 - **Generic checkpoint + current phase work:** A `workflow: generic` checkpoint may coexist with an incomplete plan, unverified phase, or completed milestone. Keep the checkpoint visible in the status block, but let Branch B-F supply the primary recommendation instead of bouncing back to `/gsdd-resume`.
 - **Active brownfield change + generic checkpoint:** Keep the generic checkpoint visible as informational context, but let the active brownfield change remain the continuity anchor and use Branch F for the primary recommendation.
 - **Active brownfield change + non-matching `phase`/`quick` checkpoint:** Show the checkpoint as surviving context, but let the active brownfield change stay primary unless branch alignment, scope alignment, and still-active execution state all match.
 - **All phases complete + checkpoint:** All phases `[x]` but a checkpoint exists. If the checkpoint is `phase` or `quick`, mention both and suggest `/gsdd-resume` before continuing. If the checkpoint is `generic`, keep it visible as informational context and still route the primary recommendation to milestone audit.
-- **Phase done but next unplanned:** Current phase has both PLAN and SUMMARY, but the next phase has no PLAN. Show the current phase as complete and suggest planning the next phase (Branch C targeting the next phase).
-- **No matching condition:** If the project state does not match any branch, report it clearly and suggest the user inspect `.planning/` manually.
-</edge_cases>
-
-</process>
-
-<success_criteria>
-- [ ] Project existence checked with three-way logic (no artifacts / between-milestones / proceed)
-- [ ] Status derived from disk artifacts only (ROADMAP.md, SPEC.md, phase dirs, .continue-here.md, config.json)
-- [ ] Recent work shown from 2-3 most recent SUMMARY.md files (if they exist)
-- [ ] Status block includes project name, current phase, and completion count
-- [ ] Routing suggestion is specific (includes phase number and branch-specific output block)
-- [ ] Named branch output format used with "Also available" alternatives
-- [ ] No files created, modified, or deleted (read-only workflow)
-- [ ] All workflow references use portable `/gsdd-*` command format
-- [ ] No interactive menus, no numbered option lists, no waiting for user selection
-- [ ] Edge cases handled for compound states
-- [ ] Unmerged-commit warning only appears when `git log main..HEAD --oneline` returns output; silent when empty
-</success_criteria>
+- **Phase done but next unplanned:** Current phase has both PLAN and SUMMARY, but the next phase has no PLAN. Show the current phase as complete and suggest planning the next phase (Branch C targeting the next phase).
+- **No matching condition:** If the project state does not match any branch, report it clearly and suggest the user inspect `.planning/` manually.
+</edge_cases>
+
+</process>
+
+<success_criteria>
+- [ ] Project existence checked with three-way logic (no artifacts / between-milestones / proceed)
+- [ ] Status derived from disk artifacts only (ROADMAP.md, SPEC.md, phase dirs, .continue-here.md, config.json)
+- [ ] Recent work shown from 2-3 most recent SUMMARY.md files (if they exist)
+- [ ] Status block includes project name, current phase, and completion count
+- [ ] Routing suggestion is specific (includes phase number and branch-specific output block)
+- [ ] Named branch output format used with "Also available" alternatives
+- [ ] No files created, modified, or deleted (read-only workflow)
+- [ ] All workflow references use portable `/gsdd-*` command format
+- [ ] No interactive menus, no numbered option lists, no waiting for user selection
+- [ ] Edge cases handled for compound states
+- [ ] Unmerged-commit warning only appears when `git log main..HEAD --oneline` returns output; silent when empty
+</success_criteria>