Merge branch 'main' into improve-doc-gen

Author: chrislyons-dev

THIRD_PARTY_LICENSES.md

@@ -77,3 +77,4 @@ This script:
 ---
 
 **Last generated**: 2026-03-07
+

docs/architecture/README.md

@@ -1,6 +1,7 @@
 # <img src="../images/archlette-stainedglassA-light.png" alt="" height="28" width="28" style="vertical-align:middle"> flarelette-jwt-kit
 
 **Architecture Documentation**
+
 Generated 2026-03-06 18:21:58
 
 ## Overview

docs/user-guide/core-concepts.md

@@ -19,6 +19,7 @@ Algorithm selection comes from one of two configuration sources:
 
 In practice: your deployment chooses the source (env or config object), and that source determines which algorithm is used.
 
+
 ### HS512 (Symmetric)
 
 **HMAC-SHA-512** with 64-byte shared secrets.
@@ -36,6 +37,7 @@ In practice: your deployment chooses the source (env or config object), and that
 - Fast signing and verification
 - Secret rotation requires coordinated rollout across producers and consumers
 
+
 **Environment detection:**
 
 ```bash
@@ -128,6 +130,7 @@ JWT_JWKS_CACHE_TTL_SECONDS=300  # Optional: default 5 minutes
 
 The kit automatically detects which algorithm to use based on environment variables for HS512/EdDSA flows.
 
+
 **Detection logic:**
 
 ```
@@ -142,8 +145,6 @@ Consumer (verification):
 
 **Note:** Asymmetric mode supports EdDSA (Ed25519), ECDSA (ES256/ES384/ES512), and RSA (RS256/384/512) verification. The actual algorithm is auto-detected from the JWK structure or token header.
 
-**Important:** ES512 signing is explicit-API driven, not env auto-detected.
-
 **Verification in code:**
 
 **TypeScript:**