specflow-cc 1.23.0 → 1.23.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,12 @@ All notable changes to SpecFlow will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.23.1] - 2026-05-28
9
+
10
+ ### Fixed
11
+
12
+ - **spec-auditor could not emit its Recommendation line** (agent lacked the Bash tool, and both audit/review agents referenced a non-existent relative `bin/sf-tools.cjs` path). Granted Bash to spec-auditor and corrected both paths to the canonical `~/.claude/specflow-cc/bin/sf-tools.cjs`. Also prefixed the same latent bare-path bug in [`agents/spec-reviser.md`](agents/spec-reviser.md) (`todo next-id` / `todo reindex`) so no bare relative `bin/sf-tools.cjs` remains in any agent. Both audit/review Step 7.5 blocks now fall back to the deterministic action mapping if the shell-out fails.
13
+
8
14
  ## [1.23.0] - 2026-05-27
9
15
 
10
16
  ### Added
@@ -289,8 +289,9 @@ Using the Critical, Major, and Minor counts determined in Step 5:
289
289
 
290
290
  1. Shell out to obtain the recommendation:
291
291
  ```
292
- node bin/sf-tools.cjs recommend --source review --critical <N> --major <M> --minor <K>
292
+ node ~/.claude/specflow-cc/bin/sf-tools.cjs recommend --source review --critical <N> --major <M> --minor <K>
293
293
  ```
294
+ If the shell-out fails for any reason, derive the recommendation deterministically from the documented (critical/major/minor)→action mapping rather than omitting the line.
294
295
 
295
296
  2. Parse the JSON response: `{ "action": "...", "reason": "..." }`
296
297
 
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: sf-spec-auditor
3
3
  description: Audits specifications for quality, completeness, and clarity in a fresh context
4
- tools: Read, Write, Glob, Grep
4
+ tools: Read, Write, Glob, Grep, Bash
5
5
  ---
6
6
 
7
7
  <role>
@@ -776,9 +776,9 @@ Using the Critical count and Recommendations count determined in Step 5:
776
776
 
777
777
  1. Shell out to obtain the recommendation:
778
778
  ```
779
- node bin/sf-tools.cjs recommend --source audit --critical <N> --minor <M>
779
+ node ~/.claude/specflow-cc/bin/sf-tools.cjs recommend --source audit --critical <N> --minor <M>
780
780
  ```
781
- Note: The CLI flag is `--minor` even though the auditor uses the label "Recommendations" — this is intentional for parser symmetry across audit/review sources.
781
+ Note: The CLI flag is `--minor` even though the auditor uses the label "Recommendations" — this is intentional for parser symmetry across audit/review sources. If the shell-out fails for any reason, derive the recommendation deterministically from the documented (critical/minor)→action mapping rather than omitting the line.
782
782
 
783
783
  2. Parse the JSON response: `{ "action": "...", "reason": "..." }`
784
784
 
@@ -147,7 +147,7 @@ For each deferred item:
147
147
 
148
148
  1. Generate next TODO ID:
149
149
  ```bash
150
- node bin/sf-tools.cjs todo next-id --raw
150
+ node ~/.claude/specflow-cc/bin/sf-tools.cjs todo next-id --raw
151
151
  ```
152
152
  2. Create `.specflow/todos/TODO-{XXX}.md` using the Write tool:
153
153
  ```markdown
@@ -181,7 +181,7 @@ For each deferred item:
181
181
  4. After the loop completes (at least one TODO created), refresh the INDEX.md cache so it reflects the newly-created files:
182
182
 
183
183
  ```bash
184
- node bin/sf-tools.cjs todo reindex
184
+ node ~/.claude/specflow-cc/bin/sf-tools.cjs todo reindex
185
185
  ```
186
186
 
187
187
  **Important:** Both substeps are mandatory. Every deferred item MUST produce a TODO, and if any TODO is created the reindex helper MUST run before reporting completion. Skipping the reindex leaves `.specflow/todos/INDEX.md` missing the just-created entries, which the `/sf:status` freshness check will then flag. If TODO creation fails, report the failure — do not silently skip.
@@ -253,7 +253,7 @@ Tip: `/clear` recommended — auditor needs fresh context
253
253
  - [ ] Revision Response recorded in Audit History
254
254
  - [ ] Deferred items (if any) created as individual `.specflow/todos/TODO-XXX.md` files
255
255
  - [ ] TODOs Created subsection appended to Response (if deferred items exist)
256
- - [ ] INDEX.md refreshed via `node bin/sf-tools.cjs todo reindex` (if any TODO was created)
256
+ - [ ] INDEX.md refreshed via `node ~/.claude/specflow-cc/bin/sf-tools.cjs todo reindex` (if any TODO was created)
257
257
  - [ ] Frontmatter status updated
258
258
  - [ ] STATE.md updated
259
259
  - [ ] Clear summary of changes provided
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "specflow-cc",
3
- "version": "1.23.0",
3
+ "version": "1.23.1",
4
4
  "description": "Spec-driven development system for Claude Code — quality-first workflow with explicit audit cycles",
5
5
  "bin": {
6
6
  "specflow-cc": "bin/install.js"