From cecabd1cad996cd06ecca20e62031ea5852649da Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 17 Jun 2026 14:32:02 +0000 Subject: [PATCH] chore: version packages --- .changeset/p314-autocreate-rfc-scope-advisory.md | 9 --------- packages/retrospective/.claude-plugin/plugin.json | 2 +- packages/retrospective/CHANGELOG.md | 10 ++++++++++ packages/retrospective/package.json | 2 +- 4 files changed, 12 insertions(+), 11 deletions(-) delete mode 100644 .changeset/p314-autocreate-rfc-scope-advisory.md diff --git a/.changeset/p314-autocreate-rfc-scope-advisory.md b/.changeset/p314-autocreate-rfc-scope-advisory.md deleted file mode 100644 index ff8c36ec..00000000 --- a/.changeset/p314-autocreate-rfc-scope-advisory.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@windyroad/retrospective": minor ---- - -run-retro Step 2b: ADR-073 auto-create-RFC reassessment advisory - -The fix-time RFC-trace gate auto-creates skeleton RFCs when a fix is proposed on a Known Error that has no RFC. Until now the only record of those auto-create events was an ephemeral line in the work-problems iteration summary, so the question ADR-073 asks you to revisit — are auto-created RFCs systematically under-scoped? — had no durable signal behind it. - -A new advisory detector (`check-autocreate-rfc-scope.sh`, run via the `wr-retrospective-check-autocreate-rfc-scope` PATH shim) reads the auto-created skeleton RFCs left on disk and surfaces the ones whose traced problem's fix has already shipped while the RFC's scope was never filled in. run-retro Step 2b reports them in the retro summary's Pipeline Instability section. The detector is advisory only — it always exits 0 and never blocks a commit. A one-off finding is the normal living-RFC pattern; a recurring population across retros is the ADR-073 reassessment trigger. (P314, RFC-005 B9) diff --git a/packages/retrospective/.claude-plugin/plugin.json b/packages/retrospective/.claude-plugin/plugin.json index a338ae8e..37a4dc44 100644 --- a/packages/retrospective/.claude-plugin/plugin.json +++ b/packages/retrospective/.claude-plugin/plugin.json @@ -78,5 +78,5 @@ } }, "name": "wr-retrospective", - "version": "0.24.1" + "version": "0.25.0" } diff --git a/packages/retrospective/CHANGELOG.md b/packages/retrospective/CHANGELOG.md index eeb3207a..29612b02 100644 --- a/packages/retrospective/CHANGELOG.md +++ b/packages/retrospective/CHANGELOG.md @@ -1,5 +1,15 @@ # @windyroad/retrospective +## 0.25.0 + +### Minor Changes + +- 649b20f: run-retro Step 2b: ADR-073 auto-create-RFC reassessment advisory + + The fix-time RFC-trace gate auto-creates skeleton RFCs when a fix is proposed on a Known Error that has no RFC. Until now the only record of those auto-create events was an ephemeral line in the work-problems iteration summary, so the question ADR-073 asks you to revisit — are auto-created RFCs systematically under-scoped? — had no durable signal behind it. + + A new advisory detector (`check-autocreate-rfc-scope.sh`, run via the `wr-retrospective-check-autocreate-rfc-scope` PATH shim) reads the auto-created skeleton RFCs left on disk and surfaces the ones whose traced problem's fix has already shipped while the RFC's scope was never filled in. run-retro Step 2b reports them in the retro summary's Pipeline Instability section. The detector is advisory only — it always exits 0 and never blocks a commit. A one-off finding is the normal living-RFC pattern; a recurring population across retros is the ADR-073 reassessment trigger. (P314, RFC-005 B9) + ## 0.24.1 ### Patch Changes diff --git a/packages/retrospective/package.json b/packages/retrospective/package.json index 790c5067..4e943d9b 100644 --- a/packages/retrospective/package.json +++ b/packages/retrospective/package.json @@ -1,6 +1,6 @@ { "name": "@windyroad/retrospective", - "version": "0.24.1", + "version": "0.25.0", "description": "Session retrospectives that update briefings and create problem tickets", "bin": { "windyroad-retrospective": "./bin/install.mjs"