wip: capture wip/2026-08-02-helios-cli-m7 (audit 2026-07-24..08-02)

[KooshaPari]

User description

Automated audit capture of local dirty state.

• Branch: wip/2026-08-02-helios-cli-m7
• Captured and pushed during the cross-drive audit sessions (2026-07-24 to 2026-08-02).
• Working tree changes preserved; no destructive operations.

---

CodeAnt-AI Description

Enforce CI quality gates and document the actual release security posture

What Changed

• Formatting, linting, tests, dependency checks, and security scans now fail CI instead of being reported as advisory warnings.
• The CI summary correctly includes dependency review results, so failed checks block the final gate.
• Tagged releases now generate signed build provenance for published build artifacts.
• Security documentation now describes the implemented attestation flow, verification steps, coverage limits, and remaining SLSA work accurately.
• Updated contributor guidance for the dual-workspace layout, repository-relative paths, required checks, governance files, and fail-hard CI rules.
• Pull request guidance now requires linked requirements or specs, test results, risk and rollback details, and release checklist confirmation.

Impact

✅ Failed checks block merges
✅ Verifiable provenance for tagged release artifacts
✅ Clearer supply-chain security expectations

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Incremental review completed	ee6dc7b	Aug 05, 2026 · 08:05	08:06
✅ Reviewed your PR	8496c3d	Aug 03, 2026 · 01:01	01:04

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8496c3d205

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Grant attestation writes to the provenance job

When a rust-v*.*.* release reaches this new job, actions/attest-build-provenance will try to upload the signed provenance to GitHub's attestations API, but this job's explicit permissions block grants only id-token and contents. GitHub's attestation docs require attestations: write for provenance generation (see https://docs.github.com/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds), and the action docs state that permission is needed to persist the attestation, so the first release with this change will fail after publishing the release unless that permission is added.

Useful? React with 👍 / 👎.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud