47ed26a01b
* fix(#3120): add register_authored_at_plan_time guard to secure-phase Root cause: Step 3 short-circuit used threats_open: 0 as the sole condition to skip directly to Step 6 (write clean SECURITY.md). It did not distinguish empty-by-all-mitigated from empty-by-no-planning. Legacy phases authored before <threat_model> blocks were canonical received a rubber-stamped clean SECURITY.md with no audit performed. Fix: Step 2c: track register_authored_at_plan_time (true iff >=1 PLAN file contained a parseable <threat_model> block) Step 3: two-condition short-circuit: - threats_open:0 AND register_authored_at_plan_time:true -> skip to Step 6 (legitimate, all mitigated) - threats_open:0 AND register_authored_at_plan_time:false -> retroactive-STRIDE mode in Step 5 (build register from implementation, then verify) Step 5: auditor constraint varies by mode: planned -> Verify mitigations exist, do not scan retroactive -> Build STRIDE register first, then verify Suite: 7039/7039. Closes #3120. * fix(lint+changeset): allow-test-rule, drop dead regex branches, fix pr field to 3142
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.