Repository navigation
feat: add CLI-only output flags (COD-486) - #10
Conversation
🤖 Automated Review PanelReviewer A — GPT-5.6-terra (Codex)APPROVE — no concrete blockers after verifying the declaration contract, exact emitted-long-flag collision namespace, Reviewer B — Gemini 3 Flash (OpenRouter)APPROVE — verified goal alignment, presentation-only boundary, validation against parameters/companions/help, Rust 2024 keyword safety, byte-deterministic generation, and the README's direct- Review resolutionAn earlier Codex finding exposed a real mismatch: validation normalized an omitted repeatable |
Auto-Merge GateConfidence: 0.92 The PR implements COD-486's explicit CLI-only boolean presentation flags: generated Observed checks: GitHub CI Scope limits: no credentials, deployment, release, destructive behavior, or manual-review marker; COD-486 contains no remaining non-PR acceptance criterion. |
Summary
cli_output_flagsfor CLI-only boolean presentation controls.clap::ArgAction::SetTrueboolean fields while keeping them out of HTTP, MCP, andparameters_json()request projection.Verification
cargo build --all-targetscargo test --all-targets— 44 codegen tests, 14 Notes surface tests, and 6 security-scan tests passed.cargo test -p hydra-codegen --test codegencargo clippy --all-targets -- -D warningscargo fmt --all -- --check(cd examples/notes && cargo run -p hydra-codegen --bin hydra-codegen -- check)git diff --check origin/mainScope boundary
No Iris runtime/replay behavior, HTTP/MCP input change, publication, tag, or release is included.
Linear: COD-486