docs(devframe): clarify onServerError applies to owned servers only

The option silently does nothing when a `server` is supplied, so lead
the JSDoc with that constraint (and why — the caller owns that object
and its crash semantics are not devframe's to change) instead of
mentioning it mid-paragraph.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Author: dvcolomban

packages/devframe/src/node/server.ts

@@ -111,11 +111,13 @@ export interface StartHttpAndWsOptions {
    */
   onReady?: (info: { origin: string, port: number, app: H3 }) => void | Promise<void>
   /**
-   * Called for any error the owned HTTP server emits after it starts
+   * Called for any error the HTTP server devframe owns emits after it starts
    * listening — e.g. a transient `EMFILE` while accepting a connection.
-   * Ignored when a `server` is supplied — the caller already owns that
-   * object and can listen on it directly. Without this, a post-bind error
-   * has no listener and crashes the process.
+   * Without it such an error has no listener and crashes the process.
+   *
+   * Applies only to a server devframe created itself. When `server` is
+   * supplied the caller owns that object and attaches to it directly, so
+   * devframe leaves its error handling alone.
    */
   onServerError?: (error: Error) => void
 }