`object-has-data` XSL transformation is too slow on large XMIR files

I'm getting performance warnings when running lints against eo-runtime:

[WARNING] XSL transformation 'object-has-data' took 106ms, whereas threshold is 100ms

What happens: The selector //o[eo:has-data(.) and not(parent::o[@base='Φ.bytes'])] calls eo:has-data(.) on every <o> in the document. The function is normalize-space(string-join($o/text(), '')) != '', which materializes and concatenates all text node content for each element before any other predicate runs. On large XMIR files this is expensive.

What should happen: The transformation completes within the 100ms threshold. Placing the cheaper not(parent::o[@base='Φ.bytes']) predicate first would reduce the number of elements eo:has-data() is evaluated on.