Currently, plugin-path-utils is not included in core-plugins. Is this intentional?
If so, I will add the information to the docs for the hem, join, offset, and sa macros, and I will add plugin-path-utils to the list of plugins loaded by the <Example> component to allow the macros to work in the dev docs examples.
However, if this is a mistake and plugin-path-utils actually should be in core-plugins, I’ll work on making the changes to core-plugins.
Yes, this was intentionally and discussed with Joost, he wanted to keep it out of the core plugins at least for some time until it is matured enough or something like that.
I feel like core-plugins is the natural home for a plugin like path-utils.
As Jonathan points out, I advocated for an incubation period before landing the changes in core. Note that I hold Jonathan and his contributions in the highest regard, but I’ve been burned before by prioritizing being kind/welcoming to contributors over moving cautiously.
So sometimes I will press the pause button, and the closer one gets to core, the higher the chance that will happen.
That being said, I think the time has come to move forward with this. So I propose that I’ll prepare a v4.1 release this weekend that will bring path-utils into core(-plugins).
That is assuming that @jonathan_haas is onboard with such a plan.
If so, we will already do so in the develop branch so that @Benjamin_F is not blocked from doing that oh so valuable documentation work 
I actually think that moving that plug-in to the core-plugins at this point is probably not a good idea as no design at the moment uses it.
The designs like Sabrina, Paul and others that use these macros and that I have in the pipeline are not fully ready. (Sabrina sort of is, but I still want to go over the documentation and provide some more photos.)
So I would wait with that until some designs actually use it, or until at least someone has reviewed the code properly and maybe tried to port their own design to the new macros.
That said, there should be no danger adding the design to the core-plugins. It’s just that nothing substantially has changed since we said we would wait.
My bad, I somehow had it in my head that it was already used.
@Benjamin_F let’s go and at it to the example design as you suggested