Does RenderUnsupportedPdfFeatures actually lift the client-side delete guard?

The server says every object on this form is Deletable either way (see /Unsupported), so the refusal lives in RAD PDF's client javascript and only the client can answer. This renders the viewer over a throwaway document and calls obj.deleteObject(false, true) — the exact call at admin.templateMapper.js:1439 — on every object on the page. Nothing is saved. Run it once each way and compare:

fresh import, flag = true (the catalog default)  |  fresh import, flag = false  |  faithful copy of the LIVE document 50045  |  clean up and stop

(nothing left over from a previous run)

pass ?uuid=<templateUUID> (or ?alias=<blob name>), plus &flag=true|false.