Skip to content

fix: clarify userConfig option copy shown at install #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KSEGIT merged 1 commit into from
Aug 4, 2026
Merged

fix: clarify userConfig option copy shown at install #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.",

@coderabbitai coderabbitai Bot Aug 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Clarify that only a non-empty VS_DISABLE value overrides disable.

scripts/lib/options.sh:6-12 treats an empty VS_DISABLE value as unset. Replace “A VS_DISABLE variable set in your shell” with “A non-empty VS_DISABLE value set in your shell” to match the actual precedence behavior.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.claude-plugin/plugin.json at line 31, Update the description value for the
disable setting to state that only a non-empty VS_DISABLE value set in the shell
overrides disable, replacing the broader wording while preserving the rest of
the description.

"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
Expand Down