moved pads don't keep, offer a new deletion token

[dcht00]

Noticed when moving a pad, I suppose this is not expected behavior.

Also, personally I'd be happy to be able to turn off the deletion token popup :)

[JohnMcLear]

Please provide steps to replicate.

[n-bux]

Also, personally I'd be happy to be able to turn off the deletion token popup :)

Compare my ticket #7996

[dcht00]

Please provide steps to replicate.

• start new pad "abc" (receive deletion token in popup)
• rename with api "movePad" call to "def"
• visit "def" pad and receive another deletion token in popup

[JohnMcLear]

Confirmed, thanks for the repro steps.

Cause: movePad is copy() + remove(), and Pad.copy() only copies the pad:<id>, :revs:N and :chat:N records — the pad:<id>:deletionToken record is never copied, and remove() then deletes the source one. So the renamed pad has no token: the one you saved validates against nothing, and since the copy keeps the same revision-0 author you're still the creator on arrival, so the server mints a fresh token and shows the modal again.

Fix in #8089 — the token now travels with the pad on a move, so your saved token keeps working and you don't get a second popup. (copyPad is left as-is: a copy is a separate pad, and two pads sharing one token secret would let a token saved for one delete the other.)

The "let me switch the token popup off entirely" part is tracked separately in #7996.