Retain completed sibling switches and declared trigger types

The owner authorized consolidation of completed Hub work outside the original plan, while preserving the deployment checkout and the active validation path. Another terminal completed this change and removed its worktree; that path was restored at its committed head without changing the deployment source. Private ancestry is not imported.

Allowed paths: case-compile bed/profile/check/command-obligation implementations, their tests, fixtures and format tables, package identity/tests, regenerated workbook samples and README.

Sibling switches use declared pairs and two fully parsed leaf paths of the same parent; the enum-signature guards remain. Trigger types default to the pack’s router/client/server declaration and may be narrowed by a profile. An explicit empty declaration stays empty; unsupported declared types are rejected, not silently discarded. A missing sibling does not authorize repeated cleanup. The public package advances to 3.4.6 and is re-signed.