feat: add JSON batch operation reference (COD-443) - #5
Conversation
🤖 Automated Review PanelGPT-5.6 (openai-codex/gpt-5.6-terra)APPROVE — the explicit generic batch contract generates aligned HTTP, CLI, and MCP surfaces. Fixture-backed tests cover HTTP/dispatch parity, CLI parse plus dispatch normalization, and MCP schema; reviewer additionally exercised real CLI and MCP batch calls successfully. No consumer-specific persistence/idempotency claims were introduced. Gemini 3 Flash (google/gemini-3-flash-preview)APPROVE — independently confirmed explicit JSON schema and CLI representation, deterministic generated artifacts, safe CLI JSON-object normalization, and consumer-owned idempotency/transaction semantics. No substantive correctness or goal-alignment issues found. |
Auto-Merge Gate — approval rationaleConfidence: 0.93 The PR fulfills COD-443's bounded Hydra objective: it demonstrates one explicit JSON batch contract projected through generated HTTP, CLI, and MCP surfaces, with a single consumer dispatch implementation. The diff keeps Iris-specific event models, hashing, idempotency, and persistence out of Hydra. Evidence
Scope limits |
Summary
Proves Hydra's existing explicit
jsonparameter capability can represent a source-agnostic ingest batch through one declared operation contract.ingest_batchreference operation inexamples/noteswith replay key, batch hash, a non-empty JSON event array, and explicit repeatable--eventCLI representation.Verification
cargo build --all-targetscargo test --all-targets(51 tests)cargo clippy --all-targets -- -D warningscargo fmt --all -- --checkcd examples/notes && cargo run -p hydra-codegen --bin hydra-codegen -- checkCloses COD-443.