Comments
If we want to have Bundles be the information package for Transactions where each entry within the bundle may be the subject of a different FHIR Operation then we should separate the Operation name from the 'status' element, make its type 'coding' to support easy extension to additional operations, use this consistently for all operations rather same named such as 'update' yet using other fields to imply an operation such as completing the deleted element to indicate perfoming a 'delete', and provide a flag field to indicate whether the operation halts on eooros only, errors and warnings or none.

Grahame's Comments
we could signifcantly increase the compleity of transactions like this, yes. We could turn them into a monster. Not that they already aren't. I am opposed to doing this just because we can see a way to make statements when we haven't counted the cost of doing them, nor do we have any use cases for doing so