docs(cla): sign contributor license agreement

[RIVALHIDE]

Related Issue

Closes #586

Summary

Adding my signature to the Contributor License Agreement (CLA) to enable future contributions to the Cortex Linux project.

Signer Details:

• Name: [cortex]
• GitHub Username: [cortex]
• Email: [cortex@example.com]
• CLA Version: 1.0

AI Disclosure

• No AI used

Checklist

• PR title follows format: type(scope): description or [scope] description
• Tests pass (pytest tests/) - N/A for CLA signature
• MVP label added if closing MVP issue - N/A
• Update "Cortex -h" (if needed) - N/A

Summary by CodeRabbit

• Chores
  • Updated the automated contributor agreement verification process to improve bot handling in the CLA check system.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request adds "cortex@example.com" to the bot allowlist in the CLA check script. As a result, this email will be treated as a bot account and excluded from CLA verification requirements.

Changes

Cohort / File(s)	Summary
CLA Check Configuration \.github/scripts/cla_check.py	Added "cortex@example.com" to bot allowlist to exempt it from CLA verification

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• mikejmorgan-ai
• Anshgrover23

Poem

🐰 A cortex hops in with a signature bright,
Added to the allowlist, everything's right!
No CLA checks for this bot so divine,
One line of code—a perfectly simple design! ✨

🚥 Pre-merge checks | ❌ 5

❌ Failed checks (5 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions signing a CLA but actual changes add a bot email to an allowlist, which is unrelated to the stated CLA signature purpose.	Align the title with actual changes: either update to describe the bot allowlist modification or revert changes to match the CLA signature objective.
Description check	⚠️ Warning	The PR description claims to add a CLA signature with signer details, but the actual code change only adds a bot email to an allowlist, creating a significant mismatch between stated and actual changes.	Update the description to accurately reflect that the change adds cortex@example.com to a bot allowlist in cla_check.py, or modify code to actually implement the CLA signature as described.
Linked Issues check	⚠️ Warning	Issue #586 requires adding a CLA signature for cortex@example.com with signer details, but the PR only adds that email to a bot allowlist, failing to meet the stated requirements.	Implement the full CLA signature as specified in issue #586 including signer name, GitHub username, and signature metadata, rather than just adding to the bot allowlist.
Out of Scope Changes check	⚠️ Warning	The code change adds cortex@example.com to a bot allowlist in cla_check.py, which is unrelated to the stated objective of adding a CLA signature in issue #586.	Remove the bot allowlist modification unless explicitly required by the issue, or clarify in the PR description and issue why this change is necessary alongside the CLA signature.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c8564d and 0712631.

📒 Files selected for processing (1)

• .github/scripts/cla_check.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Test (Python 3.11)
• GitHub Check: Test (Python 3.12)
• GitHub Check: test (3.11)
• GitHub Check: test (3.12)
• GitHub Check: test (3.10)

---

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 and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @RIVALHIDE, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request formally records a new contributor's agreement to the Contributor License Agreement (CLA) for the Cortex Linux project. By adding their signature to the cla-signers.json file, the contributor "Cortex" is now authorized to make future contributions, ensuring legal clarity for their code submissions.

Highlights

• New CLA Signature: A new entry has been added to the cla-signers.json file, recording the signature of "Cortex" to the Contributor License Agreement.
• Contributor Details: The entry includes the name "Cortex", GitHub username "Cortex", email "cortex@example.com", and a signed date of "2026-01-13" for CLA Version 1.0.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[RIVALHIDE]

@Anshgrover23 Please Merge this CLA PR

[Anshgrover23]

@RIVALHIDE I think you need to add it in allowlist, no ?

[gemini-code-assist]

Code Review

This pull request adds a new signature to the Contributor License Agreement. However, the signature details appear to use placeholder information for the name, GitHub username, and email. This is a high-severity issue that needs to be corrected to ensure the CLA is valid. I've left a specific comment with details.

[RIVALHIDE]

@Anshgrover23 Can you tell me where is allowlist

[Anshgrover23]

@RIVALHIDE Sorry my bad, to ignore list I mean.

[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

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/scripts/cla_check.py (1)

338-351: Critical: This change bypasses CLA verification rather than signing the CLA.

The bot_patterns allowlist is intended for automated systems (dependabot, renovate, codecov, etc.) that are excluded from CLA requirements. Adding cortex@example.com here causes the CLA check to skip this email entirely (lines 358-366), rather than recording a legitimate CLA signature.

This PR is titled as a CLA signature but the actual effect is to circumvent the CLA enforcement mechanism. A human contributor should be added to .github/cla-signers.json instead, not to the bot allowlist.

This change should not be merged as it:

1. Undermines the legal protection the CLA provides
2. Allows contributions without the contributor actually agreeing to CLA terms
3. Misrepresents the intent of the change

To properly sign the CLA, the contributor's information should be added to the cla-signers.json file under the individuals array with their GitHub username and emails, not added to this bot bypass list.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c8564d and 0712631.

📒 Files selected for processing (1)

• .github/scripts/cla_check.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Test (Python 3.11)
• GitHub Check: Test (Python 3.12)
• GitHub Check: test (3.11)
• GitHub Check: test (3.12)
• GitHub Check: test (3.10)

[RIVALHIDE]

@Anshgrover23 I have added cortex@example.com in allowlist in cla_check.py can you merge this.

[Anshgrover23]

LGTM!