Automatic import silently does nothing -- duplicate `importPath` rows in the settings table

Automatic/watch-folder import stopped picking anything up on my self-hosted instance (Docker on Unraid). Manually importing a single book still works fine and nothing useful shows up in the logs. Others on the same version saw imports eventually run but take 20+ minutes.

Resolution: Root cause: a settings-page/migration regression let more than one row for the importPath setting exist in the SQLite settings table, because there was no unique index on the setting name. getSetting("importPath") returns the first row -- which is always null -- while getSettings() returns the last row, the one the UI actually updates, so the watcher runs against a null root import path and finds nothing. Fix: delete the duplicate null rows and restart the container. Back up the database first.

From Docker Compose:

docker compose exec -it web sh -c 'sqlite3 "${STORYTELLER_DB_DIR:-$STORYTELLER_DATA_DIR}/${STORYTELLER_DB_FILENAME:-storyteller.db}" "DELETE FROM settings WHERE name = '\''importPath'\'' AND (value IS NULL OR value = '\''null'\'' OR value = '\'''\'') AND (SELECT COUNT(*) FROM settings WHERE name = '\''importPath'\'') > 1;"'

Or directly against the DB file:

sqlite3 /path/to/storyteller.db "DELETE FROM settings WHERE name = 'importPath' AND (value IS NULL OR value = 'null' OR value = '') AND (SELECT COUNT(*) FROM settings WHERE name = 'importPath') > 1;"

The permanent fix (deduping settings plus a unique index on setting name) went in with the importer/scanner rework that shipped in 2.14, so upgrading is the durable answer.