@ultimat3/http 25.1.0 → 26.0.0

package/README.md

@@ -336,7 +336,8 @@ mechanism. It is a plain function and not a pipeline stage, because the secret i
 and only the route knows which one applies.
 
 ```ts
-// apps/web/api/webhooks/partner/route.ts
+// apps/web/webhooks/partner.ts — mounted as a plain HTTP route through the `routes` runtime
+// override (apps/web/runtime.ts); `api/` holds no route file
 import { verifyWebhookSignature } from '@ultimat3/http';
 
 declare const env: { readonly PARTNER_WEBHOOK_SECRET: string };   // the app's defineEnv() result

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/http",
-  "version": "25.1.0",
+  "version": "26.0.0",
   "description": "Owned request lifecycle over Bun.serve: router, ordered pipeline, problem+json errors",
   "license": "MIT",
   "type": "module",
@@ -35,9 +35,9 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "25.1.0",
-    "@ultimat3/i18n": "25.1.0",
-    "@ultimat3/schema": "25.1.0",
-    "@ultimat3/time": "25.1.0"
+    "@ultimat3/core": "26.0.0",
+    "@ultimat3/i18n": "26.0.0",
+    "@ultimat3/schema": "26.0.0",
+    "@ultimat3/time": "26.0.0"
   }
 }

package/src/errors.ts

@@ -129,11 +129,10 @@ export const bodyInvalid = (
     code: 'X_BODY_INVALID',
     cause: `${pathname} body rejected: ${issues.join('; ')}`,
     ...(meta === undefined ? {} : { meta }),
-    // `x schema show` is not a command — not in the registry and not in `PLANNED_COMMANDS`, so it
-    // exits `X_CLI_UNKNOWN_COMMAND`. The same axiom-4 inversion `x logs tail` had in `error-map`:
-    // the one instruction the reader is given fails when they run it. `x routes` ships, and
-    // `hasInputSchema` plus the route's name is what it prints.
-    fix: `x routes --json   # find ${pathname}, then send a body matching its input schema`,
+    // Only a route that declares `meta.input` reaches the body stage, and no action or query does
+    // (`invoke` and `runQuery` validate their own input, as `X_INPUT_INVALID`) — so this is a plain
+    // `runtime.ts` route, and `x routes --surface api` lists those by name since owner decision 2.
+    fix: `x routes --surface api --json   # find ${pathname}, a runtime.ts route, then send a body its meta.input schema accepts`,
   });
 
 /** At construction: a hole in a scope, or a prefix shadowing `/api` or `/_x`, never serves. */

package/src/server.ts

@@ -28,7 +28,7 @@ import { type RateLimitStore, rateLimiter } from './rate-limit';
 import { withRouteBuckets } from './rate-limit-buckets';
 import { adoptRateLimitStore } from './rate-limit-installed';
 import { jsonResponse } from './response';
-import { describeRoutes, httpRouter, type Route, type RouteDescription } from './router';
+import { describeRoutes, httpRouter, type Route } from './router';
 
 /**
  * Beside its one caller rather than in `errors.ts`, which is at the 500-line ceiling — the
@@ -142,7 +142,6 @@ export interface ServerHandle {
   state(): LifecycleState;
   /** `http://host:port` once started; throws before `start()`. */
   url(): string;
-  describe(): readonly RouteDescription[];
   start(): ServerHandle;
   /** Runs core's three-phase drain, on the deadline `drain.deadlineMs` set (`lifecycleForRole`). */
   stop(): Promise<void>;
@@ -306,7 +305,6 @@ const buildServer = (options: ServerOptions, releaseStore: () => void): ServerHa
       if (server === undefined) throw serverNotStarted('url()');
       return server.url.origin;
     },
-    describe: () => describeRoutes(table),
     fetch: (request) => dispatch(request),
     start() {
       // FIRST, before the socket. `markReady()` refuses a process whose lifecycle already drained