fix: recover GHCR publishing and organize badges

[CoreyLeath-code]

Summary

Cleans up the recruiter-facing badge block and fixes the GHCR publishing path.

README

• groups release metadata, CI/security, and stack badges into separate centered rows
• removes the GHCR badge while GitHub still reports no published package, so the README does not advertise an artifact that is not present

GHCR publishing

• fixes the tagged release workflow to publish to the lowercase image path ghcr.io/coreyleath-code/helixagent
• adds a manual recovery workflow for an already-published GitHub Release such as v1.1.0; it verifies the annotated tag and package version before building and pushing 1.1.0, v1.1.0, and latest

After this PR is merged, the recovery workflow can be dispatched for v1.1.0. Once the package is visible in GitHub Packages, the GHCR badge can be added back truthfully.

[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: 49 minutes

Limit details: You’ve used the included review currently available.

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?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 341b20a2-769a-44ca-b3eb-ed2158b9650e

📥 Commits

Reviewing files that changed from the base of the PR and between dd18b5c and 60a19a5.

📒 Files selected for processing (3)

• .github/workflows/publish-existing-container.yml
• .github/workflows/release.yml
• README.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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 60a19a58bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid moving latest during recovery of an older release

When this workflow is dispatched for any older release—especially after the fixed v1.1.0 default becomes stale—it unconditionally overwrites latest with that older image. Clients tracking latest would then be silently downgraded even though a newer release still exists. Either publish only version-specific recovery tags or verify that the requested tag is the repository's newest release before updating latest.

Useful? React with 👍 / 👎.