ABI Command not recognized at end of semicolon clause

Since a semicolon clause is parsed all at once, commands that were registered in earlier commands do not get parsed properly.

There are several ways to handle this, the simplest is probably parsing single commands then spitting out the remainder. Then execution can happen followed by more parsing.

Commands might even have a flag that denotes that they "dirty" the parser.

Trace the CLI's semicolon-clause parsing and command-registration flow, then reproduce a case where an earlier command registers an ABI command that appears later in the clause. The work is done when commands registered by earlier commands are recognized and parsed correctly before the remaining clause is executed.

Written by the indexing model from the issue text.