docs(web/guides): clarify box CLI vs wheels CLI in v4 active docs

CHANGELOG.md

@@ -26,6 +26,7 @@ All historical references to "CFWheels" in this changelog have been preserved fo
 
 **Documentation**
 - Add Debug Panel guide covering each tab, configuration settings, and when the bar appears
+- Clarify BoxLang server management in cfml-engines guide; update vm-deployment tip to distinguish CommandBox server management from the `wheels` dev CLI
 
 **ORM & data layer**
 - Chainable query builder with `where()`, `orWhere()`, `whereNull()`, `whereBetween()`, `whereIn()`, `whereNotIn()`, `orderBy()`, `limit()`, and more for injection-safe fluent queries (#1922)

web/sites/guides/src/content/docs/v4-0-0-snapshot/deployment/vm-deployment.mdx

@@ -67,7 +67,7 @@ Lucee 7 is the canonical engine target for Wheels 4. Two install options work eq
 Follow the Lucee install docs end-to-end rather than re-typing them here — they're the authoritative source and they change with each release. See [Lucee installation guides](https://docs.lucee.org/guides/installing-lucee/).
 
 <Aside type="tip">
-  If you already run CommandBox on other hosts, you can install Lucee via `box server start cfengine=lucee@7.0.1+100` on the VM too. It's the same mechanism the Wheels test images use (see `tools/docker/lucee7/server.json`). The systemd unit below still applies — point `ExecStart` at the CommandBox wrapper script instead of `lucee.sh run`.
+  If your team already uses CommandBox for server management, you can run Lucee on the VM via `box server start cfengine=lucee@7.0.1+100` as an alternative to the official installer. The systemd unit below still applies — point `ExecStart` at the CommandBox wrapper script instead of `lucee.sh run`. Note that `wheels start` is a local development convenience (it bundles a Lucee Express runtime for dev machines) and is not intended for production VM deployment.
 </Aside>
 
 After install, confirm Lucee is listening on a local port (`8888` is a common default) and that a `lucee.sh` (or equivalent) start script exists in `/opt/lucee/bin`.

web/sites/guides/src/content/docs/v4-0-0-snapshot/start-here/cfml-engines.mdx

@@ -81,6 +81,10 @@ cd myApp
 box server start cfengine=boxlang@latest port=8080
 ```
 
+<Aside type="note">
+The `wheels start`, `wheels stop`, `wheels reload`, and `wheels test` commands all assume the Lucee Express bundled with the CLI — they do not interact with BoxLang. BoxLang developers manage their server through CommandBox (`box server start/stop/restart`) and reload via `?reload=true&password=<your-password>` directly. Generators (`wheels generate ...`) are pure file-system operations and work the same regardless of engine.
+</Aside>
+
 Wheels' BoxLang compatibility is verified per release in the same CI matrix as Lucee and Adobe CF. Cross-engine gotchas worth knowing about live in [`.ai/wheels/cross-engine-compatibility.md`](https://github.com/wheels-dev/wheels/blob/develop/.ai/wheels/cross-engine-compatibility.md) — most are about minor differences in struct/array semantics under closures.
 
 ## Pick an engine