When pages are redirected, they are replaced in the listmaker

That is correct. They are replaced.

And if I Stop, it gets seemingly dropped, so I can't Start again on that file.

They're not removed fully till they're saved or skipped

What I'm saying is that if I Stop, the replacement entry (the redirected-to file) either vanishes or moves to a different position in the list.

So, if I Start again, I can't immediately re-process that particular file.

Try turning off the Keep alphabetized, and just sort with a right click when you want

OK, I will try that in my next run. I don't think that would resolve the issue, though, because I really don't expect the list to re-alphabetize upon stopping. Maybe that's the issue?

What would you an option called Keep alphabetized to actually do if not keep the list alphabetized?

Why would anyone want the list to re-alphabetize after a stop even if "Keep alphabetized" is checked? Let's look at this from a "use case" perspective.

'Stop' doesn't mean I'm doing anything with or to the list, which is what "Keep alphabetized" is about. It just means "Stop". Nobody expects the list to change when stopping.

https://en.wikipedia.org/wiki/Wikipedia:AutoWikiBrowser/User_manual#Start

"Stop — Stops the editing process. (Shortcut key — Esc)"

That's right.

And what that has to do with triggering any list events is beyond my understanding. "Keep alphabetized" is supposed to run on a list event trigger, logically speaking. Not a "Stop the editing process" trigger.

When would it run then?

Let's review.

"Follow Redirects" is checked in this scenario.

1. The run process gets to a redirect in the process, and replaces it with the page it redirects to and continues processing. "Keep alphabetized" is not run at this time.

2. The user clicks Stop. "Keep alphabetized" is run.

What's interesting is that #1 is a change to the list. #2 is not. That's inconsistent.

I would argue that "Keep alphabetized" shouldn't run in any of these cases because the user doesn't expect it.

So, to your question "When would it run then?"

It would run when a user expects it to run -- that is, when they are making a change that affects the list in some way. E.g., if the user adds entries to the list.

Stopping a run process is not the user making a change that affects the list.