MPL-2.0, readable comments and defensive crypto fixes in 0.0.5

.github/ISSUE_TEMPLATE/config.yml

@@ -3,6 +3,6 @@ contact_links:
   - name: Report a security vulnerability (private)
     url: https://github.com/AlexiAxAxA/OpenCrate/security/advisories/new
     about: Suspected vulnerabilities go through GitHub private vulnerability reporting, never through a public issue. See SECURITY.md.
-  - name: Website and commercial contact
+  - name: Project website
     url: https://closecrate.com/
-    about: Commercial licensing and anything business-sensitive goes privately to god@closecrate.com.
+    about: Open Crate core and the separate Close Crate service.

.github/ISSUE_TEMPLATE/licensing-enquiry.yml

@@ -1,42 +1,28 @@
 name: Licensing enquiry
-description: Ask about the Open Crate Community License or start a commercial licensing conversation.
+description: Ask about MPL-2.0, redistribution or contributions.
 title: "[Licensing] "
 labels: ["licensing"]
 body:
   - type: markdown
     attributes:
       value: |
-        This is the licensing issue category named in section 5 of the
-        [Open Crate Community License 1.0](https://github.com/AlexiAxAxA/OpenCrate/blob/main/LICENSE-OPENCRATE).
-        **Issues are public.** Do not post revenue figures, headcount, contracts,
-        customer names or anything else you consider business-sensitive. For a
-        private conversation write to god@closecrate.com instead, or leave a way
-        to reach you here and the maintainer will continue by e-mail.
+        Open Crate 0.0.4 uses
+        [MPL-2.0](https://github.com/AlexiAxAxA/OpenCrate/blob/main/LICENSE).
+        Commercial use does not require a separate agreement.
+        **Issues are public.** Keep private business details out of the issue.
         The [licensing guide](https://github.com/AlexiAxAxA/OpenCrate/blob/main/docs/licensing.md) answers the common
-        questions about the free thresholds.
+        questions about covered files and earlier releases.
   - type: dropdown
     id: kind
     attributes:
       label: What is this about?
       options:
-        - Question about whether my use is covered by the free grant
-        - Commercial license for a business at or above a threshold
+        - MPL-2.0 requirements for modified covered files
+        - Contributing code
         - Redistribution, OEM or embedding in a product for third parties
         - Other
     validations:
       required: true
-  - type: dropdown
-    id: eligibility
-    attributes:
-      label: Group size (self-assessed, no figures needed)
-      description: Both thresholds apply to the whole corporate group. Pick the bracket only.
-      options:
-        - Below both thresholds (under USD 1M revenue and under 25 people)
-        - At or above at least one threshold
-        - Not sure how to assess it
-        - Personal or academic non-commercial use
-    validations:
-      required: true
   - type: textarea
     id: use
     attributes:
@@ -48,7 +34,7 @@ body:
     id: contact
     attributes:
       label: Private contact
-      description: An e-mail address or a note such as "reach me through the profile on this account". Required for commercial conversations.
+      description: Optional contact if the question needs private follow-up.
     validations:
       required: false
   - type: checkboxes
@@ -58,5 +44,3 @@ body:
       options:
         - label: I have not included business-sensitive figures or documents in this public issue.
           required: true
-        - label: I understand that no price, discount or right is granted by opening this issue; terms are agreed in writing.
-          required: true

CONTRIBUTING.md

@@ -11,10 +11,10 @@ Do not update frozen vectors merely to make a failing test pass. A format change
 requires a documented compatibility decision. Add dependencies deliberately and
 review their licenses, advisories and effect on the no-I/O boundary.
 
-Only contribute code you have the right to license. Commercial
-licensing requires a contributor-rights policy before external code
-contributions are accepted. Until then, please open an issue for design feedback
-before sending code. No contributor agreement is implied by this document.
+Contribute only code you have the right to license under MPL-2.0.
+Explain the reason for a check or constraint in a short comment; keep change
+history in commits or design documents. Keep safety contracts and wire formulas
+close to the code they constrain.
 
 Formatting is not a repository-wide gate yet: inherited source has existing
 formatting differences. Keep edits focused; do not mix bulk reformatting with

Cargo.toml

@@ -8,10 +8,10 @@ members = ["crates/oc-crypto", "crates/oc-format", "crates/oc-protocol", "crates
 oc-crypto = { path = "crates/oc-crypto" }
 
 [workspace.package]
-version = "0.0.2"
+version = "0.0.5"
 edition = "2024"
 rust-version = "1.90"
-license-file = "LICENSE-OPENCRATE"
+license = "MPL-2.0"
 publish = true
 
 [workspace.lints.rust]