chore: verify pin set against core 0.95.1

[mabry1985]

Bumps verified_against 0.94.0 → 0.95.1.

The current pin set (portfolio v0.16.0, github v0.1.3, project_board v0.32.0, agent_browser v0.5.1) is deployed live on the roxy Portfolio Manager running protoAgent core 0.95.1 on ava:

• manager tier loads clean: delegates + portfolio + github (write enabled)
• board v0.32.0 installed-not-enabled for spawned Lead Engineer teams (fail-closed gate)
• coder runtime present: proto 0.71.0 + git; protoContent write-clone reset to origin/main
• fleet log confirms app version changed since last boot: 0.93.1 -> 0.95.1

Lets the verify-bundle workflow re-confirm against 0.95.1.

🤖 Generated with Claude Code

[protoquinn]

👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow.

[protoquinn]

QA Audit — PR #32 | chore: verify pin set against core 0.95.1

VERDICT: WARN (CI pending — non-blocking comment; approve-on-green policy promotes to APPROVED once checks settle)

---

CI Status

• bump: skipped
• verify: queued ⏳

CI is still settling. Per the approve-on-green policy, this review will be promoted to a formal APPROVE automatically once the verify check completes terminal-green — no re-review needed.

---

Diff Review

• verified_against bumped 0.94.0 → 0.95.1 in protoagent.bundle.yaml:7 — aligns with the roxy deployment evidence
• project_board plugin ref bumped v0.31.0 → v0.32.0 — matches the deployed pin set

---

Observations

• GAP: Could not verify tag v0.32.0 on protoLabsAI/projectBoard-plugin (tool unavailable). Deployment evidence from PR description (live on roxy, manager tier loads clean, board fail-closed) substantiates the bump.
• No unresolved CodeRabbit threads. Past PR #31 on same file was APPROVED — same pattern.

— Quinn, QA Engineer

[protoquinn]

Submitted COMMENT review on #32.

[protoquinn]

✅ CI went terminal-green with no blockers on the prior review — promoting it to APPROVED per the approve-on-green policy (#748).

[protoquinn]

CI terminal-green, no blockers on prior review — auto-approving on green (#748).

[protoquinn]

🔀 Approved and terminal-green, but GitHub's auto-merge never completed (phantom BLOCKED — ws-5sc); the reconciliation sweep completed the squash merge.