`--latest` option triggers network request even for `--help` and `--version` commands

Start in src/eoc.js:115-119 and inspect the existing preAction hook around line 159, then trace how program.opts().parser is consumed and how help/version bypass command hooks. Move latest-version resolution out of module loading so those commands make no network request, and verify failures occur only for commands that build.

What happens

--latest fetches from Maven Central while src/eoc.js is still being loaded, before commander has looked at the command line. So eoc --latest --help and eoc --latest --version both block on a network request, and fail with a network error when there is none.

src/eoc.js:115-119:

let parser = fs.readFileSync(path.join(__dirname, '../eo-version.txt'), 'utf8').trim();
if (process.argv.includes('--latest')) {
  parser = require('./parser-version').get();

This is module scope, not a command action. It runs on import, so it runs for every invocation whose argv contains --latest, whatever the rest of the line says — including the two that produce no build at all.

The request is synchronous. parser-version.get() uses sync-request with timeout: 100000, socketTimeout: 100000, so an unreachable or slow repository stalls the process for up to a hundred seconds with nothing printed, since the console.info naming the version comes after the call returns.

Offline, it does not stall, it fails. get() throws on any non-200, and a failure to connect propagates out of a module-level statement, which means the process dies before commander is reached and before program.parseAsync could have turned it into the message on src/eoc.js:459-461. Asking eoc --latest --help what the flags are is not a request that should need the network at all.

process.argv.includes('--latest') is doing option parsing by hand, in a file that has commander configured a few lines below. It also matches the string anywhere on the line, so an object argument that happens to be --latest triggers the fetch too.

Suggested fix

Resolve the version where it is needed rather than where the module loads. The value is only consumed through program.opts().parser, so a preAction hook — the file already has one on src/eoc.js:159 for --dir — is the natural place:

program.hook('preAction', (command) => {
  if (command.opts().latest) {
    command.setOptionValue('parser', require('./parser-version').get());
  }
});

--help and --version never reach a hook, so both stop touching the network, and a failure to reach Maven Central becomes an error from a command that was actually asked to build something.

Worth reconsidering sync-request at the same time. It is deprecated and it blocks the event loop for the whole timeout; the rest of the file is already async, and get() has exactly one caller.