[benatespina]

Summary

• Closes the two gaps feat: keep the text of errors out of logs and spans unless runtime.telemetry.errorText includes it #252 left: React Router's default handleError logs the message and the stack of whatever a loader or an action rethrows, in production too; and on Cloudflare the dev server's "include" never reached the app, which lives in its Durable Object under a configuration bundled the same for every environment.
• @bounda-dev/react-router returns a handleError that follows runtime.telemetry.errorText through errorFields; the React Router templates and examples/onboarding wire it in app/entry.server.tsx.
• BOUNDA_ERROR_TEXT overrides errorText from the environment, so .dev.vars turns the text on in development on Cloudflare while a deployment keeps it out.

Changes

• react-router: handleError from createBounda (Node and Cloudflare) and @bounda-dev/react-router/app (HandleBoundaErrorFunction, exported). It logs one line, request failed, with the method and the error's class and code; the message, the stack and the request's path only with "include". It skips aborted requests and unwraps what React Router throws itself (no route matching). Node follows the booted app's configuration, and before any boot BOUNDA_ERROR_TEXT, then createBounda({ errorText }) (the dev server passes "include"); it never waits for a boot in flight; logger createConsoleLogger() by default. Cloudflare follows BOUNDA_ERROR_TEXT in the Worker's env, then the configuration a request has already imported; workersLogger by default. The rule is resolved synchronously: under vite dev a Worker cancels an import still pending once its response is sent, so awaiting one logged nothing. The bounda() Vite plugin warns when app/entry.server.* is missing or exports no handleError.
• core: one resolver for the precedence every host shares, resolveErrorText (a host's override, then BOUNDA_ERROR_TEXT, then the configuration, then the host's own default, then "omit"), and withErrorText, the configuration with it applied; ERROR_TEXT_VARIABLE names the variable. boot(), the CLI, the Durable Object, the Worker and both handleErrors resolve through it; the dev server's "include" is passed as the fallback, not copied. A value other than "omit" or "include" throws ConfigurationError where the app starts, and is passed over (ignoreInvalidEnv) where an app's failure is logged.
• cli: reads it below --error-text, for printed failures and the app's logs, bounda migrate included; a bad value is reported like a project that cannot load. bounda status (feat: share a lease among the background jobs, start them over after a restore, and report their status #260) opens the text of the subscribers' failures under the resolved rule, --error-text or BOUNDA_ERROR_TEXT=include alike, through the call the access log records.
• cloudflare: the Durable Object reads it from its env and applies it to the app; the Worker's 500 log follows it, and under a value it does not know still answers its 500 under the configuration's rule; workersLogger exported.
• create-bounda: app/entry.server.tsx for Node (renderToPipeableStream) and Cloudflare (renderToReadableStream), React Router 8.5's default entry for each runtime with handleError exported and called from the render's onError; BOUNDA_ERROR_TEXT=include in .dev.vars, and only a comment in .dev.vars.example, so Deploy to Cloudflare never asks for it.
• docs: observability (error text), configuration, CLI, personal data, Cloudflare adapter, and a "Logging errors" section in the React Router guide.

Tests

• React Router's own createRequestHandler over a server build whose loader rethrows: the default logs the message (control); with "omit" neither the message nor the stack reaches the console or the logger; with "include" both do.
• e2e of create-bounda: a request no route matches makes React Router call handleError; the dev server logs its text, react-router-serve does not; on Cloudflare vite dev and wrangler dev log it under .dev.vars, and wrangler dev without the line does not; the no-framework Worker logs the object's refusal with its text under .dev.vars.
• A precedence table on resolveErrorText/withErrorText, and one per host: boot(), the CLI, the Durable Object built with an env of the test's own, the Worker, the Node host and both Cloudflare handleErrors.
• Stryker: core 96.49%, cli 93.30%, react-router 99.56%, cloudflare 94.17%, create-bounda 94.57%; the survivors in changed lines are equivalent (a process?.env Node always has, now gone; the object's #app?.config for an alarm on an object whose app failed to start) or fixed.

Notes

• pnpm check is green except astro check in docs, which fails locally on macOS on a clean main too (@astrojs/check not detected, then an emnapi crash); CI runs it.
• After the release, sync the two Cloudflare template copies (pnpm templates:sync): their .dev.vars.example gains the comment.

Left out

Nothing.