Skip to content

fix(cli): reject unsupported mutation output modes - #38

Draft
bdsqqq wants to merge 1 commit into
feat/api-parity-priorityfrom
feat/api-parity-output
Draft

bdsqqq wants to merge 1 commit into
feat/api-parity-priorityfrom
feat/api-parity-output

Conversation

@bdsqqq

@bdsqqq bdsqqq commented Sep 24, 2026

Copy link
Copy Markdown
Owner

changes

  • reject ignored explicit json/quiet/verbose mutation modes before credentials
  • cover generated singular commands and seven handwritten routers
  • preserve batch json/quiet and milestone create/update json; reject conflicting batch modes
  • preserve default acknowledgements, false flags and read precedence

evidence

1,118 offline tests, typechecks, artifact checks and build pass. independent review found no issues; 40 additional manual-router entrypoint probes made zero fetch attempts. inspected all45 registered schemas, including13 output-mode mutation procedures. e2e write invocations inspected for compatibility, not run locally.

remaining

full parity incomplete; shared transport evidence, per-coordinate coverage, auth/live verification, core confirmation and configured read-format semantics remain separate. stacked on #37; draft only.

Session-Id: 01a0c9ff-ccff-7106-aa80-086d00182476
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant