chore: gap-fill 7 governance tools

[KooshaPari]

User description

Adds missing governance tools that earlier batch caps skipped. Files added: .gitattributes Taskfile.yml .github/workflows/cargo-semver-checks.yml

---

Note

Low Risk
Low risk governance/CI additions; only affects developer tooling and GitHub Actions execution when Cargo.toml changes.

Overview
Adds repo governance/tooling files: a new .gitattributes to normalize line endings and classify generated/binary files, a Taskfile.yml with common Rust workspace commands (build, test, lint, audit, ci), and a GitHub Action workflow to run cargo-semver-checks on PRs that modify Cargo.toml (plus manual dispatch).

^{Reviewed by Cursor Bugbot for commit 1e2f9e7. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Add repo task shortcuts, line-ending rules, and a semver check workflow

What Changed

• Added a common task file so contributors can run build, test, lint, format, audit, and CI checks with one command each
• Added repository rules for consistent line endings and file handling across Rust, shell, markdown, YAML, JSON, and binary files
• Added a GitHub check that runs semantic version checks automatically when Cargo.toml changes, with manual run support

Impact

✅ Fewer setup steps for local Rust checks
✅ Consistent file formatting across platforms
✅ Earlier detection of breaking dependency or version changes

🔄 Retrigger CodeAnt AI Review

Details

💡 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]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

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

[codeant-ai]

Suggestion: Cargo.lock is marked as binary, but lockfiles are plain text and are expected to be diffed and merged in PRs. Treating it as binary disables normal text diff/merge behavior, which can hide dependency changes and cause avoidable merge conflicts; classify it as text instead. [logic error]

Severity Level: Major ⚠️

- ⚠️ Dependency update PRs hide Cargo.lock textual changes.
- ⚠️ Git cannot auto-merge Cargo.lock on conflicts.
- ⚠️ Reviewers may miss important dependency version changes.

Steps of Reproduction ✅

1. In the repo root
`/tmp/pr-review/repo-clones/KooshaPari/helios-cli/1e2f9e755ed378f41dda0f4cbdf873bc411225ca`,
note there is a Rust manifest `Cargo.toml` (listed by `LS` at the root, alongside
`.gitattributes`).

2. Generate and commit a lockfile by running `cargo generate-lockfile` (which creates
`Cargo.lock` next to `Cargo.toml`), then run `git add Cargo.lock`.

3. Because `.gitattributes` line 10 (`.gitattributes:10 Cargo.lock binary
linguist-generated=false`) marks `Cargo.lock` as `binary`, run `git diff --cached` and
observe that Git shows a binary diff summary (e.g., "Binary files differ") instead of a
normal line-based text diff for `Cargo.lock`.

4. Create a branch that also modifies dependencies (regenerating `Cargo.lock`), then merge
the branches; Git again treats `Cargo.lock` as binary due to `.gitattributes:10`,
preventing normal line-level merge and forcing manual conflict resolution without readable
textual context of dependency changes.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** .gitattributes
**Line:** 10:10
**Comment:**
	*Logic Error: `Cargo.lock` is marked as `binary`, but lockfiles are plain text and are expected to be diffed and merged in PRs. Treating it as binary disables normal text diff/merge behavior, which can hide dependency changes and cause avoidable merge conflicts; classify it as text instead.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 1e2f9e7. Configure here.}

[cursor]

Taskfile targets stub workspace instead of codex-rs

High Severity

The Taskfile.yml and cargo-semver-checks workflow run cargo commands from the repository root, targeting a stub Cargo.toml instead of the active workspace in codex-rs/. This means local build, test, lint, and audit tasks provide false confidence or fail, and semver checks in CI miss actual crate changes.

Additional Locations (1)

• .github/workflows/cargo-semver-checks.yml#L7-L10

 

^{Reviewed by Cursor Bugbot for commit 1e2f9e7. Configure here.}

[cursor]

Semver checks workflow targets stub root workspace

High Severity

The new cargo-semver-checks workflow runs without specifying working-directory or a manifest-path input, so cargo-semver-checks-action resolves the workspace at the repo root. That root workspace contains only the dummy helios stub package; the real Rust crates live under codex-rs/. The workflow therefore never validates semver compatibility for any of the actual codex-rs crates, even though the trigger fires on **/Cargo.toml changes (including those under codex-rs).

 

^{Reviewed by Cursor Bugbot for commit 1e2f9e7. Configure here.}

[cursor]

Contradictory Cargo.lock attributes hide PR diffs

Low Severity

The Cargo.lock binary linguist-generated=false rule combines two attributes that work against each other. The binary macro disables text diff/merge in git, while linguist-generated=false instructs GitHub to treat the file as non-generated and therefore not collapse it in PR views. The net effect is that Cargo.lock changes are surfaced in PRs as "Binary file changed" with no line-level content, which obstructs review of dependency updates and makes it harder to catch malicious or unintended cargo audit-relevant changes.

 

^{Reviewed by Cursor Bugbot for commit 1e2f9e7. Configure here.}