Library Import ignores selected destination root folder and organizes files inside the scanned root instead

[Taldren76]

Description

When using Library Import to scan one root folder and import into a different root folder, Listenarr ignores the selected destination and creates the organized Author/Title folders inside the scanned root folder instead.

Expected Behavior

• Scan root: books (/audiobooks/books)
• Destination root: library (/audiobooks/library) — also marked as Default
• On import (Hardlink/Copy): Files should be organized into /audiobooks/library/Author/Title/...

Actual Behavior

Files are organized into /audiobooks/books/Author/Title/... (inside the scanned root), completely ignoring the selected destination root folder.

Steps to Reproduce

1. Create two Root Folders:
   • books → /audiobooks/books
   • library → /audiobooks/library (set as Default)
2. Place unorganized .m4b files into /audiobooks/books
3. Go to Library Import
4. Select the books root folder and click Scan
5. Select the destination as library
6. Choose Hardlink or Copy and click Import
7. Observe that new organized folders are created inside /audiobooks/books instead of /audiobooks/library

Environment

• Image: ghcr.io/listenarrs/listenarr:canary
• Deployment: Unraid Docker
• Volume mapping:
  • Host /mnt/user/multimedia/AudioBooks → Container /audiobooks
• library is correctly marked as the Default root folder

Additional Context

This makes the common workflow of using one folder as an “incoming/unorganized” drop location (e.g. from OpenAudible) and another as the final organized library unreliable. The destination selector appears in the UI but does not appear to be applied during the import path generation.