docs(runtime): the ordering note in createStandaloneStack describes the order the kernel actually resolves (#4131)

The comment on `defaultDatasourcePlugin`'s slot claimed the position was
load-bearing — "MUST precede ObjectQLPlugin: its start() connects the default
driver … ObjectQLPlugin.start() runs boot schema-sync right after". Both halves
are wrong, and reading the slot as a guarantee is how #4085 happened:

- the connect happens in `init()`, not `start()`;
- the position cannot deliver that order anyway. `DefaultDatasourcePlugin`
  declares a hard dependency on ObjectQL, so `resolveDependencies` HOISTS
  ObjectQLPlugin ahead of it. Measured on a real serve boot:
  `com.objectstack.engine.objectql` inits at #10,
  `com.objectstack.runtime.default-datasource` at #16 — the reverse of what the
  slot reads as.

What actually orders them is the phase split (Phase 1 completes before any
`start()`) plus that declared dependency — the contract already documented on
the plugin itself, under its "Ordering — phase, not list position" note, which
records the no-tables boot that taught it to us. This comment now points there
instead of contradicting it two files away.

Comment only; no behaviour changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ve9HidCGRGtS2UjNPUGHSV

Author: claude

.changeset/standalone-stack-ordering-comment.md

@@ -0,0 +1,5 @@
+---
+---
+
+Comment-only: correct the plugin-ordering note in `createStandaloneStack`. No
+package behaviour changes, so this releases nothing.

packages/runtime/src/standalone-stack.ts

@@ -306,9 +306,24 @@ export async function createStandaloneStack(config?: StandaloneStackConfig): Pro
     stampSearchPinyinEnabled(artifactBundle?.i18n);
 
     const plugins: any[] = [
-        // MUST precede ObjectQLPlugin: its start() connects the default driver
-        // through the datasource connection service, and ObjectQLPlugin.start()
-        // runs boot schema-sync right after — the driver has to exist by then.
+        // This position buys NOTHING, and reading it as an ordering guarantee is
+        // how #4085 happened. The kernel resolves both init and start order from
+        // the plugin dependency graph, and `DefaultDatasourcePlugin` declares a
+        // hard dependency on ObjectQL — which HOISTS ObjectQLPlugin ahead of it
+        // (measured on a serve boot: `com.objectstack.engine.objectql` inits
+        // 6 slots BEFORE `com.objectstack.runtime.default-datasource`), the exact
+        // opposite of what this slot looks like it is asking for.
+        //
+        // What actually makes the driver exist before boot schema-sync is the
+        // PHASE split, not this list: the datasource plugin connects in `init()`
+        // (Phase 1 completes before ANY `start()` runs) and depends on ObjectQL
+        // so ITS init registers the engine first. That contract, and the earlier
+        // no-tables boot that taught it to us, are documented on the plugin
+        // itself — see the "Ordering — phase, not list position" note in
+        // `default-datasource-plugin.ts`. Order requirements belong THERE, next
+        // to the code the kernel enforces them from; a comment on an array index
+        // cannot enforce anything. (#4131 tracks making the AppPlugin end of this
+        // contract enforced rather than conventional.)
         defaultDatasourcePlugin,
         new MetadataPlugin({
             // Source-file scanner OFF — declarative metadata is loaded