Sync the skill and hooks to memvara v0.15.0 - #50
Merged
Merged
Conversation
Re-vendors the skill and the hook tree from memvara/memvara v0.15.0 (026be5cf) with this repository's own sync steps, moves skill.lock and hooks.lock to that commit, keeps this repository's host= line, and composes CLAUDE.md from plugin-claude.md with the local block unchanged. The hook tree was pinned before v0.10.0, so this brings six releases of hook changes. Eight files are new and are now listed in ALLOWED_HOOK_FILES after being read: lib/agentic.py, lib/counts.py, lib/mark.py, lib/project.py, lib/project_vectors.json, lib/read_model.py, lib/settings.py and lib/state_file.py. Agentic capture (#241) runs only when the first extractor is claude -p, so it stays inert on this host. The allowance and single-send fixes (#245) and the capture-run header (#246) are in the shared hosted client. The README now says what the hooks keep and send: the project cache and the Memvara-Project header, the per-session counts, the recall mark, the switches in ~/.memvara/settings.json, and the capture.log line agentic capture leaves on this host. It also states the OAuth grant length the vendored skill states.
The counts file records lines the per-prompt recall hook injected, not the session-start block, so the README now says the recall hook.
Merged
sethigoldy
added a commit
that referenced
this pull request
Sep 24, 2026
Bumps the plugin version from 0.2.4 to 0.3.0, so that existing installs are offered the skill and hooks from memvara core v0.15.0, vendored in #50. Also corrects three places that said the hooks arrived in 0.2.5; they shipped in 0.2.4.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this does
Updates the plugin to memvara core v0.15.0 (tag
v0.15.0, commit026be5cfd815419fa4c7eda2cb0ada109ea22cab).skills/memvara/and the hook tree intohooks/with the steps inskill-sync.ymlandhooks-sync.yml, run against a checkout of the tag instead of a fresh clone. Both trees match the tag byte for byte.skill.lockandhooks.lockto026be5cf. Only thesha=lines change, andhost=opencodestays.CLAUDE.mdfromplugin-claude.mdat the tag. The local block is byte-identical before and after; the rest of the file now equals the canonical, which had been rewritten in plain English since the last sync here.The hook tree was pinned before v0.10.0, so this brings six releases of hook changes, including agentic capture (memvara/memvara#241), the named daily recall allowance and single-send hosted recalls (memvara/memvara#245), and the
Memvara-Capture-Runheader (memvara/memvara#246). The host record foropencodedid not change: capture keeps its 120-second limit.What did not sync cleanly, and what was done about it
The vendored bytes synced cleanly. The repository's own guards then failed, each for a real reason, and each was fixed rather than relaxed:
ALLOWED_HOOK_FILESafter being read, with a comment saying what each one is:lib/agentic.py,lib/counts.py,lib/mark.py,lib/project.py,lib/project_vectors.json,lib/read_model.py,lib/settings.pyandlib/state_file.py.claude -p, and here the first isopencode run. With the switch on by default, each captured turn writes a line tocapture.logsaying agentic capture was skipped. The README says so and how to turn the line off.README
A new section, "What else the hooks keep and send", describes what the v0.15.0 hooks add on this host: the project cache in
~/.memvara/.hooks/projects/and theMemvara-Projectheader on hosted calls, the per-session counts in~/.memvara/.hooks/counts/, the recall mark, the three switches in~/.memvara/settings.jsonthat turn them off, and thecapture.logline above. The OAuth grant is described the way the vendored skill describes it: until it is revoked, or ten years.Tests
Run in this branch's worktree with
MEMVARA_LIBRARYpointing at a checkout ofv0.15.0whoseorigin/mainis the same commit, so the drift and freshness checks compared against the tag. Hook tests ran with stdin closed (</dev/null).Review
A code review at high effort ran on this pull request. The review command could not target a pull request in this repository from the session that opened it, so the reviewer read
git diff origin/main...HEADat the same depth, and checked each claim in the files this repository owns against the vendored code and the core CHANGELOG. The vendored trees were left out because they are byte-identical to the tag.It found nothing to fix here. The review of the same section in cursor-memvara found that the
counts/bullet credited the first number to all the hooks, when only the per-prompt recall hook adds to it. That applies here too and is fixed in 7abc3e4.Not in this pull request