A follow up question to this How are local edits of packaged Lighting flexi-pages handled when a package is updated?
Is there a way to "break" the current logic where a local flexi-page edit (that creates and uses a clone) always wins? The aim here is to have the option (accepting the risks) to force in a new flexi-page using e.g. sfdx.
