Nuking a writeup should just unpublish it

[jaybonci]

No description provided.

[jaybonci]

Due to a flaw in the way that the engine interprets the nuke instruction, there's no real way to trap it, so when writeup maintenance nuke tries to save a draft, it just ends up getting nuked anyway. The improved object model should account for this.

[JamesCrompton]

Under normal circumstances, writeups don't get nuked. The only place in the UI where this can be done there is a note that it is almost certainly the wrong thing to do. The option to do it was put there for things we really don't want in the database, even if they are invisible.

[jaybonci]

@JamesCrompton Understood. I know this isn't standard procedure, and it isn't a "problem". This note is more for when I refactor the E2 object model into real blessed objects so that the use case is recorded.