docs: replace ASCII art diagrams with Mermaid across all docs

- native-access: plugin pipeline flow
- auto-update: build → publish → app update flow
- ci-cd: release pipeline with parallel runners
- notification-windows: ToastContent model tree

Author: kdroidFilter

docs/auto-update.md

@@ -7,20 +7,21 @@ Nucleus provides a complete auto-update solution compatible with the [electron-b
 
 ## How It Works
 
-```
-Build & Publish          Check & Install
-┌─────────────┐         ┌─────────────────┐
-│ Gradle build │────────▶│ GitHub Release,  │
-│ + YML files  │         │ S3, or HTTP host │
-└─────────────┘         └────────┬────────┘
-                                 │
-                    ┌────────────▼────────────┐
-                    │ App fetches latest-*.yml │
-                    │ Compares versions        │
-                    │ Downloads new installer  │
-                    │ Verifies SHA-512         │
-                    │ Launches installer       │
-                    └─────────────────────────┘
+```mermaid
+flowchart LR
+    build["Gradle build\n+ YML files"] --> host["GitHub Release,\nS3, or HTTP host"]
+    host --> app["App at runtime"]
+
+    subgraph app ["App at runtime"]
+        direction TB
+        fetch["Fetch latest-*.yml"] --> compare["Compare versions"]
+        compare --> download["Download new installer"]
+        download --> verify["Verify SHA-512"]
+        verify --> launch["Launch installer"]
+    end
+
+    style build fill:#0f3460,stroke:#16213e,color:#e0e0e0
+    style host fill:#533483,stroke:#16213e,color:#e0e0e0
 ```
 
 !!! tip "Try it yourself"

docs/ci-cd.md

@@ -16,33 +16,26 @@ Nucleus provides reusable composite actions and ready-to-use GitHub Actions work
 
 A typical release pipeline has four stages:
 
-```
-Tag push (v1.0.0)
-       │
-       ▼
-┌──────────────────────────────────┐
-│  Build (6 parallel runners)      │
-│  Ubuntu amd64 / arm64            │
-│  Windows amd64 / arm64           │
-│  macOS arm64 / x64               │
-│  (macOS: + sandboxed .app ZIP)   │
-└──────────┬───────────────────────┘
-           │
-     ┌─────┴──────┐
-     ▼            ▼
-┌─────────────┐ ┌──────────┐
-│ macOS       │ │ Windows  │
-│ Universal   │ │ MSIX     │
-│ Binary      │ │ Bundle   │
-│ + Signing   │ └────┬─────┘
-│ + Notarize  │      │
-└──────┬──────┘      │
-       │             │
-       ▼             ▼
-┌──────────────────────────────────┐
-│  Publish — GitHub Release        │
-│  + Update YML metadata           │
-└──────────────────────────────────┘
+```mermaid
+flowchart TB
+    tag["Tag push (v1.0.0)"] --> build
+
+    subgraph build ["Build (6 parallel runners)"]
+        direction LR
+        ubuntu["Ubuntu\namd64 / arm64"]
+        windows["Windows\namd64 / arm64"]
+        macos["macOS\narm64 / x64"]
+    end
+
+    build --> macos_sign["macOS Universal Binary\n+ Signing + Notarize"]
+    build --> msix["Windows MSIX Bundle"]
+
+    macos_sign --> publish["Publish — GitHub Release\n+ Update YML metadata"]
+    msix --> publish
+
+    style tag fill:#e94560,stroke:#16213e,color:#e0e0e0
+    style build fill:#1a1a2e,stroke:#16213e,color:#e0e0e0
+    style publish fill:#0f3460,stroke:#16213e,color:#e0e0e0
 ```
 
 ## `setup-nucleus` Action

docs/native-access/index.md

@@ -9,19 +9,23 @@ Every now and then, no runtime library covers your exact native API need. Nucleu
 
 ## How It Works
 
+```mermaid
+flowchart TB
+    A["Your Kotlin/Native code"] --> B["Gradle plugin"]
+    B --> C["Your JVM code calls it like normal Kotlin"]
+
+    B@{ shape: rect }
+
+    style B fill:#0f3460,stroke:#16213e,color:#e0e0e0
 ```
-Your Kotlin/Native code
-        │
-        ▼
-  [ Gradle plugin ]
-        │  analyzes sources via Kotlin PSI
-        │  generates @CName bridge functions (native side)
-        │  generates FFM MethodHandle proxies (JVM side)
-        │  compiles → .so / .dylib / .dll
-        │  bundles into JAR under kne/native/{os}-{arch}/
-        ▼
-Your JVM code calls it like normal Kotlin
-```
+
+The plugin:
+
+1. Analyzes sources via **Kotlin PSI**
+2. Generates `@CName` bridge functions (native side)
+3. Generates FFM `MethodHandle` proxies (JVM side)
+4. Compiles to `.so` / `.dylib` / `.dll`
+5. Bundles into JAR under `kne/native/{os}-{arch}/`
 
 The generated JVM proxies have **the exact same API** as your native classes — same names, same types, same method signatures. No wrapper types, no casting, no boilerplate.
 

docs/runtime/notification-windows.md

@@ -96,30 +96,35 @@ Implement this interface to receive toast lifecycle events. All callbacks are di
 
 The `ToastContent` data class maps the full [toast XML schema](https://learn.microsoft.com/en-us/windows/apps/develop/notifications/app-notifications/toast-schema):
 
-```
-ToastContent
-├── visual: ToastVisual (required)
-│   └── binding: ToastBindingGeneric
-│       ├── children: List<ToastVisualChild>
-│       │   ├── AdaptiveText (up to 3 at top level)
-│       │   ├── AdaptiveImage (inline)
-│       │   ├── AdaptiveGroup (multi-column layout)
-│       │   └── AdaptiveProgressBar
-│       ├── appLogoOverride: ToastGenericAppLogo?
-│       ├── heroImage: ToastGenericHeroImage?
-│       └── attribution: ToastGenericAttributionText?
-├── actions: ToastActions?
-│   ├── inputs: List<ToastInput> (max 5)
-│   │   ├── ToastTextBox
-│   │   └── ToastSelectionBox
-│   ├── buttons: List<ToastButton> (max 5)
-│   └── contextMenuItems: List<ToastContextMenuItem>
-├── audio: ToastAudio?
-├── header: ToastHeader?
-├── launch: String
-├── activationType: ActivationType
-├── scenario: ToastScenario
-└── displayTimestamp: String?
+```mermaid
+graph TB
+    TC["ToastContent"] --> visual["visual: ToastVisual ⚠️ required"]
+    TC --> actions["actions: ToastActions?"]
+    TC --> audio["audio: ToastAudio?"]
+    TC --> header["header: ToastHeader?"]
+    TC --> props["launch / activationType\nscenario / displayTimestamp"]
+
+    visual --> binding["binding: ToastBindingGeneric"]
+    binding --> children["children: List&lt;ToastVisualChild&gt;"]
+    binding --> appLogo["appLogoOverride?"]
+    binding --> hero["heroImage?"]
+    binding --> attribution["attribution?"]
+
+    children --> text["AdaptiveText (max 3)"]
+    children --> image["AdaptiveImage"]
+    children --> group["AdaptiveGroup"]
+    children --> progress["AdaptiveProgressBar"]
+
+    actions --> inputs["inputs: List&lt;ToastInput&gt; (max 5)"]
+    actions --> buttons["buttons: List&lt;ToastButton&gt; (max 5)"]
+    actions --> ctx["contextMenuItems"]
+
+    inputs --> textbox["ToastTextBox"]
+    inputs --> selbox["ToastSelectionBox"]
+
+    style TC fill:#0f3460,stroke:#16213e,color:#e0e0e0
+    style visual fill:#533483,stroke:#16213e,color:#e0e0e0
+    style actions fill:#533483,stroke:#16213e,color:#e0e0e0
 ```
 
 ### Data Types