This looks genuinely useful, thanks for building it and opening it up.
The "XO config is locked in its own database" pain is real, I've watched people rebuild remotes and backup jobs by hand after a reinstall and it's a slog.
Treating the backup surface as declarative YAML with drift detection that drops into CI is a clever angle. I'm curious how it talks to XO underneath, is it going through the JSON-RPC API? There's also the Terraform provider for XO (https://github.com/vatesfr/terraform-provider-xenorchestra), but that leans toward infra provisioning rather than backup config, so this seems to fill a different gap.
I'd like to try it against a test XO out of my own curiosity when I get a moment.
Really nice work, and folks running bigger XO fleets here will have sharper feedback than I can give.
