Dashboard › cli › Distillation
51b382de-7fb4-49c1-b9d6-e60525e0ab55["lore_tm_v1_A9AZI8ebUmEG7KZTDE-bKf0mn8RLDdStFpm9JBWZ5v4"]
packages/cli/test/lib/scanner-flags.integration.test.ts for review; its integration harness imports run from @stricli/core, uses useTestConfigDir, creates an isolated temporary working directory with mkdtempSync(join(tmpdir(), "scanner-flags-cwd-")), and captures both stdout and stderr through mocked process/context streams.context.process.stderr, noting that these errors do not write to context.stderr.NO_COMMAND_REGISTERED = "No command registered".agent-conversation view target and a supplied blank target; the latter is expected to be a validation error.--verbose before a command, a value flag between a group and subcommand, and handling of a value flag when followed by --help.--release '1.0.0'.cli route map has a defaults leaf, allowing default-command routing to be tested without side effects.--version integration coverage includes: top-level --version, --version at deeper route levels, a value flag missing its value not swallowing --version, and --version after a -- escape remaining available to the wrapped command.command --help --json emitting command metadata as JSON, --json --help being order-insensitive, --fields narrowing JSON help output, and bare --help without --json continuing to render textual usage.issue has a default command, so an unknown token such as nope is forwarded to that default command rather than necessarily being rejected during route selection.