b3730c979b
* test: gsd-intel-updater layout-detection block must be gated or removed (#3290 RED) Group A asserts the bare `ls -d .kilo ... || echo unknown` detection invocation is absent or wrapped in a framework-repo gate (fails RED: currently unconditional). Group B confirms zero downstream consumers of the verdict (passes GREEN: none exist). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(intel): gate layout-detection block on framework-repo check (#3290) The "Runtime layout detection" bash block in gsd-intel-updater ran unconditionally on every project analysed, emitting a noisy: Layout detection returned "unknown" — this project is not a GSD-system installation (no `.claude/get-shit-done/` or `.kilo/` runtime root). for every ordinary (non-GSD-framework) user project. Group B audit confirmed zero downstream consumers of the verdict outside the file itself. Fix (option A): wrap the detection bash block in a positive framework-repo gate — `jq -r '.name' package.json == "get-shit-done-cc"` — so it runs only when analysing the GSD framework's own repo. The layout table (.kilo/* paths) is retained for kilo-layout coverage (required by bug #2351 regression test). Dead-code vintage: byte-identical from v1.21.0 through v1.41.1 per reporter. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * changeset: pr=3299 for #3290 --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Changeset Fragments
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.
See #2975 for the full rationale.
Adding a fragment
node scripts/changeset/new.cjs \
--type Fixed \
--pr 1234 \
--body "fix the thing — explain the user-visible change in one sentence"
This writes .changeset/<adjective>-<noun>-<noun>.md with frontmatter and a body. Three random words → concurrent PRs don't collide.
Format
---
type: Fixed
pr: 1234
---
**`/gsd-foo` no longer drops trailing slashes** — explain the user-visible change.
Allowed type: values follow Keep a Changelog: Added, Changed, Deprecated, Removed, Fixed, Security.
Opting out
PRs that legitimately have no user-facing impact can add the no-changelog label. CI honors it. When unsure, add the fragment.
At release time
node scripts/changeset/cli.cjs render --version vX.Y.Z --date YYYY-MM-DD
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.