* test(3727): add failing test for --fix flag dispatch in code-review workflow
Adds bug-3727-code-review-fix-flag-dispatch.test.cjs with:
- Pure-function tests on parseCodeReviewFlags() / resolveCodeReviewWorkflow()
from new code-review-flags.cjs typed IR module
- Structural docs-parity tests asserting dispatch_fix step exists in
code-review.md and that initialize step references code-review-flags.cjs
Structural tests FAIL today (RED): workflow has no dispatch_fix step and
no reference to code-review-flags.cjs in initialize. IR-level tests pass
because the lib module is introduced in this commit as the typed seam.
Fixes#3727
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(3727): wire --fix/--all/--auto flags through code-review workflow
The initialize step now parses --fix, --all, and --auto from argv (via the
code-review-flags parser seam added in the previous test commit) and the
workflow dispatches gsd-code-fixer when --fix is truthy and the review
returned findings. Fixes the regression introduced when PR #2947 closed
#2946 without actually shipping the workflow dispatch.
Fixes#3727
* chore(3727): update changeset to reference PR #3743
The fix commit landed with the linked-issue number as the pr: field
placeholder. Updating to the actual PR number now that the PR is open.
* fix(3727): register code-review-flags.cjs in INVENTORY.md and manifest
Add missing row for get-shit-done/bin/lib/code-review-flags.cjs to the CLI
Modules table in docs/INVENTORY.md (count 72→73) and regenerate
docs/INVENTORY-MANIFEST.json to fix three failing CI tests:
- cli-modules-doc-parity: every CLI module must have a row in INVENTORY.md
- inventory-counts: headline "CLI Modules (N shipped)" must match file count
- inventory-manifest-sync: INVENTORY-MANIFEST.json must match filesystem
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This directory holds per-PR CHANGELOG fragments. Every PR with user-facing changes drops one (or more) <random-name>.md files here describing its CHANGELOG entry. Fragments are consolidated into the top-level CHANGELOG.md at release time.
Why
Two PRs that both edit the ### Fixed block of CHANGELOG.md always conflict on merge — git can't pick a serialization order without human input. Two PRs that each add a fresh .changeset/<unique-name>.md never conflict because they don't share lines.
Reads every fragment, groups bullets by type:, replaces ## [Unreleased] with a new ## [vX.Y.Z] - YYYY-MM-DD block, opens a fresh ## [Unreleased] above, deletes consumed fragments. Idempotent.
86e067924f