Dashboard › craft › Distillation
69b33861-0e85-4be2-bcdb-d730aa2df370["lore_tm_v1_0vZfekBhQ95ngNxznFwnVwT_PVQSWEdUD4P5Y738Z_Q","lore_tm_v1_R-jwXoxud7JTeteH75_xsosonPKNPlmH9I4e9GGFHBs"]
Date: Aug 24, 2026
2.29.0-dev.0, confirming Bugbot’s stale-gate finding.2.29.0.fixGlobalBooleanFlags’ manual argv scan with Node’s parser.src/utils/helpers.ts defines MAX_STEP_OUTPUT_BYTES = 64 * 1024.envToBool(envVar) lowercases String(envVar) and returns false for values in FALSY_ENV_VALUES: '', 'undefined', 'null', '0', 'false', and 'no'.extractWorkspaceSelection(argv, env = process.env) in src/utils/helpers.ts reads CRAFT_WORKSPACE; supports --workspace foo and --workspace=foo; a supplied CLI workspace value takes precedence over the environment value; bare/valueless --workspace, or --workspace= with an empty value, falls back to CRAFT_WORKSPACE; returns undefined when neither provides a value.extractWorkspaceSelection treats a following token as the --workspace value only when it exists and does not start with '-'; it intentionally leaves bare --workspace for yargs validation rather than consuming another option as its workspace name.GlobalFlags in src/utils/helpers.ts includes optional 'dry-run'?: boolean, 'no-input'?: boolean, and 'log-level'?: keyof typeof LogLevel; internal defaults in GLOBAL_FLAGS are 'dry-run': false, 'no-input': false, and 'log-level': 'Info'.