fix(plugin-hono-server): a request for port 0 no longer warns that port 0 is in use

kernel:listening compared the requested port with the bound one and warned
whenever they differed. Port 0 asks for a kernel-assigned port, so the two
can never match and nothing was in use. The warning now fires only for a
non-zero request the adapter's EADDRINUSE walk moved; the started line
already names the bound port.

The released-port ledger's reason for serve-port-drift-notice.e2e.test.ts
quoted that warning as why its negative arm cannot use --port 0. It now
states only the arm's subject: a non-zero request, which --port 0 cannot ask.

Claude-Session: https://claude.ai/code/session_01SYEJqDL3NXxrJRBVqaMu9T
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/24387-port-zero-busy-warning.md

@@ -0,0 +1,10 @@
+---
+'@objectstack/plugin-hono-server': patch
+---
+
+fix(plugin-hono-server): a request for port 0 no longer warns that port 0 is in use
+
+Clause-②: no (no export, option or type moves: a log line stops firing for a legal request)
+
+- **What changed.** `HonoServerPlugin`'s `kernel:listening` hook compared the requested port with the bound one and warned `Port 0 is in use, using port N instead` whenever they differed. Port `0` asks for a kernel-assigned port, so the two can never match and nothing was in use. Every `os serve --port 0` boot printed that warning under the banner's Boot diagnostics, at the default log level and at `info`. The warning now fires only for a non-zero request that the adapter moved to another port.
+- **Unchanged.** A kernel-assigned boot prints the existing `HTTP server started successfully` line, which already names the bound port, and nothing else. A non-zero request whose port is held still warns, naming the requested and the bound port.

packages/cli/test/released-port-production-spawn.pin.test.ts

@@ -86,8 +86,7 @@ const RELEASED_DRAW_LEDGER: Readonly<Record<string, { draws: number; why: string
   'serve-port-drift-notice.e2e.test.ts': {
     draws: 1,
     why: 'the NEGATIVE arm is a boot that binds exactly the non-zero port it asked for and says '
-      + 'nothing about ports; `--port 0` asks for no port, and that boot prints plugin-hono-server\'s '
-      + '"Port 0 is in use, using port N instead" (#24387)',
+      + 'nothing about ports; a non-zero request is its subject, which `--port 0` cannot ask',
   },
   'serve-publishes-bound-port.e2e.test.ts': {
     draws: 2,

packages/plugins/plugin-hono-server/src/hono-plugin.ts

@@ -709,7 +709,12 @@ export class HonoServerPlugin implements Plugin {
             await this.server.listen(port);
 
             const actualPort = this.server.getPort();
-            if (actualPort !== port) {
+            // Port 0 is a request for a kernel-assigned port, not a busy one:
+            // `listen(0)` can never bind the number it was given, so a mismatch
+            // there says nothing about a port in use. The started line below
+            // already names the bound port. Only a non-zero request that the
+            // adapter's EADDRINUSE walk moved is a drift worth a warning.
+            if (port !== 0 && actualPort !== port) {
                 ctx.logger.warn(`Port ${port} is in use, using port ${actualPort} instead`);
             }
             ctx.logger.info('HTTP server started successfully', {