ci: establish enterprise GitHub Actions automation baseline

[CoreyLeath-code]

Summary

Adds a minimal-maintenance automation baseline for CI, stack-aware testing, security scanning, CodeQL, dependency review, caching, coverage artifacts, and GitHub Actions Dependabot updates.

Existing project workflows and quality configuration were preserved. This PR is intentionally a baseline; stack-specific tests and release policy should be tightened where the repository has additional requirements.

Validation contract

• CI detects Python, Node.js, Go, Rust, Maven, and CMake projects.
• Security includes Gitleaks and Trivy SARIF.
• CodeQL is scheduled weekly and runs on pushes and pull requests.
• Dependency review blocks high-severity dependency changes.
• Dependabot updates GitHub Actions weekly.

[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.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 381342fc-8f99-47d2-931a-e24157680add

📥 Commits

Reviewing files that changed from the base of the PR and between 95dea88 and 636885f.

📒 Files selected for processing (3)

• .github/workflows/codeql.yml
• .github/workflows/dependency-review.yml
• .github/workflows/security.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ops/enterprise-automation-20260723

---

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.}