[cloudflare workerd] Workers Logs omits a native Error logged after a structured object

## Observed symptom 🐛 Bug Report — Runtime APIs: Workers Logs omits a native Error logged after a structured object For `console.error(context, error)`, where `context` is a plain object and `error` is a native `TypeError`, stored Workers Logs events contained the structured context but omitted the exception's name, message and stack. Repeating the failing request with `wrangler tail --format json` attached captured the native error in both `message` and `errorInfo`. This prevents diagnosis of a handled failure from retained logs unless a live tail was attached. The application did not stringify, wrap or nest the error before passing it as the second console argument. ## Observed behavior On 2026-09-26, a deployed Worker caught `TypeError: Invalid header value.` while constructing a request and logged it using this shape: ```js console.error({ message: "Request construction failed", ...context }, er ## Literal error text ``` Workers Logs omits native Error ``` ## Environment GitHub issue cloudflare/workerd #7537; state=open ## Trigger / context For `console.error(context, error)`, where `context` is a plain object and `error` is a native `TypeError`, stored Workers Logs events contained the structured context but omitted the exception's name, message and stack. Repeating the failing request with `wrangler tail --format json` attached captured the native error in both `message` and `errorInfo`. This prevents diagnosis of a handled failure from retained logs unless a live tail was attached. The application did not stringify, wrap or nest the error before passing it as the second console argument. ## Observed behavior On 2026-09-26, a deployed Worker caught `TypeError: Invalid header value.` while constructing a request and logged it using this shape: ```js console.error({ message: "Request construction failed", ...context }, error); ``` The message above is generalized; application-specific context and identifiers are omitted. - Two stored console events retrieved through the Workers Observability telemetry query API contained only `level`, the contextual `message`, and the context objects. Neither exposed the exception name, message, stack or `errorInfo`. `$metadata.error` repeated the contextual summary; `$workers.truncated` was `false`. - A subsequent attempt through the same catch site, captured with live tail, included `"TypeError: Invalid header value."` as `message[1]`. Its `errorInfo[0]` was `null`; `errorInfo[1]` contained `name: "TypeError"`, `message: "Invalid header value."`, and the stack frames ide ## Source evidence - https://github.com/cloudflare/workerd/issues/7537 (2026-09-26T06:06:28Z) — GitHub issue #7537 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:43:35.178343Z - scout_id: C4710e24ff9 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.