commander 10.0.1: Option.implies() in Commander 10.0.1 accepts a string option name to set boolean flags without decomposing the string into numeric indices as in Commander 10.0.0

# Notes

- **Search answer:** `search_known_solution` returned existing sample `sha256:5c6d27a5983a0c5c7ab82d8867250554602d63b07860b3cdacd2dcd58f498252` ("Pass a string option name to Option.implies() to imply boolean options without string key decomposition").
- **How the wrong version fails:** In Commander 10.0.0, passing a string option name to `.implies('quiet')` fails silently with a green build in loose assertions because `Object.assign` treats the string as an array-like object (`{ '0': 'q', '1': 'u', '2': 'i', '3': 'e', '4': 't' }`), leaving `opts.quiet` undefined and polluting `opts` with numeric string index keys.

{"case":{"believed":"Passing a string option name to Option.implies() sets that option to true when the triggering option is parsed.","caseId":"case:sha256:dd859b17c9ecd9511d5daccf4846a5c9aba87919ca8d75cf30bd86b39e3ddf6a","contract":["Option.implies('quiet') on an option implicitly sets the boolean quiet option to true when the parent flag is present in Commander 10.0.1 instead of decomposing the string into numeric character properties as in 10.0.0","opts().quiet is strict equal to true","opts() does not contain string index keys ('0', '1', etc.)","omitting the triggering option leaves implied options undefined","direct --quiet flag sets quiet option independently"],"goal":"Option.implies() in Commander 10.0.1 accepts a string option name to set boolean flags without decomposing the string into numeric indices as in Commander 10.0.0","kind":"HOW","packages":["pkg:npm/commander@10.0.1"],"schemaVersion":1,"symbols":["Option.implies"]},"contractCommand":["node","test/contract.mjs"],"environment":{"arch":"x64","ecosystem":"npm","executionContext":"node","language":"node","os":"linux","packageManager":"npm","runtime":"node","schemaVersion":1},"license":"MIT-0","packages":["pkg:npm/commander@10.0.1"],"schemaVersion":1,"symbols":["Option.implies"],"verifierAdapter":"node-typescript@1"}

{
  "name": "csx-sample-commander-implies-fix",
  "version": "1.0.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "csx-sample-commander-implies-fix",
      "version": "1.0.0",
      "license": "MIT-0",
      "dependencies": {
        "commander": "10.0.1"
      }
    },
    "node_modules/commander": {
      "version": "10.0.1",
      "resolved": "https://registry.npmjs.org/commander/-/commander-10.0.1.tgz",
      "integrity": "sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==",
      "license": "MIT",
      "engines": {
        "node": ">=14"
      }
    }
  }
}

{
  "name": "csx-sample-commander-implies-fix",
  "version": "1.0.0",
  "private": true,
  "type": "module",
  "license": "MIT-0",
  "dependencies": {
    "commander": "10.0.1"
  }
}

import { Command, Option } from 'commander';

/**
 * Parses CLI arguments for a command with implied option relationships.
 *
 * In Commander 10.0.0, passing a string option name to `.implies('quiet')`
 * decomposed the string as an object into `{ '0': 'q', '1': 'u', ... }` and left
 * `opts.quiet` undefined. Commander 10.0.1 (patch release fixing PR #1854)
 * handles string arguments directly as `{ quiet: true }`.
 *
 * @param {string[]} argv - CLI flags/arguments passed by user
 * @returns {Record<string, any>} Parsed options object
 */
export function parseOptions(argv) {
  const program = new Command();
  program
    .name('demo')
    .addOption(new Option('-s, --silent', 'suppress output').implies('quiet'))
    .option('-q, --quiet', 'quiet mode')
    .exitOverride();

  program.parse(argv, { from: 'user' });
  return program.opts();
}

import { strict as assert } from 'node:assert';
import { parseOptions } from '../src/index.mjs';

// 1. Asserting string option name to Option.implies() sets target boolean option to true in Commander 10.0.1
const silentOpts = parseOptions(['--silent']);
assert.equal(silentOpts.silent, true);
assert.equal(silentOpts.quiet, true);

// 2. Asserting options dictionary is not polluted with decomposed numeric index keys ('0', '1', etc.)
assert.equal(silentOpts['0'], undefined);
assert.equal(silentOpts['1'], undefined);
assert.deepEqual(silentOpts, { silent: true, quiet: true });

// 3. Asserting target options remain undefined when triggering flag is omitted
const defaultOpts = parseOptions([]);
assert.equal(defaultOpts.silent, undefined);
assert.equal(defaultOpts.quiet, undefined);
assert.deepEqual(defaultOpts, {});

// 4. Asserting direct target flag still functions independently
const quietOpts = parseOptions(['--quiet']);
assert.equal(quietOpts.silent, undefined);
assert.equal(quietOpts.quiet, true);
assert.deepEqual(quietOpts, { quiet: true });

console.log('CONTRACT PASS: Option.implies() string argument implies boolean option in Commander 10.0.1 without string key decomposition');