Add atomic Process group removal with explicit reuse and ordering impact

docs/language.rst

@@ -2292,6 +2292,26 @@ A qualified selection inside an expanded reusable process MUST NOT silently
 delete the outer reference or shared definition item. The editor directs the
 user to open the definition or explicitly select the outer reference.
 
+For a group of local Process or FunctionalChain contributions and maintained
+links, removal MUST admit every original typed selection member before reducing
+overlapping cascade commands. A selected link already removed by a selected
+occurrence's cascade remains a selected effect in the review. A mixed local and
+qualified selection MUST refuse as a whole, without a primary-only fallback.
+A locally owned ContextualLink is distinct from a read-only relation displayed
+inside a reused definition; its explicit owner governs removal even when both
+endpoint paths are qualified.
+
+The aggregate review MUST identify actual deleted records, changed surviving
+records, and affected caller definitions. Removing the last explicit topology
+marker can restore an exchange-only sequence's implicit ordered meaning;
+removing an interior exchange from a legacy order changes adjacent pairs.
+These consequences MUST be explicit before confirmation. Reused topology and
+entry/exit connections can also change without an interpretation-mode switch
+or new stored relation. Caller-definition counts MUST NOT be presented as
+counts of reference instances. Empty or incomplete surviving sequences retain
+their ordinary diagnostics; deletion MUST NOT invent replacement controls or
+links to conceal such consequences.
+
 Confirmation identifies the captured object and removal effect. Cancel and
 Escape preserve model, source and history. A confirmation token belongs to one
 dialog; changes to its document, revision, owner or selected identity invalidate