Summary
ov init --json writes human-readable log lines before the final JSON object, which makes --json mode unreliable for machine consumers.
Reproduction
Run:
Observed output begins with lines like:
Initializing overstory for "<repo>"...
...
Bootstrapping ecosystem tools...
...
and only then prints a JSON object on the last line.
Expected
When --json is passed, stdout should contain only valid JSON so callers can parse the command output directly without tail-line workarounds.
Why this matters
--json implies machine-readable output. Right now scripts have to special-case ov init by extracting the last line instead of parsing stdout as JSON.
Summary
ov init --jsonwrites human-readable log lines before the final JSON object, which makes--jsonmode unreliable for machine consumers.Reproduction
Run:
Observed output begins with lines like:
and only then prints a JSON object on the last line.
Expected
When
--jsonis passed, stdout should contain only valid JSON so callers can parse the command output directly without tail-line workarounds.Why this matters
--jsonimplies machine-readable output. Right now scripts have to special-caseov initby extracting the last line instead of parsing stdout as JSON.