Broot still running in background (looking for reproduction)

Sometimes broot still runs in the background and burns my computer.

Maybe because I ran broot start at $HOME path, and there were too many files need to be scanned, and `Ctrl+Q` hadn't broken all tasks?

Start by reproducing the report with `broot start` from `$HOME`, allowing the scan to run, then pressing `Ctrl+Q`; observe whether any broot process or work remains and consumes resources. The issue is done when the reproduction is understood and the relevant background work reliably stops or has a documented, testable fix.

Written by the indexing model from the issue text.