What happened?
fixmap verify --help documents --output <file>, and parseArgs accepts it, but runVerify always writes to stdout and never reads options.output. The flag is silently ignored — no file is created, exit code 0.
npx -y @aryam/fixmap@0.7.4 verify --report plan.json --diff HEAD~1...HEAD \
--format json --output verify.json
# prints JSON to stdout; verify.json is not created
plan correctly honors --output (packages/cli/src/cli-runner.ts ~194). runVerify (~452) only calls io.stdout(...).
How can we reproduce it?
Commands above; confirm verify.json missing while stdout has the payload.
What did you expect instead?
Write the verification result to --output (same as plan), or reject --output on verify with a clear error until implemented. Silent ignore is the failure mode.
FixMap version or commit
v0.7.4
Where did this happen?
CLI
What happened?
fixmap verify --helpdocuments--output <file>, andparseArgsaccepts it, butrunVerifyalways writes to stdout and never readsoptions.output. The flag is silently ignored — no file is created, exit code 0.npx -y @aryam/fixmap@0.7.4 verify --report plan.json --diff HEAD~1...HEAD \ --format json --output verify.json # prints JSON to stdout; verify.json is not createdplancorrectly honors--output(packages/cli/src/cli-runner.ts~194).runVerify(~452) only callsio.stdout(...).How can we reproduce it?
Commands above; confirm
verify.jsonmissing while stdout has the payload.What did you expect instead?
Write the verification result to
--output(same as plan), or reject--outputon verify with a clear error until implemented. Silent ignore is the failure mode.FixMap version or commit
v0.7.4
Where did this happen?
CLI