chore: track rust crates in release please

[seven332]

Summary

• add crates/api-contracts to release-please config and manifest
• use api-contracts-rs as the Rust component name to avoid colliding with the TypeScript package
• add crates/sandbox-mock to release-please config and skip changelog for internal/helper crates

Verification

• jq empty release-please-config.json .release-please-manifest.json
• compared Rust workspace members from cargo metadata against release-please config and manifest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[seven332]

Code Review: PR #12249

Summary

Reviewed the release-please Rust crate tracking changes. The PR is config-only and adds missing Rust workspace members to release-please tracking.

Key Findings

Critical Issues (P0)

• None.

High Priority (P1)

• None.

Testing Review

Coverage

• chore: release-please config/manifest alignment -> no behavioral test required.
• Verified JSON syntax and checked Rust workspace members from cargo metadata against both release-please config and manifest.

Convention Compliance

• No test files changed. No testing convention violations.

Testing Verdict: Not Applicable

Bad Smell Analysis

• Mock violations: 0
• Test coverage issues: 0
• Defensive programming: 0
• Dynamic imports: 0
• Type safety issues: 0
• Hardcoded configuration issues: 0
• Lint/type suppressions: 0
• Timer/delay issues: 0

Recommendations

• No blocking recommendations. The api-contracts-rs component avoids collision with the TypeScript api-contracts package, and skip-changelog is appropriate for the generated/helper Rust crates.

Verdict

LGTM

---

Full review details: codereviews/20260509/
Testing standards: docs/testing.md