chore(deps): base protoagent 0.106.0 + github-plugin v0.3.0 — head-pinned reads - #8
Merged
Merged
Conversation
…nned reads
Lands the pr-reviewer-plugin#20 fix on Vera. The two bumps are one change and
must ship together:
• base 0.106.0 carries protoAgent#2100 — review-finder and verifier now read
a PR's code with `github_read_pr_file` (and the verifier fails closed to
"uncertain" when it cannot read at the head)
• github-plugin v0.3.0 PROVIDES that tool
Base alone would leave the seats naming a tool that isn't installed; the plugin
alone would install a tool nothing calls.
Why it matters: `github_read_file`'s `ref` defaults to the repo's default
branch, so the panel was reading the PRE-PR file and "confirming" that symbols
a PR ADDS don't exist — false blockers on correct PRs (protoAgent#2088, and
#2094 compounded 8→9→11 across re-reviews). Prompt-level ref discipline was
already in both seats, the recipe passed the head SHA everywhere, and a test
asserted the wording — it still read main. The tool now takes no ref at all.
Note this also moves the base 0.104.5 → 0.106.0, so Vera picks up everything
else in that range.
Follow-up once deployed: re-enable `regate: true` on her live config (turned off
while these false FAILs could arm blocking reviews).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mabry1985
added a commit
that referenced
this pull request
Jul 21, 2026
) #8 bumped the Dockerfile to protoagent:0.106.0 but left the manifest's `verified_against` and the README's pinned-base line at 0.104.5 — the exact lockstep the Dockerfile comment calls out ("keeping it in step with the manifest's `verified_against`"). Left drifted, the manifest claims Vera is verified against a core two minor versions behind the one she actually runs, which is the field an operator reads to decide whether a bump has been checked. Verified against the running instance on the 0.106.0 base: • scripts/check_card_drift.py → OK (description set, skills ['pr_review'], version 0.106.0) • scripts/a2a_conformance.py → 28 passed, 0 failed (card, version gate, 11/11 methods, v0.3 compat) • card identity intact: name=vera, skill pr_review, 3 declared extensions (confidence-v1 correctly gone as of protoAgent#2092) • container running, 0 restarts Co-authored-by: GitHub CI <ci@example.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Lands the pr-reviewer-plugin#20 fix on Vera.
The two bumps are one change and must ship together:
protoagent:0.104.5→0.106.0review-finder+verifierread PR code withgithub_read_pr_file, and the verifier fails closed touncertainwhen it can't read at the headgithub-pluginv0.2.0 → v0.3.0Base alone leaves the seats naming a tool that isn't installed; the plugin alone installs a tool nothing calls.
Why
github_read_file'srefdefaults to the repo's default branch, so the panel read the pre-PR file and "confirmed" that symbols a PR adds don't exist — false blockers on correct PRs. Reproduced on protoAgent#2088 (goalDetailQueryreported missing; exported at line 90 of the reviewed head), and #2094 compounded 8 → 9 → 11 findings across three re-reviews because recalledprior_findingsre-seed each panel.Prompt-level ref discipline was already in both seats, the recipe passed the head SHA to every step, and there was a passing test asserting the wording — and it still read
main. v0.3.0's tool takes no ref at all.Scope note
This also moves the base 0.104.5 → 0.106.0, so Vera picks up everything else released in that range, not just this fix.
After merge
Publish → roll Vera → re-enable
regate: true(disabled while false FAILs could arm blocking reviews) → watch the next few FAILs verify as genuine.🤖 Generated with Claude Code