LOL, some of the comments in the source are gold.

https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/ABORT.ASM

Note:  We do need to explicitly close FCBs.  Reasons are as follows:  If we
; are running in the no-sharing no-network environment, we are simulating the
; 2.0 world and thus if the user doesn't close the file, that is his problem
; BUT...  the cache remains in a state with garbage that may be reused by the
; next process.  We scan the set and blast the ref counts of the FCBs we own.
;
; If sharing is loaded, then the following call to close process will
; correctly close all FCBs.  We will then need to walk the list AFTER here.
;
; Finally, the following call to NET_Abort will cause an EOP to be sent to all
; known network resources.  These resources are then responsible for cleaning
; up after this process.
;
; Sleazy, eh?~

You can put in a timeout command at the end, and then call the next .bat file.

For example “TIMEOUT /T 60” waits for 60 seconds before resuming, or you can override it by pressing any key.

So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.

Excellent, thanks!

Does anyone know of an active fork with sponsorblock?