deploy(vera): bump the protoAgent base 0.108.0 → 0.132.0 - #27
Merged
Conversation
The plugin pins are already current (pr-reviewer v0.24.0 and github v0.3.0 are both the newest tags; protopatch 0.6.1 is the newest npm). The core is the only thing that drifted — 24 minor releases behind, so this is the deliberate base bump the Dockerfile asks for, with `verified_against` moved in step. What's in it for Vera specifically (she's headless — most of the range is console/desktop/Windows work that never reaches her): - #2373 `fix(review): findings contract requires verbatim evidence quotes` (0.126.0) — the CORE half of the grounding fix. pr-reviewer v0.24.0 shipped the plugin half in #26 and has been running without its counterpart since. - #2447 `fix(review): build the published review from blocks, never echo model text` (0.130.0) — the core twin of pr-reviewer#53, still open. - #2297 `feat(workflows): opt-in per-step timeout with graceful degradation` (0.116.0) — the mechanism pr-reviewer#47 needs for the slowest-finder floor (live eval: 57 exhaustions, crossfile slowest in 190 reviews, p90 752s). - #2341 `fix(llm): retry a provider that goes silent mid-stream` (0.120.0) and #2349 `fix(a2a): fail a wedged turn instead of leaving it WORKING forever` (0.121.0) — both bear on the 88.6% completion rate. - #2389 `feat(config): merge-on-boot declarative seeding` (0.126.0) — the fleet-wide fix for our seed-once caveat. It is opt-in via PROTOAGENT_SEED_MERGE, left UNSET here: the seed carries `repos: []` while the live volume holds the 9-repo allowlist, so enabling it is a compose change to make deliberately, not a side effect of this bump. Verified by building this image and booting it on a throwaway config volume: all 8 plugins load, pr-reviewer registers its tools + webhook/dispatch/sweep and mounts both routers, the webhook stays auth-exempt (HMAC-authed) while /api/plugins/pr-reviewer/eval is 200 with the bearer and 401 without and returns the unchanged schema, the seeded a2a identity survives (card serves Vera's description + the pr_review skill, version 0.132.0), SOUL seeds, and clawpatch 0.6.1 runs on node 22. No breaking changes in the range. Watchtower rolls her on merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0178c2V1CuZy2oQKDRG8zYca
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.
The plugin pins are already current —
pr-reviewerv0.24.0 andgithubv0.3.0 are both the newest tags upstream (pr-reviewer'smainis 0 commits ahead of v0.24.0), and protopatch 0.6.1 is the newest npm. The core is the only thing that drifted: 24 minor releases behind. This is the deliberate base bump the Dockerfile asks for, withverified_againstmoved in step.What's actually in it for Vera
She's headless, so most of the 0.109→0.132 range (console, desktop, Windows, OAuth providers) never reaches her. What does:
fix(review): findings contract requires verbatim evidence quotesfix(review): build the published review from blocks, never echo model textfeat(workflows): opt-in per-step timeout with graceful degradationfix(llm): retry a provider that goes silent mid-streamfix(a2a): fail a wedged turn instead of leaving it WORKING foreverfix(plugins): structured error envelope for plugin endpointsfix(plugins): hot-REMOUNT plugin routers on reload#2389
feat(config): merge-on-boot declarative seeding(0.126.0) is the fleet-wide fix for our seed-once caveat — the one that made the bakeda2a:block invisible to an already-seeded volume. It is opt-in viaPROTOAGENT_SEED_MERGEand left UNSET here: our seed carriesrepos: []while the live volume holds the 9-repo allowlist, so turning it on is a compose change inhomelab-iacto make deliberately, not a side effect of this bump. (Its three-way merge would keep the live value anyway — the first merge boot has no baseline, so every existing key is treated as operator-owned — but that's not a property to lean on by accident.)Verification
Built this image and booted it on a throwaway config volume:
pr-reviewerregisters 2 tools + 1 subagent + webhook/dispatch/sweep, and both routers mount (/plugins/…and/api/plugins/…).pr-reviewer-sweepsurface starts;/plugins/pr-reviewer/webhookstays in the auth-exempt list (HMAC-authed), so the cloudflared path still works./api/plugins/pr-reviewer/eval→ 200 with the bearer, 401 without, and the response schema is unchanged field-for-field.pr_reviewskill (the runtime half of the drift guard),version: 0.132.0.SOUL.mdseeds;clawpatch 0.6.1runs on node v22.23.2.No BREAKING entries in the changelog range.
On merge: CI publishes
:latestand Watchtower rolls her in ~60s. The config volume (vera_vera-config) persists, so the allowlist,shadow_mode: falseandpromotion_owner: trueall carry over.🤖 Generated with Claude Code
https://claude.ai/code/session_0178c2V1CuZy2oQKDRG8zYca