From 1a2a3996da5663099066d584329583a274475102 Mon Sep 17 00:00:00 2001 From: alexander-yevsyukov Date: Thu, 18 Jun 2026 20:06:03 +0100 Subject: [PATCH] Stop wiring the version.gradle.kts Edit-block hook MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `Edit|Write|MultiEdit -> protect-version-file.sh` PreToolUse hook blocked agents from editing `version.gradle.kts`, forcing all version changes through the `bump-version` skill. It was friction without protection: it blocked the Edit tool but left a Bash `sed` write open, so it never actually prevented editing — it just diverted agents onto a path that then needed a permission prompt, defeating the autonomy the skill exists to provide. The protections that matter are outcome-based and stay in place: the `Bash` gate (`publish-version-gate.sh`) still blocks a build/publish unless the branch is bumped above base, and CI's `checkVersionIncrement` still rejects an already-published version. Because `migrate` clobber-copies this template into every consumer's `.claude/settings.json`, dropping the entry here removes the block from all consumers on their next `./config/pull`. The companion change deletes `protect-version-file.sh` from the shared `agents` repo. Co-Authored-By: Claude Opus 4.8 --- .claude/settings.json | 9 --------- 1 file changed, 9 deletions(-) diff --git a/.claude/settings.json b/.claude/settings.json index 823c2b2f..08c47574 100644 --- a/.claude/settings.json +++ b/.claude/settings.json @@ -64,15 +64,6 @@ } ], "PreToolUse": [ - { - "matcher": "Edit|Write|MultiEdit", - "hooks": [ - { - "type": "command", - "command": "$CLAUDE_PROJECT_DIR/.agents/scripts/protect-version-file.sh" - } - ] - }, { "matcher": "Bash", "hooks": [