diff --git a/.changes/context-budget/feat-guard-move-22d06d06.md b/.changes/context-budget/feat-guard-move-22d06d06.md deleted file mode 100644 index 3b5e0aede5..0000000000 --- a/.changes/context-budget/feat-guard-move-22d06d06.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -bump: major ---- - -### Removed - -- The settings-write ask hook and its `settings_write_ask_enabled` option leave context-budget for the guardrails plugin, which runs the same checkpoint. Without guardrails enabled, a file-editing tool writes a settings file with no prompt, `/context-budget:audit fix` included. Enable guardrails to keep the ask, and set `settings_write_ask_enabled` again there if you had changed it: the value set here does not carry over. -- `/context-budget:setup` no longer reports the toggle or prints a route to change it, and its `node` check names only the measurement engine. The setup evals that tested the toggle are removed, and the rest no longer name it. - -### Changed - -- `/context-budget:audit fix` names the guardrails checkpoint, when guardrails is enabled, as what makes a project settings edit prompt. diff --git a/.changes/guardrails/feat-guard-move-34c15d84.md b/.changes/guardrails/feat-guard-move-34c15d84.md deleted file mode 100644 index 97a2fc37dc..0000000000 --- a/.changes/guardrails/feat-guard-move-34c15d84.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -bump: minor ---- - -### Added - -- **`settings-write-ask`, from context-budget.** A PreToolUse checkpoint on Write, Edit and NotebookEdit that asks before a file-editing tool writes a settings file Claude Code reads. Its decisions are unchanged; the reason now opens with `guardrails:`. Option `settings_write_ask_enabled` (on by default). The README's "Settings-write ask" section carries its limits and the #3864 decision. -- **`connected-page-gate`, from review.** A PreToolUse guard on the Artifact tool that denies publishing an HTML page whose content security policy names a loopback `connect-src`. Its decisions are unchanged; the reason now opens with `guardrails:`. Option `connected_page_guard_enabled` (on by default). -- Anyone who had set either option under context-budget or review sets it again under guardrails: the old values do not carry over. diff --git a/.changes/plugin-profiles/feat-guard-move-180191d2.md b/.changes/plugin-profiles/feat-guard-move-180191d2.md deleted file mode 100644 index 50faf3af69..0000000000 --- a/.changes/plugin-profiles/feat-guard-move-180191d2.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -bump: patch ---- - -### Changed - -- The `always-on` profile no longer lists `context-budget`, whose settings-write ask now runs in guardrails; `context-budget` moves to `harness-upkeep`. diff --git a/.changes/prototype/feat-prototype-vendor-fit-5b8e21c4.md b/.changes/prototype/feat-prototype-vendor-fit-5b8e21c4.md deleted file mode 100644 index e1e1b24ab1..0000000000 --- a/.changes/prototype/feat-prototype-vendor-fit-5b8e21c4.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -bump: minor ---- - -### Added - -- `/prototype:pressure-test vendor-fit` checks whether an outside service does what the rules need. - The logic module stays pure; a thin adapter behind the app's own port is the only file that - calls the vendor's sandbox, with sandbox keys from the environment and synthetic records only, - never production credentials or regulated data. The terminal shell shows each check passing or - failing, and the durable note records the verdict. Eval case `pt-vendor-fit-no-sandbox-key`. - -### Changed - -- `/prototype:explore-directions` keeps every write stubbed by default. When the question names a - write's behavior, that write may go to the vendor's sandbox on the real stack, stated at the top - of the prototype, never against production or regulated data. Eval case - `ed-write-behavior-sandbox`. diff --git a/.changes/review/feat-guard-move-e45a71c5.md b/.changes/review/feat-guard-move-e45a71c5.md deleted file mode 100644 index eb4fb6cc43..0000000000 --- a/.changes/review/feat-guard-move-e45a71c5.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -bump: major ---- - -### Removed - -- The connected-page Artifact guard and its `connected_page_guard_enabled` option leave review for the guardrails plugin, which runs the same guard. Without guardrails enabled, nothing blocks publishing a connected page as an Artifact, which exposes the local session-bridge port. Enable guardrails to keep the guard, and set `connected_page_guard_enabled` again there if you had changed it: the value set here does not carry over. review now registers no hook. -- `scripts/check-hook-registration.sh` is removed with the hook it checked, and the node prerequisite's notice no longer names it. - -### Added - -- `/review:explain-change`'s `build-digest.mjs --connect` prints a warning on stderr, whether or not guardrails is enabled, that the page it wrote is local-only, works only on this machine and must never be published as an Artifact. Its stdout still prints only the page path. diff --git a/plugins/context-budget/.claude-plugin/plugin.json b/plugins/context-budget/.claude-plugin/plugin.json index 14a8674038..e5153e92bf 100644 --- a/plugins/context-budget/.claude-plugin/plugin.json +++ b/plugins/context-budget/.claude-plugin/plugin.json @@ -5,7 +5,7 @@ "name": "Melodic Software", "email": "info@melodicsoftware.com" }, - "version": "1.1.16", + "version": "2.0.0", "license": "MIT", "types": "./types/index.d.ts", "userConfig": { diff --git a/plugins/context-budget/CHANGELOG.md b/plugins/context-budget/CHANGELOG.md index 6ea38d8c02..8963ca6f21 100644 --- a/plugins/context-budget/CHANGELOG.md +++ b/plugins/context-budget/CHANGELOG.md @@ -7,6 +7,17 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Versions 0.6.38 and 0.6.40 were reserved by parallel changes and never published. +## [2.0.0] - 2026-11-16 + +### Changed + +- `/context-budget:audit fix` names the guardrails checkpoint, when guardrails is enabled, as what makes a project settings edit prompt. + +### Removed + +- The settings-write ask hook and its `settings_write_ask_enabled` option leave context-budget for the guardrails plugin, which runs the same checkpoint. Without guardrails enabled, a file-editing tool writes a settings file with no prompt, `/context-budget:audit fix` included. Enable guardrails to keep the ask, and set `settings_write_ask_enabled` again there if you had changed it: the value set here does not carry over. +- `/context-budget:setup` no longer reports the toggle or prints a route to change it, and its `node` check names only the measurement engine. The setup evals that tested the toggle are removed, and the rest no longer name it. + ## [1.1.16] - 2026-11-16 ### Changed diff --git a/plugins/guardrails/.claude-plugin/plugin.json b/plugins/guardrails/.claude-plugin/plugin.json index 4b311aff83..6e8e88c038 100644 --- a/plugins/guardrails/.claude-plugin/plugin.json +++ b/plugins/guardrails/.claude-plugin/plugin.json @@ -234,5 +234,5 @@ "default": "" } }, - "version": "3.5.1" + "version": "3.6.0" } diff --git a/plugins/guardrails/CHANGELOG.md b/plugins/guardrails/CHANGELOG.md index d635a483a9..176a8221a2 100644 --- a/plugins/guardrails/CHANGELOG.md +++ b/plugins/guardrails/CHANGELOG.md @@ -3,6 +3,14 @@ All notable changes to the `guardrails` plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning. +## [3.6.0] - 2026-11-16 + +### Added + +- **`settings-write-ask`, from context-budget.** A PreToolUse checkpoint on Write, Edit and NotebookEdit that asks before a file-editing tool writes a settings file Claude Code reads. Its decisions are unchanged; the reason now opens with `guardrails:`. Option `settings_write_ask_enabled` (on by default). The README's "Settings-write ask" section carries its limits and the #3864 decision. +- **`connected-page-gate`, from review.** A PreToolUse guard on the Artifact tool that denies publishing an HTML page whose content security policy names a loopback `connect-src`. Its decisions are unchanged; the reason now opens with `guardrails:`. Option `connected_page_guard_enabled` (on by default). +- Anyone who had set either option under context-budget or review sets it again under guardrails: the old values do not carry over. + ## [3.5.1] - 2026-11-16 ### Changed diff --git a/plugins/plugin-profiles/.claude-plugin/plugin.json b/plugins/plugin-profiles/.claude-plugin/plugin.json index 402549642e..e54a7f645f 100644 --- a/plugins/plugin-profiles/.claude-plugin/plugin.json +++ b/plugins/plugin-profiles/.claude-plugin/plugin.json @@ -5,7 +5,7 @@ "name": "Melodic Software", "email": "info@melodicsoftware.com" }, - "version": "0.2.1", + "version": "0.2.2", "license": "MIT", "types": "./types/index.d.ts", "keywords": [ diff --git a/plugins/plugin-profiles/CHANGELOG.md b/plugins/plugin-profiles/CHANGELOG.md index 6d3df4048c..a4f066fa04 100644 --- a/plugins/plugin-profiles/CHANGELOG.md +++ b/plugins/plugin-profiles/CHANGELOG.md @@ -3,6 +3,12 @@ All notable changes to the `plugin-profiles` plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning. +## [0.2.2] - 2026-11-16 + +### Changed + +- The `always-on` profile no longer lists `context-budget`, whose settings-write ask now runs in guardrails; `context-budget` moves to `harness-upkeep`. + ## [0.2.1] - 2026-11-16 ### Changed diff --git a/plugins/prototype/.claude-plugin/plugin.json b/plugins/prototype/.claude-plugin/plugin.json index a113eb488f..3303550b75 100644 --- a/plugins/prototype/.claude-plugin/plugin.json +++ b/plugins/prototype/.claude-plugin/plugin.json @@ -5,7 +5,7 @@ "name": "Melodic Software", "email": "info@melodicsoftware.com" }, - "version": "0.33.2", + "version": "0.34.0", "license": "MIT", "keywords": [ "prototype", diff --git a/plugins/prototype/CHANGELOG.md b/plugins/prototype/CHANGELOG.md index e455509121..37b2fd720b 100644 --- a/plugins/prototype/CHANGELOG.md +++ b/plugins/prototype/CHANGELOG.md @@ -3,6 +3,23 @@ All notable changes to the `prototype` plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning. +## [0.34.0] - 2026-11-16 + +### Added + +- `/prototype:pressure-test vendor-fit` checks whether an outside service does what the rules need. + The logic module stays pure; a thin adapter behind the app's own port is the only file that + calls the vendor's sandbox, with sandbox keys from the environment and synthetic records only, + never production credentials or regulated data. The terminal shell shows each check passing or + failing, and the durable note records the verdict. Eval case `pt-vendor-fit-no-sandbox-key`. + +### Changed + +- `/prototype:explore-directions` keeps every write stubbed by default. When the question names a + write's behavior, that write may go to the vendor's sandbox on the real stack, stated at the top + of the prototype, never against production or regulated data. Eval case + `ed-write-behavior-sandbox`. + ## [0.33.2] - 2026-11-16 ### Changed diff --git a/plugins/review/.claude-plugin/plugin.json b/plugins/review/.claude-plugin/plugin.json index b1da51b135..88f511febf 100644 --- a/plugins/review/.claude-plugin/plugin.json +++ b/plugins/review/.claude-plugin/plugin.json @@ -5,7 +5,7 @@ "name": "Melodic Software", "email": "info@melodicsoftware.com" }, - "version": "9.5.6", + "version": "10.0.0", "license": "MIT", "keywords": [ "review", diff --git a/plugins/review/CHANGELOG.md b/plugins/review/CHANGELOG.md index e2fb1b65f9..0bfe2c3c46 100644 --- a/plugins/review/CHANGELOG.md +++ b/plugins/review/CHANGELOG.md @@ -3,6 +3,17 @@ All notable changes to the `review` plugin are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning. +## [10.0.0] - 2026-11-16 + +### Added + +- `/review:explain-change`'s `build-digest.mjs --connect` prints a warning on stderr, whether or not guardrails is enabled, that the page it wrote is local-only, works only on this machine and must never be published as an Artifact. Its stdout still prints only the page path. + +### Removed + +- The connected-page Artifact guard and its `connected_page_guard_enabled` option leave review for the guardrails plugin, which runs the same guard. Without guardrails enabled, nothing blocks publishing a connected page as an Artifact, which exposes the local session-bridge port. Enable guardrails to keep the guard, and set `connected_page_guard_enabled` again there if you had changed it: the value set here does not carry over. review now registers no hook. +- `scripts/check-hook-registration.sh` is removed with the hook it checked, and the node prerequisite's notice no longer names it. + ## [9.5.6] - 2026-11-16 ### Changed