While handling #217, I'm going to add a work-around needed because we are on basex 10.6 (may 2023 https://github.com/BaseXdb/basex/releases/tag/10.6).

A more recent version of basex (12.1 https://github.com/BaseXdb/basex/releases/tag/12.1 release in December 2025) will allow us to remove the work-around, so I'm creating an issue to track this down & remove the work-around later.