docs: add light AI notes to manual

Add a small set of measured references to coding-agent and AI-assisted workflows in the manual pages where they fit naturally.

Keep the changes limited to overview, setup, migration, tooling, performance, and LLM documentation so the docs stay close to their existing tone.

Author: jderochervlk

markdown-pages/docs/manual/build-performance.mdx

@@ -70,6 +70,8 @@ ReScript doesn't take whole seconds to run every time. The bulk of the build per
 
 In short, thanks to our compiler and the build system's architecture, we're able to **only build what's needed**. If `MyFile.res` isn't changed, it isn't recompiled. Renaming or moving files is handled automatically, with no stale builds.
 
+That kind of tight, correct incremental feedback is especially useful in coding-agent workflows, where small edits need to be validated quickly.
+
 ## Speed Up Incremental Build
 
 ReScript uses the concept of interface files (`.resi`) (or, equivalently, [module signatures](./module.mdx#signatures)). Exposing only what you need naturally speeds up incremental builds. E.g. if you change a `.res` file whose corresponding `.resi` file doesn't expose the changed part, then you've reduced the amount of dependent files you have to rebuild.

markdown-pages/docs/manual/converting-from-js.mdx

@@ -87,6 +87,8 @@ Open an editor tab for `src/Main.res.js`. Do a command-line `diff -u src/main.js
 
 **Always make sure** that at each step, you keep the ReScript output `.res.js` file open to compare against the existing JavaScript file. Our compilation output is very close to your hand-written JavaScript; you can simply eye the difference to catch conversion bugs!
 
+This step-by-step workflow also pairs well with AI-assisted migrations: a tool can make a small change, and you can review the generated JS against the original file at each step.
+
 ## Step 3: Extract Parts into Idiomatic ReScript
 
 Let's turn the `defaultId` variable into a ReScript let-binding:

markdown-pages/docs/manual/editor-code-analysis.mdx

@@ -19,6 +19,8 @@ Dead code refers to code that's present in your codebase but is never executed.
 
 ReScript’s language design allows for accurate and efficient dead code analysis using the **ReScript Code Analyzer**, available via the official VSCode extension.
 
+This is useful not only for manual refactors, but also for AI-assisted edits where fast project-wide feedback helps catch incorrect assumptions early.
+
 ### Prerequisites
 
 - ReScript VSCode extension (v1.8.2 or higher)

markdown-pages/docs/manual/installation.mdx

@@ -68,6 +68,8 @@ That compiles your ReScript into JavaScript, then uses Node.js to run said JavaS
 
 **When taking your first steps with ReScript, we recommend you use our unique workflow of keeping a tab open for the generated JS file** (`.res.js`/`.res.mjs`), so that you can learn how ReScript transforms into JavaScript. Not many languages output clean JavaScript code you can inspect and learn from! With our [VS Code extension](https://marketplace.visualstudio.com/items?itemName=chenglou92.rescript-vscode), use the command "ReScript: Open the compiled JS file for this implementation file" to open the generated JS file for the currently active ReScript source file.
 
+That workflow is also handy when experimenting with coding agents, since both the source and generated JS stay easy to inspect.
+
 During development, instead of running `npm run res:build` each time to compile, use `npm run res:dev` to start a watcher that recompiles automatically after file changes.
 
 ## Integrate Into an Existing JS Project
@@ -172,6 +174,8 @@ bun create rescript-app
 
 Since ReScript compiles to clean readable JS files, the rest of your existing toolchain (e.g. Vite, Rspack, Rollup) should just work!
 
+That low setup overhead also makes it practical to try ReScript in fast-moving teams, including ones exploring AI-assisted workflows.
+
 Helpful guides:
 
 - [Converting from JS](./converting-from-js.mdx).

markdown-pages/docs/manual/introduction.mdx

@@ -42,10 +42,14 @@ A `Hello world` ReScript program generates **20 bytes** of JS code. Additionally
 
 ReScript's build time is **one or two orders of magnitude** faster than alternatives. In its watcher mode, the build system usually finishes before you switch screen from the editor to the terminal tab (two digits of milliseconds). A fast iteration cycle reduces the need of keeping one's mental state around longer; this in turn allows one to stay in the flow longer and more often.
 
+That same fast loop is also useful in AI-assisted workflows, where small edits need to be checked and repaired quickly.
+
 ### Readable Output
 
 ReScript's JS output is very readable. This is especially important while learning, where users might want to understand how the code's compiled, and to audit for bugs.
 
+It also helps when teams use coding agents but still want the generated result to stay easy to inspect and review.
+
 This characteristic, combined with a fully-featured JS interop system, allows ReScript code to be inserted into an existing JavaScript codebase almost unnoticed.
 
 ### Preservation of Code Structure

markdown-pages/docs/manual/llms.mdx

@@ -19,6 +19,7 @@ Currently, we have the following files...
 ...and package-level documentation:
 
 - [/docs/react/llms](../react/llms.mdx) — the LLms documentation for ReScript React.
+- For a human-oriented overview of how these properties help in coding-agent workflows, see [ReScript and Coding Agents](./agentic-workflows.mdx).
 
 ## Notes