[nikku]

Proposed Changes

Adds a rule that warns when termination inside multi-instance is used. For non-BPMN experts this is ambiguous - does not do what you may expect (cancel single instance only).

Closes #223

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]

🟡 Changes recommended

A nonexistent fixture filename causes ENOENT failures in both test references, while the documentation mischaracterizes legitimate termination of parallel work within the current iteration.

2 open issues

• Use the correct fixture filename in both references · New
• Clarify that terminating the current iteration is valid · New

What changed in this PR

Adds no-multi-instance-termination to bpmnlint to clarify that termination directly inside a multi-instance subprocess affects only the current iteration, addressing #223.

Changes:

• Implements the scope advisory and enables it as a warning in recommended.
• Adds fixtures and tests covering iteration types, nested scopes, event-definition references, and configuration integration.
• Documents the rule with examples of iteration-level and all-iteration cancellation.

File	Description
test/​spec/​config-spec.mjs	Expects the new recommended warning.
test/​rules/​no-multi-instance-termination/​valid-other-end-events.bpmn	Covers non-terminate end events.
test/​rules/​no-multi-instance-termination/​valid-non-multi-instance.bpmn	Provides non-multi-instance controls.
test/​rules/​no-multi-instance-termination/​valid-nested.bpmn	Covers separate nested termination scopes.
test/​rules/​no-multi-instance-termination/​transaction.bpmn	Covers multi-instance transactions.
test/​rules/​no-multi-instance-termination/​sequential.bpmn	Covers sequential iterations.
test/​rules/​no-multi-instance-termination/​referenced-termination.bpmn	Covers referenced terminate definitions.
test/​rules/​no-multi-instance-termination/​parallel.bpmn	Covers explicit and default parallel iterations.
test/​rules/​no-multi-instance-termination/​nested-multi-instance.bpmn	Covers nested multi-instance scopes.
test/​rules/​no-multi-instance-termination.mjs	Adds rule and integration assertions.
test/​integration/​compilation/​test/​bpmnlintrc.expected.js	Updates expected compiled rule registration.
rules/​no-multi-instance-termination.js	Implements the termination-scope warning.
docs/​rules/​README.md	Links the new rule documentation.
docs/​rules/​no-multi-instance-termination.md	Explains the rule and cancellation examples.
docs/​rules/​examples/​no-multi-instance-termination-incorrect.bpmn	Illustrates termination within one iteration.
docs/​rules/​examples/​no-multi-instance-termination-event-subprocess-correct.bpmn	Illustrates iteration-level event-subprocess interruption.
docs/​rules/​examples/​no-multi-instance-termination-correct.bpmn	Illustrates cancellation of all iterations.
config/​recommended.js	Enables the advisory at warning level.
config/​all.js	Registers the rule in the complete ruleset.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The escalation examples omit required escalation references, so they do not reliably demonstrate the documented cancellation behavior.

1 open issue

• Add escalationRef to throwing escalation end event · New

2 resolved since last review

• Use the correct fixture filename in both references
• Clarify that terminating the current iteration is valid

_{Review effort: Balanced}