Follow-up to #82. The hook fixes landed on main but could not reach an install.
c569cdd rewrote all four hook scripts without bumping the manifest. The version is what the installer compares, so /plugin reported "already at the latest version (0.1.18)" and never refreshed its cache.
Both halves of the install were observably out of step:
~/.claude/plugins/marketplaces/scribe-plugin -> at 3284ac6, fixed
~/.claude/plugins/cache/.../scribe/0.1.18/ -> still lowercase env vars, jq -rR
The marketplace clone pulls on its own. The cache is what executes, and it is only re-copied when the version changes — so a plugin/ change without a bump ships to the repo and stops there.
This is the #1040 lesson, recorded in milestone #232's own verification section ("Any plugin/ change bumps plugin.json in the same commit") and missed anyway. Nothing enforces it: plugin/** triggers no CI workflow at all (#2204), so neither the missing bump nor the three broken scripts could have been caught automatically.
After merge: /plugin update + /reload-plugins should report 0.1.19, and /tmp/scribe-autoinject/ + /tmp/scribe-priorart/ should come into existence on the next prompt and file edit.
Follow-up to #82. The hook fixes landed on `main` but could not reach an install.
`c569cdd` rewrote all four hook scripts without bumping the manifest. The version is what the installer compares, so `/plugin` reported *"already at the latest version (0.1.18)"* and never refreshed its cache.
Both halves of the install were observably out of step:
```
~/.claude/plugins/marketplaces/scribe-plugin -> at 3284ac6, fixed
~/.claude/plugins/cache/.../scribe/0.1.18/ -> still lowercase env vars, jq -rR
```
The marketplace clone pulls on its own. The **cache is what executes**, and it is only re-copied when the version changes — so a `plugin/` change without a bump ships to the repo and stops there.
This is the #1040 lesson, recorded in milestone #232's own verification section ("Any `plugin/` change bumps `plugin.json` in the same commit") and missed anyway. Nothing enforces it: `plugin/**` triggers no CI workflow at all (#2204), so neither the missing bump nor the three broken scripts could have been caught automatically.
After merge: `/plugin` update + `/reload-plugins` should report 0.1.19, and `/tmp/scribe-autoinject/` + `/tmp/scribe-priorart/` should come into existence on the next prompt and file edit.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs
c569cdd rewrote all four hook scripts and did not bump the manifest. The
version is what the installer compares, so `/plugin` reported "already at
the latest version (0.1.18)" and never refreshed its cache — the fix was
on main and unreachable.
Both halves of the install were observably out of step:
~/.claude/plugins/marketplaces/scribe-plugin -> at 3284ac6, fixed
~/.claude/plugins/cache/.../scribe/0.1.18/ -> still lowercase env
vars and `jq -rR`
The clone pulls on its own; the CACHE is what executes, and it is only
re-copied when the version changes. So a plugin change without a bump
ships to the repo and stops there.
This is the #1040 lesson, already recorded in milestone #232's own
verification section ("Any `plugin/` change bumps `plugin.json` in the
same commit") and still missed — the rule was written down and not
followed. Nothing in CI enforces it, which is the same gap as #2204:
`plugin/**` triggers no workflow at all, so neither the missing bump nor
the broken scripts could be caught.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #82. The hook fixes landed on
mainbut could not reach an install.c569cddrewrote all four hook scripts without bumping the manifest. The version is what the installer compares, so/pluginreported "already at the latest version (0.1.18)" and never refreshed its cache.Both halves of the install were observably out of step:
The marketplace clone pulls on its own. The cache is what executes, and it is only re-copied when the version changes — so a
plugin/change without a bump ships to the repo and stops there.This is the #1040 lesson, recorded in milestone #232's own verification section ("Any
plugin/change bumpsplugin.jsonin the same commit") and missed anyway. Nothing enforces it:plugin/**triggers no CI workflow at all (#2204), so neither the missing bump nor the three broken scripts could have been caught automatically.After merge:
/pluginupdate +/reload-pluginsshould report 0.1.19, and/tmp/scribe-autoinject/+/tmp/scribe-priorart/should come into existence on the next prompt and file edit.🤖 Generated with Claude Code
https://claude.ai/code/session_01UaYUaouG9jjhATyuxCKrQs