[Chore] Record historical conversation workspace mismatch - #1601
[Chore] Record historical conversation workspace mismatch#1601zoomote[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: Mark the PR ready. Required CI must pass before CodeRabbit starts. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What changed
Added a focused expected-failure test reproducing the historical-conversation workspace mismatch. The test opens the provider in one workspace, restores a conversation bound to another worktree, and asserts that file mention search should follow the open workspace.
Why this change was made
The mismatch is currently reproducible but lacked a durable automated signal. Using Vitest's expected-failure form documents the desired behavior without changing product logic or blessing the existing binding as correct.
Impact
There is no product behavior change. The suite now records one expected failure that can be converted to a normal regression test when conversation workspace switching is implemented.