UML 2.5 Break Fragment Scope Inside Nested Loop Combined Fragments

UML 2.5 combined fragments let modelers interrupt or exclude message flows using break and ignore operators. The goal is to determine the termination scope of a break fragment nested inside a loop operand across all participating lifelines.

The UML 2.5 specification describes break behavior informally, so it is unclear whether exiting a break inside a loop aborts only the current iteration, the enclosing combined fragment, or the entire interaction. Tool-specific extensions may override base semantics, which complicates cross-platform validation.

Assume UML 2.5 semantics without vendor extensions.

Does a break inside a loop terminate only the current loop iteration? Should the break propagate to all lifelines in the enclosing interaction? What is the correct guard-resolution order for ignore fragments nested under a break?