Harden evidence-driven semantic-tag releases

[CoreyLeath-code]

Summary

• Make semantic-version tags fail closed until the exact tagged commit passes Ruff, pytest, Docker/native-interop validation, CodeQL, secret scanning, and SBOM generation.
• Refuse tag-update events, lightweight tags, malformed semantic versions, version/tag mismatches, missing changelog sections, and existing GitHub Releases.
• Attach a tagged source archive, SHA-256 checksum, CycloneDX SBOM, and reproduction instructions.
• Preserve GHCR publication, but run it only after the GitHub Release succeeds.
• Document semantic-version policy and maintainer release steps without publishing a release.

Evidence boundary

Vector timing is not run on shared GitHub-hosted runners. The attached reproduction instructions provide the exact command for generating a host-specific JSON artifact, and release notes describe the C++ path only as optional native interoperability.

Validation

• Green on commit dd18e78f738f2f4bb98214905eb24bb5af347f91: Lint & Test Engine, Enterprise CI, Security & Supply Chain, and the new HelixAgent Release workflow.
• Release workflow: scoped Ruff gate, pytest, Docker build, optional C++ ctypes interop, CodeQL, secret scan, and CycloneDX SBOM all passed.
• On this pull-request event, release creation and GHCR publication were skipped by the tag-only guards.
• No tag, GitHub Release, container image, or benchmark result has been published by this change.

[coderabbitai]

Warning

Review limit reached

@CoreyLeath-code, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b698e6ed-6947-441c-bd77-c06a9fe7fb45

📥 Commits

Reviewing files that changed from the base of the PR and between cc4fa98 and dd18e78.

📒 Files selected for processing (5)

• .github/workflows/ci-cd.yml
• .github/workflows/release.yml
• CHANGELOG.md
• README.md
• docs/RELEASING.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.