OBSERVED 2026-08-22 21:11:19, on the shipped v0.220.2, while creating the hold for Part 3.

The double-failure message ends:

    "... Vedd fel velünk a kapcsolatot — a korábbi állapot mentése megvan:
     pre-restore-20260822T211114Z-docmost-postgres.sql"

"a korábbi állapot mentése megvan" = "the backup of the previous state EXISTS".

IN THIS CASE IT DOES NOT. The rollback failed precisely BECAUSE that file was gone:

    ROLLBACK ALSO FAILED (a visszavonáshoz szükséges mentés nem található
    (pre-restore-20260822T211114Z-docmost-postgres.sql): stat ...: no such file or directory)

So the customer is told, in the same sentence, that we could not restore their previous state AND
that a copy of it exists — naming a file that does not. The sentence is built from `safety`, the path
writeSafetyDump returned, without asking whether it is still there.

This is the SAME CLASS as R-361 itself: a sentence asserting a property the code does not check.
It is not the trigger's artefact — ANY rollback failure whose cause is a missing or unreadable undo
copy produces it, and that is one of the two ways a rollback can fail.

NOT ACTED ON in this session's Part 1/2 scope. Filed as a register row.
