Clarify non-copy-left licensing option for enterprises

[jviotti]

We came across some enterprises that are, by company policy, totally
prohibited from making use of AGPL software, even if in the case of a
CLI like this, should not trigger any copyleft requirements under normal
use.

This clarifies we are still able to cater to that audience if really
needed, as the contribution guide outlines.

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: Clarifies that organisations requiring a non-copyleft licence for internal use can contact Sourcemeta.
Changes: Adds a contact link to the README’s enterprise licensing note, complementing the existing AGPL usage guidance.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.markdown">

<violation number="1" location="README.markdown:302">
P3: The newly reworded sentence in the "A note for enterprises" callout ends with "further*" and is missing a terminating period before the closing emphasis marker. Every other sentence in this paragraph (and the previous version of this line, which ended "(mailto:hello@sourcemeta.com).*") ends with a period. Add a period so the sentence reads "...to discuss further."*"</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The newly reworded sentence in the "A note for enterprises" callout ends with "further*" and is missing a terminating period before the closing emphasis marker. Every other sentence in this paragraph (and the previous version of this line, which ended "(mailto:hello@sourcemeta.com).") ends with a period. Add a period so the sentence reads "...to discuss further.""

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.markdown, line 302:

<comment>The newly reworded sentence in the "A note for enterprises" callout ends with "further*" and is missing a terminating period before the closing emphasis marker. Every other sentence in this paragraph (and the previous version of this line, which ended "(mailto:hello@sourcemeta.com).*") ends with a period. Add a period so the sentence reads "...to discuss further."*"</comment>

<file context>
@@ -297,5 +297,6 @@ yours. This is the same way that managing your proprietary code with
-[hello@sourcemeta.com](mailto:hello@sourcemeta.com).*
+organisation, see our [licensing page](https://www.sourcemeta.com/licensing/)
+and reach out to [hello@sourcemeta.com](mailto:hello@sourcemeta.com) to discuss
+further*
</file context>

Suggested change

	further*
	further.*