feat(pino): allow customizing error logging - #1934

✅ No new issues found.

Reviewed changes — Extends the pino LoggingHandlerPlugin with a logError(logger, error) option for customizing error payloads and log levels.

• packages/pino/src/handler-plugin.ts: adds the optional logError to LoggingHandlerPluginOptions and routes all three logger.error call sites (internal/interceptor, business-logic, stream) through this.logError, defaulting to (logger, error) => logger.error(error). Business and stream sites gained an else if (logger) guard, which is required to avoid calling logError(undefined, error) when the context logger is absent.
• packages/pino/src/handler-plugin.test.ts: adds warn spy and Logger type import; three new tests cover custom internal/business/stream error logging, plus assertions that logError is not called on abort paths.
• apps/content/docs/integrations/pino.md: documents logError in the sample and prose.

I verified the implementation routes all error-logging call sites through logError, preserves logger.error(error) as the default, and keeps business/stream aborts at info without invoking logError — consistent with the JSDoc and docs contract. I ran pnpm vitest run packages/pino/src (14 passed) and pnpm --filter @orpc/experimental-pino type:check (clean). The default and custom paths are both genuinely exercised; the new tests would fail if routing regressed to logger.error.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}