[shivros]

Summary

• Repin Rite's only direct Hydra dependencies from v0.1.1 to the approved immutable v0.2.2 release.
• Lock hydra-core and hydra-codegen at afd8303da577898db06212d87e0fd1d4a32a4d3b.
• Regenerate all committed projections twice; the second generation is byte-identical and no generated artifact bytes changed.

Verification

• Verified public non-draft/non-prerelease release and signed annotated tag v0.2.2 (5ff3ffc… → afd8303…).
• cargo metadata --locked --format-version 1 resolves both Hydra packages to v0.2.2 at afd8303….
• cargo run --locked -p rite-codegen -- write twice; SHA-256 values for generated/cli.rs, generated/http.rs, and generated/mcp.json were identical.
• cargo run --locked -p rite-codegen -- check
• cargo build --locked --all-targets
• cargo test --locked --all-targets
• cargo clippy --locked --all-targets -- -D warnings
• cargo fmt --all -- --check
• cargo test --locked -p rite-server --lib
• cargo run --locked -p rite-cli -- list-handlers --config rite.example.toml
• cargo run --locked -p rite-cli -- get-handler nope --config rite.example.toml (expected nonzero JSON error)
• creed diff
• git diff --check

No operation, source/action behavior, generated contract, deployment, configuration, release, or live webhook behavior changed.

Linear: https://linear.app/codefold/issue/COD-479/rite-repin-to-the-approved-hydra-release-with-deterministic

[shivros]

🤖 Automated Review Panel

Reviewer A — GPT-5.6-terra

Verdict: APPROVE

The change is precisely scoped to the two explicit Hydra tag pins and their lockfile entries. Both crates resolve to v0.2.2 at the required immutable commit. The reviewer independently confirmed that generation inputs, api/operations.yaml, generator configuration, and all checked-in generated artifacts are unchanged, preserving shared dispatch, raw HTTP ingress, HMAC ordering, and router behavior.

Reviewer B — Gemini 3 Flash

Verdict: APPROVE

The release SHA matches the lockfile resolution; both direct declarations are correctly upgraded; generation is byte-identical across two writes; and no logic changes affect raw-request ingress or router behavior.

Panel disposition: APPROVE.

[shivros]

Auto-Merge Gate — approval rationale

Confidence: 0.96

COD-479 has a clear, bounded consumer-repin goal. This PR changes only Rite’s two direct Hydra tag pins and their corresponding lockfile resolutions, from v0.1.1 to the approved immutable v0.2.2 commit afd8303da577898db06212d87e0fd1d4a32a4d3b. The linked ticket’s required deterministic regeneration and generated-surface preservation evidence is recorded; the dual-model review panel approved the exact scope.

Checks observed: CI test and Creed context drift completed successfully. Pre-write metadata reports MERGEABLE / CLEAN.

Scope limits: no source/action behavior, public operation contract, deployment, release, configuration, credential, or live-webhook change.