fix(review): preserve terminal escalation evidence - #1819
Conversation
Reuse the existing STATUS escalation decoder for terminal capture closures and retain its native diagnostic evidence in tool output without adding a continuation. Refs: Gentleman-Programming/gentle-ai#4553 Validation: 98 focused tests, real native single-lens committed-candidate E2E, type baseline without regressions, runtime parity, provider-contract and runtime harness. Full unit and expanded devbinary suites retain failures independently reproduced on pristine main.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (5)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughEscalation data is now decoded for last-event closures and included in escalated closure output. Tests cover escalation evidence, closure capture behavior, and terminal status from the reviewer relay. ChangesEscalation Closure Data
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The escalation-evidence change is mergeable after normal checks; no unresolved issue attributable to this PR is established. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Linked issue
Refs Gentleman-Programming/gentle-ai#4553 (
status:approved, nonclosing).PR type
type:bug)Summary
escalationdiagnostic on terminal capture closures using the existing STATUS parser.Review path
lib/review-integration-v2.tsand generated runtimeextensions/gentle-ai.tsReview the decoder and mapper first. Native lifecycle, finding-rationale retrieval, recovery, and the separate targeted-validator evidence compatibility issue are out of scope.
Verification
node --experimental-strip-types --test tests/review-last-event-closure.test.ts tests/review-integration-v2.test.ts tests/native-review-cli.test.ts.node --experimental-strip-types --test --test-name-pattern='terminal single-lens escalation' tests/devbinary/pi-host-relay.devtest.ts.git diff --checkpass.pnpm testreports 4,955 passed, 2 failed, 44 skipped. Pristine main reports the same two routing-test failures (4,951 passed, 2 failed, 44 skipped). The expanded devbinary file has the same two selected-untracked/mode-isolation failures in main and candidate; the new escalation E2E passes. These failures were not modified or waived.Scope and rollback
244 changed lines across five files. Revert this commit as one unit to restore the previous decoder and generated runtime. No native authority, consent, delivery, or terminal-state policy changes.
Summary by CodeRabbit