From fb526d8d7f6ef7c4c1a2fb61bde6302f4896f57b Mon Sep 17 00:00:00 2001 From: KSEGIT Date: Tue, 4 Aug 2026 00:18:26 +0100 Subject: [PATCH] fix: clarify userConfig option copy shown at install MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The two options presented during `/plugin install` described internals rather than behavior, and neither stated its default. - `disable`: retitled to name it as a kill switch. The old title said "Disable blocking", but the flag no-ops every hook — including the SessionStart prereq check and PostToolUse auto-record, not just the PreToolUse block. Now leads with the default and notes that a VS_DISABLE shell variable overrides the setting in both directions. - `window_hours`: says what actually happens when the window lapses (the dependency blocks again until re-verified) and gives the trade-off for tuning it up or down. Now leads with the default and spells out the 1-168h bounds. Copy only — no schema, key, default, or bound changed. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_0118eLJLbPbqYXiPc8R9AAiJ --- .claude-plugin/plugin.json | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 48ad895..5b08fd6 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -27,14 +27,14 @@ "userConfig": { "disable": { "type": "boolean", - "title": "Disable blocking", - "description": "If true, all version-sentinel hooks no-op (PreToolUse block, SessionStart prereq warning, PostToolUse auto-record). Equivalent to VS_DISABLE=1.", + "title": "Turn off Version Sentinel (kill switch)", + "description": "Default: false — the guardrail is active. Set true and every hook becomes a no-op: dependency edits and install commands are no longer blocked, the startup check for jq/curl/python3 is skipped, and successful installs stop being auto-recorded. Use it as a temporary escape hatch when a hook misfires or you are working offline, then switch it back. A VS_DISABLE variable set in your shell overrides this setting in both directions.", "default": false }, "window_hours": { "type": "number", - "title": "Check freshness window (hours)", - "description": "How long a /vs-record entry stays fresh before the hook re-blocks.", + "title": "How long a recorded version check stays valid (hours)", + "description": "Default: 24 hours (minimum 1, maximum 168 = one week). A check you save with /vs-record satisfies the guardrail for this long; once it lapses, the next change to that dependency is blocked again until you re-verify the version against its registry. Lower it to catch fast-moving packages and new advisories sooner; raise it to avoid repeat lookups during a long refactor, at the cost of acting on staler data.", "default": 24, "min": 1, "max": 168