@ultimat3/http 19.3.1 → 19.3.2

package/CLAUDE.md

@@ -422,6 +422,12 @@ Owned request lifecycle over `Bun.serve`. Tier 2.
   `APP_ERROR_STATUS` is process-global runtime state filled by the app's own imports, while both
   named surfaces are build artefacts derived from source, so in a CLI process it answers `{}`.
   Wiring one means deriving it from source, not re-exporting the map.
+- **A handler's own `Response.status` is never rewritten.** `error-map.ts` answers the status of a
+  THROW; a status a handler chose — `html(page, { status: 404 })`, which is what a page route's
+  `withStatus(404, data)` in `@ultimat3/render` becomes — passes through every stage as written,
+  body included, in dev and in production. `pipeline-handler-status.test.ts` pins it, because the
+  render seam is only true while this is: ai-maxxing's `/fleet/nope` answered 200 for as long as
+  the only way to a 404 was the error page, outside the app's shell.
 - **The context carries the inbound headers, never the `Request`.** `ctx.requestHeaders` is set
   once at construction; `useRequestHeader` / `useRequestCookie` are what app code reads, and
   `UltimateRequest.cookie()` is what `hooks.authenticate` reads. A `Request` on the context is a

package/package.json

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

package/src/error-map.ts

@@ -347,6 +347,10 @@ export const ERROR_STATUS = {
   // document that said "the details are in this process's logs" about an error whose whole
   // value is the sentence naming the prop and its bytes. Measured on ai-maxxing, 2026-09-05.
   X_ISLAND_PROPS_INVALID: 500,
+  // A loader answered `withStatus` with a 3xx, or a status outside 200–599. Raised INSIDE the
+  // request that ran the loader, so it needs a row for the same reason the line above does: an
+  // unclassified 500 blanks the sentence naming the status and the `redirect()` to use instead.
+  X_ROUTE_STATUS_INVALID: 500,
   // @ultimat3/mail
   // The deployment configured no transport. It reaches a caller only through an inline
   // `send(…, { sync: true })` inside a request; the queued path dead-letters instead. A server-side
@@ -361,6 +365,9 @@ export const ERROR_STATUS = {
   // MCP host is mounted inside this pipeline — a code that renders 429 on one and 500 on the other
   // is exactly the split this table exists to prevent.
   X_MCP_RATE_LIMITED: 429,
+  // The second MCP code answered on a request before dispatch, and 413 for the same reason the row
+  // above is 429: `transport-http.ts` already answers it with that status by hand.
+  X_MCP_BODY_TOO_LARGE: 413,
   // @ultimat3/core
   // The caller asked for a format the pipeline cannot produce (`?f=avif`): the request names an
   // unsupported representation, which is 415 — not a 500, which would blame the server for it.