[docs-scanner] Missing context for modelRunner.enabled decision in Compose Bridge

[docker-agent]

File: content/manuals/compose/bridge/use-model-runner.md

Issue

The "Configure model runner settings" section jumps directly into showing a Helm values configuration without explaining when or why users would set modelRunner.enabled to true vs false:

modelRunner:
    # Set to false for Docker Desktop (uses host instance)
    # Set to true for standalone Kubernetes clusters
    enabled: false

The decision criteria are only mentioned in inline comments within the YAML block, which users might miss. The subsequent "Deploying a model runner" section explains the difference, but it comes after the configuration block.

Suggested fix

Add a brief introductory paragraph before the configuration block that explains:

• When to use enabled: false (Docker Desktop with host-based Model Runner)
• When to use enabled: true (standalone Kubernetes clusters)
• Why this distinction matters

Example:

## Configure model runner settings

The `modelRunner.enabled` setting determines where Docker Model Runner runs:

- Set to `false` for Docker Desktop, which uses the Model Runner instance on your host machine
- Set to `true` for standalone Kubernetes clusters, which deploys Model Runner as a pod in your cluster

When deploying using generated Helm Charts, you can control the model runner configuration through Helm values:

---

Found by nightly documentation freshness scanner