fix(ai): handle empty combat withdrawal members - #7248
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus 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 |
|
Superseded by #7270, which merged the same |
Fixes #7095.\n\nAvoids eager indexing when combat-withdrawal candidate members are empty or non-singular; only a one-member slice yields a combat pair.