Update reactive analysis post with monorepo support and simplified instructions

- Add monorepo support bullet point under "For Developers"
- Rewrite "Try It Today" section with version requirements and simple editor workflow
- Add link to Dead Code Analysis documentation

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: cristianoc

markdown-pages/blog/reactive-analysis.mdx

@@ -63,6 +63,7 @@ The reactive analysis infrastructure is landing now. Here's what it enables:
 ### For Developers
 
 - **Editor integration** (coming soon): Dead code warnings that update as you type
+- **Monorepo support**: The analyzer now works correctly in monorepo setups, running from the workspace root with proper binary lookup
 - **Faster CI analysis**: Incremental runs are dramatically faster than full runs
 - **Immediate feedback loop**: See the impact of your changes instantly
 
@@ -87,20 +88,15 @@ The goal is an editor experience where the tooling _keeps up with you_—no wait
 
 ## Try It Today
 
-The reactive analyzer is available now in the development builds:
+**Requirements:**
 
-```bash
-# Clone and build
-git clone https://github.com/rescript-lang/rescript
-cd rescript
-make lib
+- ReScript compiler >= 12.1.0
+- VSCode or Cursor with rescript-vscode extension >= 1.74.0 (upcoming release)
 
-# Run with timing info
-cd your-project
-path/to/rescript-editor-analysis reanalyze -dce -config -reactive -timing
-```
+1. Start the build watcher (accept the prompt when opening a ReScript file, or run **"ReScript: Start Build"**)
+2. Run **"ReScript: Start Code Analyzer"**
 
-The `-timing` flag shows how much work the reactive system avoided on subsequent runs. You can also use `-runs N` to benchmark multiple iterations.
+Dead code warnings will appear in your editor and update automatically as you save files. For configuration options and usage details, see the [Dead Code Analysis guide](../docs/manual/editor-code-analysis.mdx).
 
 ## Acknowledgments