Tootfinder

Ok, major major stupid flaw in #jellyfin and looks like the only solution is wipe clean the entire dB and reinstall … every time you make an outside change?!
And starting from scratch means copious mislabeled items. It will take me weeks to fix television shows. Admittedly I chose Jellyfin because it appeared to work well sharing legacy files and folders with Nextcloud, and I loved the big-screen apps. It was fun, until I noticed …
But I can't spend my life re-entering metadata, and the family just laughs at the brokenness.
How, no, why on earth would a competent programmer throw an uncaught exception and abort because a file to be deleted has already been removed, or simply renamed? What is the business case for such? Why make an archive write-only, no deletes, no renames, no moves?
Is there a less fragile alternative?