Thank you, this looks very good, appreciate the addition.
One small suggestion above re version, otherwise looks good to me.

Thanks for the look! Fix pushed in f1cc08c — drops the bogus "log line" claim and gives Docker users + local Python users separate paths to find their version.

drops the bogus "log line" claim

I am not sure I follow.

When I switch to debug level, I see these logs:

============== ENVIRONMENT SETTINGS ==============
image_tag: dev
short_commit_id: 06adae9
use_config_yaml: true

From here, users could provide us the tag as well as the commit ID.
What if we simply asked users to switch to debug logs and
(1) disable all jobs other than the ones failing
(2) switch to debug-level
(3) provide full logs, including the header that shows "VERBOSE | 🛠️ Decluttarr - Settings 🛠️" incl. commit ID etc?

As example:

VERBOSE | 🛠️ Decluttarr - Settings 🛠️

============== ENVIRONMENT SETTINGS ==============
image_tag: dev
short_commit_id: 06adae9
use_config_yaml: true
================ GENERAL SETTINGS ================
log_level: DEBUG
test_run: false
timer: 10
ssl_verification: true
private_tracker_handling: remove
public_tracker_handling: remove
obsolete_tag: Obsolete
protected_tag: Keep
================== ACTIVE JOBS ===================
🟢 remove_bad_files
⚪️ remove_done_seeding
🟢 remove_failed_downloads
🟢 remove_failed_imports
🟢 remove_metadata_missing
🟢 remove_missing_files
🟢 remove_orphans
🟢 remove_slow
🟢 remove_stalled
🟢 remove_unmonitored
🟢 search_unmet_cutoff
🟢 search_missing
🟢 detect_deletions
================== JOB SETTINGS ==================
remove_bad_files:
keep_archives: false
remove_failed_downloads: {}
remove_failed_imports:
message_patterns:

• Not a Custom Format upgrade for existing*
• Not an upgrade for existing*
• 'Found potentially dangerous file with extension'
• Invalid video file*
• No files found are eligible for import*
• One or more episodes expected in this release were not imported or missing from
  the release
  remove_metadata_missing:
  max_strikes: 3
  remove_missing_files: {}
  remove_orphans: {}
  remove_slow:
  max_strikes: 3
  min_speed: 100
  remove_stalled:
  max_strikes: 3
  remove_unmonitored: {}
  search_unmet_cutoff:
  max_concurrent_searches: 3
  min_days_between_searches: 7
  search_missing:
  max_concurrent_searches: 3
  min_days_between_searches: 7
  detect_deletions: {}
  =============== INSTANCE SETTINGS ================
  Sonarr:
• base_url: http://sonarr:8989
  api_key: '*****'
  Radarr:
• base_url: http://radarr:7878
  api_key: '*****'
  Readarr:
• base_url: http://readarr:8787
  api_key: '*****'
  ============ DOWNLOAD CLIENT SETTINGS ============
  qbittorrent:
• base_url: http://qbittorrent:8080
  name: qBittorrent

So something like replacing these three fields:

• Decluttarr version (input)
• Sanitized config (textarea, yaml-rendered)
• test_run state (dropdown)

With one consolidated field:

• Decluttarr startup banner + debug logs (textarea, shell-rendered) — "Run with log_level: DEBUG. Disable jobs not related to your issue (reduces noise). Paste the full
  output starting from the 🛠️ Decluttarr - Settings 🛠️ header through the cycle that exhibits the bug. API keys in the header are already masked as ***** — but scrub any
  ?apikey= in URLs from later log lines."

Yes, I think that sound sensible, what do you think?
As these logs can be lenghty, should we encourage them using an external pastebin? What do you think?

Yeah logs can be a pain. I like pastebin as alternative

Good call — Medium path applied in f1ab69d:

• Dropped the separate Sanitized config field (your settings banner already covers it)
• Rewrote the logs field to ask for the full 🛠️ Decluttarr - Settings 🛠️ startup banner + the failing cycle, with the three-step workflow you laid out: disable non-failing jobs → debug level → paste the lot
• Tweaked the version field description to mention the banner also has image_tag / short_commit_id, so reporters can cross-check

Net: 13 fields instead of 14, less duplication. Kept version / test_run / OS / *arr versions as separate easy-scan fields up top for triage at a glance — happy to drop those into the log paste too if you'd rather have everything in one place.

I think it‘s a good first version. Let‘s run with it snd finetune it along the way. Good to be merged from my point of view.

Good call — applied in 0e88557:

• Field renamed to Decluttarr commit hash (clearer ask)
• Dropped latest / dev from placeholder and description with a one-liner explaining why those move too fast for repro
• Split the lookup paths into bullets: Docker users → short_commit_id in the settings banner; local Python users → git rev-parse --short HEAD

Ready to merge whenever.