Repository navigation
chore: Extend the completion gate to require fresh code-review evidence, not just verification - #654
Conversation
Agentflare-Branch: task/182-extend-the-completion-gate-to-require-fr Agentflare-Item: 182-extend-the-completion-gate-to-require-fr
Agentflare-Branch: task/182-extend-the-completion-gate-to-require-fr Agentflare-Item: 182-extend-the-completion-gate-to-require-fr
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (4)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe completion gate now requires fresh verification and review evidence. Runtime state records ChangesReview evidence completion gate
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The completion gate now requires fresh review evidence alongside verification evidence, with review state recorded, invalidated after mutations, and checked before completion actions. The change is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
Tracking this PR for automated review ( |
Status: Implementation is complete and verified.
This branch already had a full implementation checkpointed from a prior session (commits
1472f79/eefa054, "wip(sdd-loop): task 0 checkpoint"). I reviewed it against the task spec and it matches exactly:ReviewEvidencestruct insrc/optimize/runtime.rs, parallel toVerificationEvidence, withhas_fresh_review/invalidate_reviewusing the sameVERIFICATION_FRESHNESS_SECSwindow.is_review_completion()triggers on theReportFindingstool call specifically (notSkill/Task/Agentdispatch) — the doc comment explains why: dispatch only proves a skill loaded or an agent was backgrounded, not that review work happened. This is a real, documented coverage gap: arequesting-code-reviewsubagent dispatch that only returns prose won't be picked up.completion_gate_reason(src/hook_redirect.rs) now takeshas_fresh_review: booland blocksdone/check_mergewith a review-specific message, mirroring the verification message's style.hook.rs(PreToolUse) andhook_completion_gate.rs(PostToolUse records evidence onReportFindingssuccess, invalidates both verification and review evidence on mutating tool calls).Verification performed this session:
cargo build --lib— clean.cargo test --bin agentflare -- completion_gate review— all 30+ new/updated tests pass (hook_redirect::,hook_completion_gate::,optimize::runtime::).cargo test --bin agentflare— 109/110 pass; the one failure (mcp_prompts::tests::optimize_review_returns_full_skill_body) is unrelated (untouchedflare-codecrate) and I confirmed it also fails identically on a cleanmastercheckout.cargo clippyon the touched files — no warnings. Workspace-wide-D warningsclippy has pre-existing failures in unrelated crates (agent-registry,flare-workflow) that I confirmed also exist onmaster.Concerns: none blocking. Two things worth your attention:
Opened by
claude-codeon flared:51bb8de6c33b for item #182 via agentflare.Summary by CodeRabbit
New Features
Bug Fixes