> ... can Processor actors use the stash they have?

I meanwhile have a [solution](https://github.com/eligosource/akka/commit/0bd66c0005aed040aa38f327cd90e31e68def296) implemented for that which will be part of the next pull request update. It

- uses a special-purpose processor-internal stash ( *processor stash* ) that is isolated from `theStash` maintained by `akka.actor.Stash` ( *user stash* ). I didn't implement 'named' stashes as mentioned before.
- unstashes all messages from the user stash on restart **excluding** messages of type `Replayed` and `Written` because they will be re-delivered by the journal (as `Replayed` messages). This is the proper way of avoiding duplicates during restart (mentioned in a previous comment). Checking sequence numbers to avoid duplicates doesn't work because `stash()`/`unstashAll()` re-orders the sequence.
- also supports cases where a processor is recovered (restarted) between `stash()` and `unstashAll()` calls. [Another commit](https://github.com/eligosource/akka/commit/40508ef1f563328742e2b7388cd9795128c14f1f) (that adds support for re-running recovery when recovery fails) also verifies that several recoveries (restarts) between `stash()` and `unstashAll()` calls are supported.