ExitHandler

The throwable itself, not a rendering: PatchHandle.lastError hands it out whole and only the status line shortens it.

The blueprint this handler answers for. Carried here rather than passed beside it: the two are one choice, and a separate parameter could disagree with the subclass.

A throwing callback is swallowed — the hook only observes, so the patched method must still run. Recording it is therefore the only thing that keeps a broken handler visible to Patches.handle. Two writes and no log line, deliberately: a handler on a hot method throws per call, and logging a stack that often costs more than whatever it was patched to watch.