Yes, need you to flesh out

on-no-match="shallow-copy-all"

of

https://balisage.net/Proceedings/vol27/html/Kay01/BalisageVol27-Kay01.html#d1
0153e637

instead, the paper says

For arrays, it does

<xsl:apply-templates select="array:parcels(.)" mode="#current"/>

that is, it wraps each of the array members into a parcel and processes
each one separately.

For maps, it does:

<xsl:apply-templates select="map:entries()" mode="#current"/>

It actually does something akin to

<xsl:array>
   <xsl:apply-templates select="array:parcels(.)" mode="#current"/>
</xsl:array>

That one I can I understand and use with what is in Saxon 11 EE, I
think, if

or

<xsl:map>
   <xsl:apply-templates select="map:entries()" mode="#current"/>
</xsl:map>

For that I wonder how it avoid infinite recursion turning any map into
xsl:map processing the map contents as map entries turning them into
xsl:map processing the map contents as map entries turning them into
xsl:map...

These constructs take the solutions to my XML Prague 2016 use cases from

Yes, that seems amazing. Is that paper also implemented in e.g. a Saxon
12 branch?