chore:update LICENSE to AGPL

[RadCod3]

Resolves #41

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Project license updated from Apache 2.0 to GNU AGPL v3.

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

Walkthrough

The LICENSE file has been entirely replaced, switching from Apache License 2.0 to GNU Affero General Public License Version 3, introducing copyleft and network server obligations in place of the previous permissive licensing model.

Changes

Cohort / File(s)	Summary
License Text Replacement LICENSE	Apache 2.0 license text (201 lines) removed and replaced with AGPL-3.0 license text (661 lines), establishing copyleft protections with network interaction clauses

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Poem

🐰 Hop, hop! The license now runs free,
With copyleft chains, as bold can be—
No more permissive, now we share,
What networks build with open care!
AGPL keeps the source so bright, ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR only replaces the LICENSE file with AGPL-3.0 text but does not update pyproject.toml [#41] or README.md [#41] as required by the linked issue.	Add license field to pyproject.toml and update README.md with license badge and section as specified in issue #41.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore:update LICENSE to AGPL' clearly and concisely describes the main change: updating the LICENSE file to AGPL.
Description check	✅ Passed	The description 'Resolves #41' is related to the changeset, referencing the issue that motivated the license change.
Out of Scope Changes check	✅ Passed	All changes in the PR (LICENSE file replacement) are within scope of the requirements stated in issue #41.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @LICENSE:
- Around line 42-48: The license text change to AGPL v3 introduces
network-server obligations that differ from Apache 2.0; update all release
notes, the changelog entry, and any "upgrading" or "legal" documentation to
explicitly call out the breaking change: state that AGPL v3 requires operators
of networked services to provide source for modified versions to users, describe
the impact for SaaS/self-hosted deployments, and add a clear
migration/compatibility notice for maintainers of forks and downstream projects
(include links to the AGPL v3 terms and recommend seeking legal counsel).

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e0aa888 and d61a500.

📒 Files selected for processing (1)

• LICENSE

🔇 Additional comments (2)

LICENSE (2)

1-61: Verify PR completeness against stated objectives.

The LICENSE file content matches the official AGPL-3.0 text (Version 3, 19 November 2007). However, the PR objectives list four required changes:

1. Replace LICENSE file with AGPL-3.0 text — ✓ completed
2. Add license = {text = "AGPL-3.0-or-later"} to pyproject.toml — not provided
3. Update README.md with license badge and section — not provided
4. Update GitHub repository license setting — not applicable in PR files

Clarify whether the pyproject.toml and README.md updates are included in this PR or separate commits. If separate, ensure they're addressed before merge to avoid incomplete license migration.

---

620-661: Verify source file header updates are included.

The "How to Apply These Terms" section (lines 620–661) provides guidance for adding license notices to source files. Standard boilerplate should be added to each file to indicate AGPL licensing.

Confirm that all source files in the repository have been updated with appropriate AGPL license headers and copyright notices.