docs(site): document inlined-imports field in front-matter reference (#738)

Author: github-actions[bot]

site/src/content/docs/reference/front-matter.mdx

@@ -61,6 +61,10 @@ runtimes:                      # optional runtime configuration (language enviro
   #   feed-url: "https://pkgs.dev.azure.com/myorg/_packaging/myfeed/nuget/v3/index.json"
 # env:                          # RESERVED: workflow-level environment variables (not yet implemented)
 #   CUSTOM_VAR: "value"
+# inlined-imports: false        # When true, resolve {{#runtime-import ...}} markers at compile time
+#                               # (default: false -- markers are resolved at pipeline runtime, so
+#                               # prompt-body edits do not require recompilation).
+#                               # See the Inlined Imports section below for details.
 mcp-servers:
   my-custom-tool:              # containerized MCP server (requires container field)
     container: "node:20-slim"
@@ -236,6 +240,27 @@ becomes a `repos:` entry, with `checkout: false` added for entries
 that weren't listed under `checkout:`. Mixing the legacy fields with
 an existing `repos:` block is rejected; pick one shape.
 
+## Inlined Imports
+
+The `inlined-imports:` field controls when `{{#runtime-import ...}}`
+markers in the markdown body are resolved. It defaults to `false`.
+See the [Runtime imports reference](/ado-aw/reference/runtime-imports/) for the full marker
+syntax, path resolution rules, and runtime behavior.
+
+When `inlined-imports: false` (the default), the compiler leaves runtime-import
+markers to be resolved on the pipeline runner. Prompt-body edits do not require
+recompiling the generated YAML — the pipeline fetches the latest prompt at
+runtime automatically.
+
+When `inlined-imports: true`, the compiler resolves all runtime-import
+markers at compile time, including the implicit top-level marker that
+normally reloads the body itself. The emitted YAML contains the fully
+expanded prompt body, so the pipeline file is self-contained.
+
+The trade-off is that the generated YAML is larger, and prompt-body
+edits require `ado-aw compile` plus committing the updated pipeline
+file.
+
 ## Filter Validation
 
 The compiler validates filter configurations at compile time and will emit