Shared folder import folder location field improperly disabled in "Add to Vault" modal

[C-Bjorn]

Bug Description

When adding a shared folder to the vault using the "Add to vault" modal, the "Folder location" field is disabled (cannot be selected or edited) in some scenarios. This occurs even when it should be possible to set the destination folder location.

Steps to Reproduce

1. Get invited to a shared folder and attempt to add it to your vault.
2. Observe that the folder location field, which defaults to /, is visible in the modal.
3. The field is not interactive—the cursor can't be set and the folder path cannot be changed.

Technical Details

• Code: In src/components/AddToVaultModalContent.svelte, the FolderSelectInput's disabled property is set to disabled={availableFolders.length === 0}.
• When availableFolders.length === 0, the entire FolderSelectInput is disabled.
• This appears to be an implementation oversight. The disabling should depend on whether a folder is selected—not whether folders are globally available.
• For users, this makes it impossible to change the target location for imported shared folders, except when specific frontend state is met, which may not be intended.

Expected Behavior

• The folder location input should be enabled when a folder is being added, so that users can select their destination.
• It should not be globally disabled based on the global number of available folders.

Not Feature-Gated

• There is no logic or feature gate intentionally locking this feature to premium/beta. The field disabling is purely UI state-based.

Related Code

<FolderSelectInput
  {app}
  {sharedFolders}
  selectedFolder={folderLocation}
  disabled={availableFolders.length === 0}
/>

Recommendation

• The disabling logic for the input should likely be disabled={!selectedRemoteFolder} or similar, reflecting per-session/modal state, not the global count of available folders.

Environment

• Relay plugin version: [please specify]
• Obsidian version: [please specify]
• OS: [please specify]