Handle special outputCollection defined variables

[nikku]

Proposed Changes

Ensure that outputCollection is a variable that always bubbles - it cannot be contained in ad-hoc sub-processes.

Depends on bpmn-io/extract-process-variables#38

Checklist

Ensure you provide everything we need to review your contribution:

• Contribution meets our definition of done
• Pull request establishes context
  • Link to related issue(s), i.e. Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}
  • Brief textual description of the changes
  • Screenshots or short videos showing UI/UX changes
  • Steps to try out, i.e. using the @bpmn-io/sr tool

[Copilot]

Pull request overview

This pull request updates test expectations to reflect that outputCollection variables from ad-hoc sub-processes now always bubble up to the parent process scope and cannot be contained within the sub-process. This change depends on upstream modifications in @bpmn-io/extract-process-variables v2.2.0.

Changes:

• Updated test assertions to expect toolCallResults (an outputCollection variable) to have parent process scope instead of ad-hoc sub-process scope
• Modified test descriptions to clarify that outputCollection variables leak to parent processes
• Added explanatory comments documenting that this leakage is intentional and cannot be prevented

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.