--json does not always answer with a JSON document from impact:
axiomcode impact --json with no name prints the usage text instead of answering for the working tree's edits. impact with no name at the front door (and the MCP impact() with no name) answers your edits: …; the machine form gets nothing usable. Same in 0.1.8.axiomcode impact <a name nothing declares> --json prints the refusal as plain text, so stdout does not parse as JSON.
path, context, tests, changed and link answer --json with a document in every form (path and context refusals since #1912).
Found by the 0.1.9 cross-platform release check (5 soft checks per platform: "after edit: impact --json (no name) answers").
--jsondoes not always answer with a JSON document fromimpact:axiomcode impact --jsonwith no name prints the usage text instead of answering for the working tree's edits.impactwith no name at the front door (and the MCPimpact()with no name) answersyour edits: …; the machine form gets nothing usable. Same in 0.1.8.axiomcode impact <a name nothing declares> --jsonprints the refusal as plain text, so stdout does not parse as JSON.path,context,tests,changedandlinkanswer--jsonwith a document in every form (path and context refusals since #1912).Found by the 0.1.9 cross-platform release check (5 soft checks per platform: "after edit: impact --json (no name) answers").