chore(skill-pin): bump SHA-256 after vaultpilot-skill#9 (closes #375) - #378
Closed
szhygulin wants to merge 1 commit into
Closed
chore(skill-pin): bump SHA-256 after vaultpilot-skill#9 (closes #375)#378szhygulin wants to merge 1 commit into
szhygulin wants to merge 1 commit into
Conversation
…375) vaultpilot-skill PR #9 (closes vaultpilot-skill#8) replaced the remaining `<OWNER>` placeholder in SKILL.md:20 with the canonical `szhygulin` namespace. Coordinated pin bump per the maintainer workflow in vaultpilot-skill's README. Pin update: cd689838314a700dfff80d4c881bf51190cd6c71c747f3152e7cab8d943df2cc → 1f437e7e0870438ebe7d4c8b40b210b54041bd31a16110152f091761fb053ff5 Re-verified against the merged-master SKILL.md via: curl -fsSL https://raw.githubusercontent.com/szhygulin/vaultpilot-skill/master/SKILL.md | sha256sum Sentinel stays at v4 (`VAULTPILOT_PREFLIGHT_INTEGRITY_v4_7655818578c7a044`) — prose-only fix, no protocol change. Note: vaultpilot-mcp#375 originally predicted the post-fix hash as `7ea855a4…`, computed by applying the OWNER fix to the original `10db66ad…` baseline. That baseline was already stale by the time the issue was filed (vaultpilot-skill PRs #4 + #5 added Invariants #7 + #8 since the original pin was set), so the actual post-merge hash differs from the prediction. The pin in this PR is keyed off the live `master` tree post-#9, not the predicted value. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #375. Coordinated pin bump in lockstep with vaultpilot-skill#9 (which closed vaultpilot-skill#8 — the remaining `` placeholder in `SKILL.md:20`).
Pin update
Re-verified against the merged-master `SKILL.md`:
```
$ curl -fsSL https://raw.githubusercontent.com/szhygulin/vaultpilot-skill/master/SKILL.md | sha256sum
1f437e7e0870438ebe7d4c8b40b210b54041bd31a16110152f091761fb053ff5 -
```
Sentinel stays at v4 (`VAULTPILOT_PREFLIGHT_INTEGRITY_v4_7655818578c7a044`) — prose-only fix in vaultpilot-skill, no protocol change.
Note on the issue's predicted hash
#375 predicted the post-fix hash as `7ea855a4…`, computed by applying the OWNER fix to the original `10db66ad…` baseline. By the time the issue was filed, that baseline was already stale — vaultpilot-skill PRs #4 + #5 had added Invariants #7 + #8 to `SKILL.md` since the original pin was set. The actual post-merge hash differs from the prediction; the pin in this PR is keyed off the live `master` tree post-#9.
This drift between "live master" and "the pin in main" was the prompt for vaultpilot-skill#10 — the integrity alarm should have fired during testing when the local `SKILL.md` diverged from the MCP-emitted pin, but it did not. That investigation is tracked separately.
Test plan
🤖 Generated with Claude Code