docs: Reorganize n_analysis_workers documentation

Simplify the documentation structure:
- Move usage explanation to regular section text
- Add concise "Experimental" warning about potential removal/changes
- Keep "Signature analysis parallelization" note to clarify automatic
  parallelization is independent of this option

Author: aviatesk

docs/src/launching.md

@@ -153,27 +153,21 @@ require a server restart to take effect.
 
 Number of concurrent analysis worker tasks for running full analysis.
 
+The code loading phase must execute sequentially due to package environment and
+world age constraints. However, when multiple analysis units are open (e.g.,
+package source code and test code), increasing `n_analysis_workers` may reduce
+overall analysis time: while one unit is in the signature analysis phase,
+another can begin code loading concurrently.
+
+!!! warning "Experimental"
+    This option is experimental and may be removed or its semantics may be changed
+    substantially in future versions as the full analysis architecture evolves.
+
 !!! note "Signature analysis parallelization"
     The signature analysis phase is parallelized automatically using
     `Threads.@spawn` when Julia is started with multiple threads. This
-    parallelization is independent of `n_analysis_workers` and generally
-    provides significant speedups (e.g., ~4x faster with 4 threads for large
-    packages).
-
-!!! warning "Current limitations"
-    This option is experimental. JETLS currently runs all analysis within a
-    single server process. These "workers" are concurrent tasks, not separate
-    processes. Due to constraints around package environment switching and
-    world age management, the code loading phase of each analysis unit must
-    execute sequentially.
-
-    However, when multiple analysis units are open (e.g., package source code
-    and test code), increasing `n_analysis_workers` may reduce overall analysis
-    time: while one unit is in the signature analysis phase, another can begin
-    code loading concurrently.
-
-    The semantics of this option may change substantially in future versions as
-    the full analysis architecture evolves.
+    parallelization is independent of `n_analysis_workers` and provides
+    significant speedups (e.g., ~4x faster with 4 threads for large packages).
 
 ### [Client configuration](@id init-options/client-config)