feat(review): enhance diagnostic propagation for negotiated failures - #221
feat(review): enhance diagnostic propagation for negotiated failures#221Juanjo-Ramirez wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughNative integration failures now carry process diagnostics through both native CLI implementations. Controller routing recognizes these errors, sanitizes diagnostics, omits raw failure envelopes, and validates negotiated unknown ChangesNative diagnostics propagation
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/review-controller-native-routing.test.ts`:
- Around line 1163-1174: Update the fixture around NativeReviewCliV216.invoke to
instantiate the actual NativeReviewIntegrationError rather than assigning its
name onto a plain Error. Add an adapter-level non-zero-envelope test that
verifies invoke attaches diagnostics before controller sanitization, and ensure
the test exercises the changed native transport path.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 3f05779b-9a5e-45bc-864f-5b2c7b197bc7
⛔ Files ignored due to path filters (8)
openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/README.mdis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/manifest.jsonis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/observed-start-failure.jsonis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/patch.diffis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/reference/failure.fixture.jsonis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/reference/failure.schema.jsonis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/reproduction.mdis excluded by!openspec/changes/**openspec/changes/consolidate-review-parity-runtime/upstream-trackers/handoff-122-review-diagnostic-propagation/validation.mdis excluded by!openspec/changes/**
📒 Files selected for processing (4)
extensions/gentle-ai.tslib/native-review-cli.tsruntime/native-review-cli.mjstests/review-controller-native-routing.test.ts
Review diagnostic propagation handoff
The Pi adapter repair is proven: after verified package-local Gentle AI v2.1.11 provisioning, local provider inspection succeeds and an authorized fresh ordinary START returns a sanitized provider diagnostic. The raw negotiated failure payload is not exposed.
Review first
patch.difffor the four-file repair.reproduction.mdfrom a source checkout.validation.mdbefore treating the installed package as validated.Impact and decision
review/startdiagnostic captured inobserved-start-failure.json.non-zero/operation_outcome_unknowndiagnostic. Native maintainers must add stage-level sanitized failure evidence.startwith no lineage, expose only sanitized diagnostics forreview/start; never exposenative_failureor raw payload content.v1.2.0at113906a34c1b527ba2d65806b7638bff32b8e916.fix/review-diagnostic-propagationat4d5214b410d352712be20917e81f9ce5974d039a, with the repair present as working-tree changes.Evidence boundary
Proven: the focused source regression passes; package-local Gentle AI v2.1.11 provisioning was verified; local provider inspection succeeds; and the authorized fresh ordinary START returned the sanitized diagnostic recorded in
observed-start-failure.json.Native escalation required: the remaining native failure is generic (
non-zero/operation_outcome_unknown) and lacks stage-level sanitized failure evidence. Native maintainers must add that evidence before the root cause can be diagnosed.Authority boundary: status reconciliation reports no lineage and action
start. No replay is safe, and this evidence cannot authorize a commit. This bundle does not authorize creating, replaying, or inspecting a real review lineage.Tracker paths
../122-receipt-tree-path-diagnostics.md../README.md(the feat(review): validate scope-changed should identify which files differ #122 row)Safety statement
This bundle contains no private authority material, credentials, tokens, native receipts, real review snapshots, target values, repository identities, or user identities.
patch.diffredacts a test-only sentinel value and excludes this handoff directory, so it is a review artifact rather than an apply-ready patch.Summary by CodeRabbit