[shivros]

Summary

• Reconcile the Releases & versioning section with the published Hydra v0.3.0 release.
• Record the signed annotated tag object and exact peeled release target.
• Preserve the exact feat: add CLI-only output flags (COD-486) #10–test: gate TypeScript fixture freshness in CI #18 provenance, explain the role of chore: prepare Hydra v0.3.0 release metadata #19/COD-523, retain v0.2.2 history, and keep consumer repin/publication boundaries explicit.

Scope

• README-only documentation change.
• No tag, release, dependency, generated artifact, consumer repin, deployment, crates.io/npm publication, or MCP-over-HTTP runtime change.

Verification

• Live release read-back: v0.3.0 release https://github.com/TechGodHQ/hydra/releases/tag/v0.3.0, non-draft/non-prerelease.
• Signed tag object: a663045a704ca500d3f2b0ea471906dd42ae8674, valid signature.
• Peeled target: 4b518b76ea9f731d75ae3e53f536f669dd493791.
• git diff --check
• creed diff
• cargo build --all-targets
• cargo test --all-targets (60 codegen, 14 Notes, 6 Security Scan tests)
• cargo clippy --all-targets -- -D warnings
• cargo fmt --all -- --check
• cargo run --locked -p hydra-codegen --bin hydra-codegen -- check in examples/notes, examples/security-scan, and examples/ts-client
• examples/ts-client: npm ci --ignore-scripts --no-audit --no-fund, npm run check:generated, npm run typecheck, npm run build, npm run test:nested-schema
• Two hydra-codegen write passes followed by check; generated output remained current and the working tree contains only README.md.

Review panel

• Reviewer A (Codex): APPROVE — no correctness or consumer-boundary findings.
• Reviewer B (Gemini 3 Flash): APPROVE — no correctness or convention findings.

Closes COD-533.

[shivros]

🤖 Automated Review Panel

Reviewer A — Codex

APPROVE

• The change is README-only and stays within Releases & versioning.
• The live v0.3.0 URL, signed annotated tag object a663045a704ca500d3f2b0ea471906dd42ae8674, and peeled target 4b518b76ea9f731d75ae3e53f536f669dd493791 are correct.
• Exact feat: add CLI-only output flags (COD-486) #10–test: gate TypeScript fixture freshness in CI #18 provenance, chore: prepare Hydra v0.3.0 release metadata #19/COD-523 preparation role, v0.2.2 history, migration guidance, and consumer authorization boundaries are preserved.
• No correctness, release-documentation, consumer-boundary, or convention violations found.

Reviewer B — Gemini 3 Flash

APPROVE

• v0.3.0 is correctly presented as published, with the tag object and peeled commit recorded.
• The exact feat: add CLI-only output flags (COD-486) #10–test: gate TypeScript fixture freshness in CI #18 provenance is retained and chore: prepare Hydra v0.3.0 release metadata #19/COD-523 is correctly identified as preparation metadata at the published target.
• v0.2.2 history and exact target remain discoverable; migration, numeric-precision, and opaque-result guidance is preserved.
• The README maintains the distinction between Hydra publication and separately authorized consumer repins/publication/deployment, and does not claim crates.io/npm or MCP-over-HTTP runtime delivery.
• No correctness or convention findings.

[shivros]

Auto-Merge Gate

Confidence: 0.96

This README-only correction directly satisfies COD-533: it replaces stale “unpublished” v0.3.0 language with the published release, signed tag object, exact peeled target, preserved provenance, and explicit downstream consumer-authorization boundary.

Observed checks: Test and Creed context drift completed successfully. The PR is open, non-draft, MERGEABLE, and CLEAN. Linear COD-533 is in review and contains no manual-review or do-not-merge marker. The existing two-model review panel approved the change with no findings.

Scope limit: README.md only; no release, tag, consumer repin, deployment, generated artifact, credential, or runtime change.