Should the 'mwscript' helper script in the production and vagrant environments be replaced by a version that calls mwcmd.php specifically? Would prefer to do "mwcmd commonswiki refreshImageMetadata" rather than "mwscript mwcmd.php commonswiki refreshImageMetadata" ...
Topic on Talk:Requests for comment/Proper command-line runner for maintenance tasks
My understanding is that mwscript is necessary because each script is its own entry point, but now we could have a single multiversion entry point that just wraps the new runner.
My understanding is that mwscript exists because WMF's setup needs to know which version's maintenance script to run. For example, mwscript eval.php --wiki=foowiki might run /srv/mediawiki-staging/php-1.32.0-wmf.19/maintenance/eval.php while mwscript eval.php --wiki=barwiki needs to run /srv/mediawiki-staging/php-1.32.0-wmf.20/maintenance/eval.php instead.
That won't go away with the changes proposed here, it just means that "mwcmd" or whatever has to decide between /srv/mediawiki-staging/php-1.32.0-wmf.19/maintenance.php and /srv/mediawiki-staging/php-1.32.0-wmf.20/maintenance.php instead.