### Bug Description When organizing a directory to a directory, craft-parts exhibits two different behaviors: MERGE and NEST, depending on the presence of glob keys. If the source is a glob key and destination is the `(overlay)` pseudo-partition the behavior is different from all other glob key cases, as shown in the table below: | Key type | Destination type | Behavior | |------------------|-------------------|----------| | Explicit (no *) | Any | MERGE | | Glob (*) | Partition root | NEST | | Glob (*) | Overlay partition | MERGE | | Glob (*) | Regular path | NEST | The inconsistency is at lines 199-202 of organize.py: if dst_path in install_dir_map.values(): real_dst_path = dst_path / src_path.name else: real_dst_path = dst_path The "else" branch handles the overlay partition case and sets real_dst_path to dst_path directly, causing a MERGE instead of a NEST. To make the overlay partition consistent with other destinations, the fix would be to also nest the source directory name for the overlay partition: if dst_path in install_dir_map.values(): real_dst_path = dst_path / src_path.name elif dst_partition_pair.partition == OVERLAY_PARTITION: real_dst_path = dst_path / src_path.name else: real_dst_path = dst_path This ensures that a glob key always nests, regardless of whether the destination is a partition root, overlay partition, or regular path. The only case that should MERGE is when the key is explicit (no *), since the user is explicitly naming the source directory and specifying where its contents should go. [organize_behavior.txt](https://github.com/user-attachments/files/28116512/organize_behavior.txt) ### To Reproduce Create a part that organizes from a glob key to a directory under `(overlay)/`. ### part yaml ```shell ``` ### Relevant log output ```shell N/A ```