chore: bring verified_against + README in step with the 0.106.0 base - #9
Merged
Conversation
#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: 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.
#8 bumped
Dockerfiletoprotoagent:0.106.0but left two coupled fields at0.104.5:protoagent.bundle.yaml:28verified_against0.104.50.106.0README.md:56pinned-base line0.104.50.106.0That's 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 — and that's the field an operator reads to decide whether a bump has been checked.Verified against the running instance
Vera is live on the 0.106.0 base (container up, 0 restarts):
scripts/check_card_drift.py→ OK — description set, skills['pr_review'], version0.106.0scripts/a2a_conformance.py→ 28 passed, 0 failed — card, version gate (-32009on a missingA2A-Versionheader), 11/11 JSON-RPC methods, v0.3 aliasesname=vera, skillpr_reviewconfidence-v1correctly gone (protoAgent#2092 stopped declaring an extension nothing emits)🤖 Generated with Claude Code