I'm not clear on what the JobLauncher provides that would address the needs that the jobRegistry here does.  The jobRegistry here is purely to keep track, across child applicationContexts, what jobs are running so that they are available to be stopped via the stop.  Am I missing something?