bmad-method 6.10.1-next.42 → 6.10.1-next.43

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.10.1-next.42",
+  "version": "6.10.1-next.43",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/bmm-skills/ship/bmad-build-auto/step-04-review.md

@@ -86,14 +86,11 @@ Write the following details to `{spec_file}` under `## Auto Run Result`:
 
 Set `{spec_file}` frontmatter `followup_review_recommended` from the computation above.
 
-If version control is unavailable, set `{spec_file}` frontmatter `final_revision: NO_VCS` and `status: done`, then proceed to HALT.
+If version control is unavailable, set `{spec_file}` frontmatter `status: done`, then proceed to HALT.
 
-If version control is available:
+If version control is available, write `status: done` into `{spec_file}` frontmatter, then:
 
-1. Commit any reviewed-diff files that remain uncommitted. Keep commits already created during this run. Verify every reviewed-diff file appears in the change set after `{baseline_revision}` and none remains uncommitted. Do not push.
-2. Obtain the current full canonical revision directly from version control and preserve it verbatim as `{final_revision}`.
-3. Write `{final_revision}` and `status: done` into `{spec_file}` frontmatter.
-4. If `{spec_file}` is tracked in that working copy, commit only `{spec_file}` as a spec-finalization commit. Keep `{final_revision}` unchanged. Otherwise leave the finalized spec in place; do not create a substitute artifact.
-5. Verify the version-controlled working copy is clean. Otherwise HALT with status `blocked` and blocking condition `finalization left repository dirty`.
+1. Commit any reviewed-diff files that remain uncommitted, including `{spec_file}` when it is tracked in that working copy. Keep commits already created during this run. Verify every reviewed-diff file appears in the change set after `{baseline_revision}` and none remains uncommitted. Do not push.
+2. Verify the version-controlled working copy is clean. Otherwise HALT with status `blocked` and blocking condition `finalization left repository dirty`.
 
 HALT with status `done`.

package/src/bmm-skills/ship/bmad-retrospective/references/evidence-gathering.md

@@ -17,7 +17,7 @@ Collect what the epic produced and note the source path or range of each:
 
 A stories-mode epic is a spec folder. Map it onto the checklist above: `SPEC.md` is the epic spec; `stories.yaml` in list order is the story list, each entry's artifact being the single `stories/<id>-*.md` it names; there is no sprint status; the previous retrospective, when resuming, is `{spec-folder}/RETROSPECTIVE.md`; session logs are unchanged.
 
-The diff range differs. Each story records its own baseline in its artifact frontmatter — `baseline_revision` from `bmad-build-auto`, `baseline_commit` from `bmad-build` — so there is no single epic-wide range. Take the range end from `final_revision` when the artifact carries one; otherwise it is the next story's baseline in list order, which is exact because `bmad-build` adds no commit of its own after the work. For the last story, when nothing records the end, say so rather than substituting `HEAD`. A baseline that is absent or is not a revision leaves that story with no commit or diff evidence — record that too. Group the stories sharing an identical range and run `git_evidence.py` once per distinct range, passing that group's ids as one comma-separated `--stories` value. No `^` is needed here: unlike the sprint-mode range above, the recorded baseline is already the pre-change commit. Ranges may overlap or diverge; count a shared commit or file change once in the aggregate views while keeping each story's range as its provenance.
+The diff range differs. Each story records its own baseline in its artifact frontmatter — `baseline_revision` (deprecated) or `baseline_commit` — so there is no single epic-wide range. The range end is the next story's baseline in list order, which is exact because neither skill adds a commit of its own after the work. For the last story, when nothing records the end, derive it from the history — usually `HEAD`, though not always — and mark it inferred rather than recorded. A baseline that is absent or is not a revision leaves that story with no commit or diff evidence — record that too. Group the stories sharing an identical range and run `git_evidence.py` once per distinct range, passing that group's ids as one comma-separated `--stories` value. No `^` is needed here: unlike the sprint-mode range above, the recorded baseline is already the pre-change commit. Ranges may overlap or diverge; count a shared commit or file change once in the aggregate views while keeping each story's range as its provenance.
 
 ## Missing evidence