CHANGELOG promotion was a manual operator step that was never run, so 463 fragments for work already shipped in <=1.3.1 accumulated in .changeset/. Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1] CHANGELOG sections (#690 backfill, PR #694). Rendering them now would duplicate and mis-attribute shipped work. Move them to .changeset/archived/ (read non-recursively by all changeset tooling, so never rendered), keeping only the 3 genuinely-unreleased fragments at the top level. Prep for wiring `render` into the release finalize job (#690 follow-up). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
6 lines
668 B
Markdown
6 lines
668 B
Markdown
---
|
|
type: Added
|
|
pr: 3424
|
|
---
|
|
**Adds optional fallow structural pre-pass support for `/gsd-code-review` via `code_quality.fallow.*` config keys** — when enabled, the workflow resolves a fallow binary (`PATH` then `node_modules/.bin`), writes `.planning/phases/<phase>/FALLOW.json`, and passes a dedicated `<structural_findings>` block into `gsd-code-reviewer` so `REVIEW.md` can separate `Structural Findings (fallow)` from narrative reviewer findings. This ships a new CLI module (`fallow-runner.cjs`) plus SDK twin normalization logic (`sdk/src/query/fallow-audit.ts`), updates config schema/docs, and keeps default behavior unchanged when fallow remains disabled.
|