chore(release): finalized v0.1.0

Author: Adel2411

CHANGELOG.md

@@ -1,31 +1,31 @@
 ## 0.1.0
 
-Initial release of M-Security — a native Rust cryptographic SDK for Flutter.
+Initial release of M-Security, a native Rust cryptographic SDK for Flutter.
 
 ### Authenticated Encryption (AEAD)
 
-- **AES-256-GCM** — Industry-standard authenticated encryption with 32-byte keys, 12-byte auto-generated nonces, and 16-byte authentication tags.
-- **ChaCha20-Poly1305** — High-performance alternative optimized for mobile processors lacking dedicated AES hardware.
+- **AES-256-GCM.** Industry-standard authenticated encryption with 32-byte keys, 12-byte auto-generated nonces, and 16-byte authentication tags.
+- **ChaCha20-Poly1305.** High-performance alternative optimized for mobile processors lacking dedicated AES hardware.
 - Unified `CipherHandle` interface for both ciphers (create, encrypt, decrypt, generate key).
 - Output format: `nonce || ciphertext || tag`.
 
 ### Hashing
 
-- **BLAKE3** — Ultra-fast integrity verification with one-shot and streaming APIs via `HasherHandle`.
-- **SHA-3-256 (Keccak)** — NIST-standard hashing with one-shot and streaming APIs.
-- **Argon2id** — PHC-winning password hashing with Mobile (64 MiB) and Desktop (256 MiB) presets, automatic salt generation, and PHC string output.
+- **BLAKE3.** Ultra-fast integrity verification with one-shot and streaming APIs via `HasherHandle`.
+- **SHA-3-256 (Keccak).** NIST-standard hashing with one-shot and streaming APIs.
+- **Argon2id.** PHC-winning password hashing with Mobile (64 MiB) and Desktop (256 MiB) presets, automatic salt generation, and PHC string output.
 
 ### Key Derivation (KDF)
 
-- **HKDF-SHA256** — RFC 5869-compliant key derivation with `derive`, `extract`, and `expand` operations. Output range: 1-8160 bytes.
+- **HKDF-SHA256.** RFC 5869-compliant key derivation with `derive`, `extract`, and `expand` operations. Output range: 1-8160 bytes.
 
 ### Security
 
-- All key material held in Rust behind opaque `#[frb(opaque)]` handles — raw keys never cross the FFI boundary.
+- All key material held in Rust behind opaque `#[frb(opaque)]` handles; raw keys never cross the FFI boundary.
 - Secure memory management with `ZeroizeOnDrop` on all key-holding structs.
-- `clippy::unwrap_used = "deny"` — no unwrap in FFI-visible code.
-- `panic = "abort"` in release profile — no undefined behavior from panics crossing FFI.
-- Nonces generated internally via `OsRng` — callers never handle nonces.
+- `clippy::unwrap_used = "deny"`, preventing unwrap in FFI-visible code.
+- `panic = "abort"` in release profile, preventing undefined behavior from panics crossing FFI.
+- Nonces generated internally via `OsRng`; callers never handle nonces.
 
 ### Platform Support
 

RELEASE_GUIDE.md

@@ -6,9 +6,9 @@ This document describes how to create a new release of M-Security after merging
 
 M-Security follows [Semantic Versioning](https://semver.org/) (SemVer):
 
-- **MAJOR** (`X.0.0`) — Breaking API changes (e.g., removing a function, changing a return type).
-- **MINOR** (`0.X.0`) — New features, backward-compatible (e.g., adding a new cipher or hash algorithm).
-- **PATCH** (`0.0.X`) — Bug fixes and patches, backward-compatible (e.g., fixing edge case in encryption).
+- **MAJOR** (`X.0.0`): Breaking API changes (e.g., removing a function, changing a return type).
+- **MINOR** (`0.X.0`): New features, backward-compatible (e.g., adding a new cipher or hash algorithm).
+- **PATCH** (`0.0.X`): Bug fixes and patches, backward-compatible (e.g., fixing edge case in encryption).
 
 For pre-release versions, append a suffix: `0.2.0-dev.1`, `1.0.0-beta.1`.
 
@@ -70,12 +70,12 @@ Move the `## Unreleased` section content under a new version header with the cur
 ```
 
 Follow [Keep a Changelog](https://keepachangelog.com/) format with these categories:
-- **Added** — New features
-- **Changed** — Changes to existing functionality
-- **Deprecated** — Features that will be removed in future versions
-- **Removed** — Removed features
-- **Fixed** — Bug fixes
-- **Security** — Vulnerability fixes
+- **Added**: New features
+- **Changed**: Changes to existing functionality
+- **Deprecated**: Features that will be removed in future versions
+- **Removed**: Removed features
+- **Fixed**: Bug fixes
+- **Security**: Vulnerability fixes
 
 ### 4. Run All Checks
 
@@ -147,15 +147,15 @@ Or via the GitHub web UI:
 > **First-time setup**: Ensure you are authenticated with `dart pub login` and that the package publisher is configured on pub.dev. See [Verified Publishers](https://dart.dev/tools/pub/verified-publishers).
 
 ```bash
-# Dry run first — review what will be published
+# Dry run first: review what will be published
 dart pub publish --dry-run
 
 # If everything looks good, publish
 dart pub publish
 ```
 
 **Important notes:**
-- Publishing is **permanent** — you cannot unpublish a version (only retract within 7 days).
+- Publishing is **permanent**. You cannot unpublish a version (only retract within 7 days).
 - Ensure `lib/src/rust/` generated files are included (they are needed by consumers).
 - The `.pubignore` or `.gitignore` controls which files are excluded from the published package.
 - Verify the package size is under 100 MB (gzip) / 256 MB (uncompressed).