Library auto-organize: per-root path templates (SAF + future folder-like remotes)

[LizAinslie]

Summary

Auto-organize library files into a user-specified path layout. Templates are per root / source instance so a flat Music/ dump of singles can use a different pattern than a full album tree, and the same system extends to folder-like remotes (WebDAV / cloud mounts) later.

Why

• Flat folders of singles make folder cover.jpg useless
• Users want {albumArtist}/{album}/{track} - {title}.{ext} without manual sorting
• SAF tree grants already allow create/rename/move inside the tree

Requirements

Templates (per root / source)

• Tokens: {albumArtist}, {artist}, {album}, {title}, {track}, {disc}, {year}, {ext}
• Separate patterns for album tracks vs singles / no-album
• Defaults shipped; editable per local SAF root and per remote folder-like source later

Behavior

1. Dry-run planned moves
2. Apply: create dirs, move/rename inside granted tree only
3. Update catalog paths / content URIs
4. Collision: skip | suffix | overwrite
5. Missing tags → optional _unsorted/

Settings UI

• Per-root Organize layout under Library / Sources
• Template editor + token cheatsheet + dry-run / apply

Branch

feature/library-sources