feat(licensing)!: adopt AGPL and commercial licensing

Publish Ragmir under AGPL-3.0-only from v3.0.0 onward, provide a separate commercial licensing path, ship complete license files in every npm tarball, and enforce the policy in validation. Releases before v3.0.0 keep their published license.

Author: jb-thery

.github/PULL_REQUEST_TEMPLATE.md

@@ -17,3 +17,8 @@
 
 - [ ] No secrets, private documents, `.env` files, or generated `.ragmir/` state are included.
 - [ ] Public documentation does not expose private project, customer, or validation details.
+
+## Licensing
+
+- [ ] I have the right to submit these changes under `AGPL-3.0-only`.
+- [ ] For code contributions, commercial relicensing rights have been confirmed with the maintainer.

AGENTS.md

@@ -4,7 +4,8 @@
 
 - Speak with users in French. Keep code, identifiers, comments, file names, and commit messages in English.
 - Keep the repository free of private documents, generated `.ragmir/` state, credentials, and environment files.
-- Ragmir is a fully open-source MIT project. Do not add activation, account, hosted-storage, native-shell, or cloud-vendor integrations.
+- Ragmir is open source under `AGPL-3.0-only`, with a separate commercial licensing option from JCode Works. Keep manifest, package, documentation, landing, and release metadata aligned with that policy. Do not add activation, account, hosted-storage, native-shell, or cloud-vendor integrations.
+- Do not merge an external code contribution unless the maintainer has confirmed the contributor grants the rights needed for both the AGPL and commercial licensing paths.
 - The repository is a pnpm workspace. Use the pinned Node version from `mise.toml`; Rust is not part of this project.
 - Start feature work from `develop` on `feature/*`, use pull requests into `develop`, and never publish or deploy without explicit confirmation.
 

CLAUDE.md

@@ -12,6 +12,9 @@ pnpm example
 Use `pnpm --filter @jcode.labs/ragmir <script>` for Core-only work. The pinned Node version lives in
 `mise.toml`; activate mise in your shell or run local workspace commands with that pinned version.
 Published packages require Node.js 22 or later, matching their manifests and release gate.
+Ragmir source is `AGPL-3.0-only` from v3.0.0 onward, with a separate commercial licensing option.
+Keep package metadata, license files, public documentation, and release notes aligned. External code
+contributions need confirmed rights for both licensing paths before merge.
 
 ## Workspace
 

COMMERCIAL-LICENSE.md

@@ -0,0 +1,36 @@
+# Commercial licensing
+
+Ragmir is available through two licensing paths.
+
+## Open-source path
+
+The source code is available under the
+[GNU Affero General Public License v3.0 only](https://github.com/jcode-works/jcode-ragmir/blob/main/LICENSE)
+(`AGPL-3.0-only`). This path allows use, modification, and redistribution under the terms of that
+license, including its source-availability requirements for modified software used over a network.
+
+## Commercial path
+
+A separate commercial agreement is available for organizations that want to integrate, modify,
+redistribute, or operate Ragmir as part of proprietary software or a hosted service without the
+AGPL obligations applying to that use.
+
+Contact JCode Works at [contact@jcode.works](mailto:contact@jcode.works) to discuss commercial
+terms. This document describes the availability of commercial licensing. It is not itself a grant
+of commercial rights. Those rights begin only under a separate signed agreement.
+
+## Version boundary
+
+Releases before `v3.0.0` remain available under the license published with those releases. Source
+code released from `v3.0.0` onward is `AGPL-3.0-only` unless an individual file states otherwise.
+
+## Contributions and third-party material
+
+Third-party dependencies, model files, and other separately identified material keep their own
+licenses. Code contributions require the rights described in
+[CONTRIBUTING.md](https://github.com/jcode-works/jcode-ragmir/blob/main/CONTRIBUTING.md) so the
+project can continue to offer both licensing paths.
+
+The AGPL license does not grant trademark rights in the Ragmir, JCode Labs, or JCode Works names or
+logos. Factual references to the project are welcome, but modified or commercial offerings must
+not imply endorsement.

CONTRIBUTING.md

@@ -1,6 +1,7 @@
 # Contributing
 
-Ragmir is an open-source MIT project. Issues and pull requests are welcome.
+Ragmir is an open-source `AGPL-3.0-only` project with a separate commercial licensing option.
+Issues and pull requests are welcome.
 
 Ragmir is maintained by a single developer ([Jean-Baptiste Thery](https://github.com/jb-thery)).
 Be kind, be specific, and keep the scope of each contribution focused so it can be reviewed
@@ -74,6 +75,17 @@ pnpm audit:security
   protected semantic-release workflow from `main`; versions come from Conventional Commits, not
   manual package bumps.
 
+## Contribution licensing
+
+By submitting a documentation, test, or code contribution, you confirm that you have the right to
+submit it under the project's [AGPL-3.0-only license](./LICENSE). Code contributions are accepted
+only after the maintainer also confirms the project has the rights needed to offer that
+contribution under separate commercial terms. The maintainer may request a separate written
+contributor agreement before merge.
+
+This policy preserves both licensing paths without taking copyright ownership away from the
+contributor. See [COMMERCIAL-LICENSE.md](./COMMERCIAL-LICENSE.md) for the public licensing boundary.
+
 ## Security
 
 Do not report vulnerabilities through public issues. Follow [`SECURITY.md`](./SECURITY.md).