Add logging section

omvll/introduction/getting-started/index.md

@@ -234,6 +234,31 @@ OMVLL_PYTHONPATH: "<mirror of $OMVLL_PYTHONPATH>"
 OMVLL_CONFIG:     "<mirror of $OMVLL_CONFIG>"
 ```
 
+## Logging
+
+During compilation, O-MVLL produces log files to help you inspect what was configured and which passes were applied.
+By default, these logs are written into a folder named `omvll-logs` where your compiler has been invoked.
+
+If `output_folder` is set, the logs folder is created at:
+
+```bash
+<output_folder>/omvll-logs
+```
+
+Inside `omvll-logs`, you will find:
+
+**omvll-init.log**
+Contains the full initialization and setup logs for the tool. This is the first place to look if you want to verify configuration, or general startup behavior.
+
+**omvll-module-logs/<architecture>/<moduleName>.log**
+A per-module log with detailed information about the obfuscation pipeline. These files describe which passes were applied to each module and include more granular pass-level output.
+
+{{< alert type="dark" icon="fa-regular fa-face-thinking" >}}
+Log files are generated per module, not per compilation unit.
+This means the number of log files may be lower than the number of compiled source files.
+We’ve particularly observed this behaviour in Xcode builds, where BATCH_MODE is enabled by default, causing multiple compilation units to be grouped into fewer modules.
+{{</ alert >}}
+
 ## Android NDK (Linux and MacOS)
 
 The toolchain provided by the Android NDK is based on LLVM and **linked with `libc++`**.