Most importantly, in my opinion, these capabilities directly violate the concept of a "repository". Rather than allowing content modifications, it would be better to focus on updates through versioning, but allow the deprecated versions to remain permanently.

Further, updateContent/deleteContent introduce numerous technical issues. What happens if an artifact has derived artifacts? What happens if those derived artifacts have relationships pointing to them, or custom properties defined on them? I'd argue that automatically removing or updating those would violate the "impact analysis" use case and could directly result in numerous conflicts.