Add elastic 2.0 license

[yuval-qf]

Summary by CodeRabbit

• Chores
  • Added a LICENSE.md file detailing the Elastic License 2.0 terms for the project.
  • Updated the license badge and link in the README to reflect the Elastic License.

[coderabbitai]

Walkthrough

A new file named LICENSE.md has been added to the repository. This file contains the complete text of the Elastic License 2.0, outlining the terms and conditions for using, distributing, and modifying the software. Additionally, the README.md license badge and link were updated from the MIT License to the Elastic License. No changes were made to code or exported entities.

Changes

File(s)	Change Summary
LICENSE.md	Added Elastic License 2.0 text as license file.
README.md	Updated license badge and link from MIT to Elastic License.

Poem

A license now rests in our code’s cozy den,
Elastic in spirit, with rules penned by men.
Use, share, and tinker—but do read with care,
For rabbits and coders, the terms are all there.
🐇📜

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Lite

📥 Commits

Reviewing files that changed from the base of the PR and between 5a6abdb and 7cef60a.

📒 Files selected for processing (1)

• README.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• README.md

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

LICENSE.md (1)

1-4: Prefer the canonical filename LICENSE (no extension) for better tooling support

Most packaging/publishing tools (e.g., GitHub’s license detection, Python’s setuptools, npm) only auto-detect and embed the license when the file is named exactly LICENSE or LICENSE.txt. Using LICENSE.md may cause the license to be missed in generated distributions or on the repository overview.

Action: Rename the file to LICENSE (or symlink/copy) and adjust any documentation links accordingly.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Lite

📥 Commits

Reviewing files that changed from the base of the PR and between 97a1f3d and 5a6abdb.

📒 Files selected for processing (1)

• LICENSE.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

LICENSE.md (1)

Learnt from: CR
PR: qualifire-dev/qualifire#0
File: .cursor/rules/self_improve.mdc:0-0
Timestamp: 2025-07-01T11:54:49.379Z
Learning: Document breaking changes

🔇 Additional comments (1)

LICENSE.md (1)

1-94: Sync package metadata with the new license

Now that the Elastic 2.0 license is in place, remember to update setup.py (or other manifest files) so the license= field reflects "Elastic-2.0" (or the SPDX identifier Elastic-2.0). Without this, downstream consumers and compliance scanners might assume an incorrect default.