Stop wiring the version.gradle.kts Edit-block hook

[alexander-yevsyukov]

What

Removes the Edit|Write|MultiEdit → protect-version-file.sh PreToolUse entry from the .claude/settings.json template. Because migrate clobber-copies this template into every consumer's .claude/settings.json on each ./config/pull, dropping the entry here removes the block from all consumers on their next pull — no per-repo edits needed.

The Bash publish gate (pre-pr-gate.sh, publish-version-gate.sh), the PostToolUse hooks (sanitize-source-code.sh, update-copyright.sh), and the SessionStart init-submodules hook are all left intact.

Why

The 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:

• publish-version-gate.sh still blocks a build/publish unless the branch is bumped above base.
• CI's checkVersionIncrement still rejects an already-published version.

Companion change

The shared agents repo deletes the now-unreferenced script: SpineEventEngine/agents#21.

Rollout

Merge this PR first: it removes the wiring everywhere on the next ./config/pull, and the script lingering unused in .agents/shared is harmless. Then merge the agents PR (deletes the script). Merging in the other order leaves a brief window where a consumer's settings reference a deleted script — a non-blocking stderr note on edits, not a real break.

[Copilot]

Pull request overview

This PR updates the config repository’s Claude settings template to stop invoking the version-file protection hook on edit/write operations, relying instead on the existing publish/version gates to enforce correct versioning outcomes across consumer repositories.

Changes:

• Removed the PreToolUse hook that ran protect-version-file.sh for Edit|Write|MultiEdit in .claude/settings.json.
• Kept the existing Bash pre-PR/publish gates and the PostToolUse sanitization/copyright hooks unchanged.

Comments suppressed due to low confidence (1)

.claude/settings.json:70

• The PR description calls protect-version-file.sh “now-unreferenced”, but this repo still wires it via .codex/hooks.json (PreToolUse apply_patch|Edit|Write). After the companion agents change deletes the script, Codex hook execution will reference a missing file (at least causing stderr / hook failure) even though .claude/settings.json no longer does. Consider removing the protect-version hook from .codex/hooks.json as part of this rollout (or explicitly scoping the PR description/rollout to Claude-only settings).

    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {