Enable replayServerAsyncOperationLogs on Pro Node renderer

Without this flag, console.* calls made inside async Server Components
are captured by the renderer's per-request sharedConsoleHistory but not
replayed back to Rails' logs. Any error-path logging from an async
component (for example, a catch block that console.errors before
returning an error fallback div) disappears, making runtime failures
invisible.

The generator template, RORP spec dummy, and every maintained RSC demo
set this to true for the same reason.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ihabadham

renderer/node-renderer.js

@@ -47,6 +47,11 @@ const config = {
   // Flight-protocol yielding — with it stubbed, the RSC stream silently
   // emits zero chunks and hangs until the Fastify idle timeout fires.
   stubTimers: false,
+  // Surface console output from async server-component code. Without this,
+  // `console.error` calls from within async Server Components (e.g.
+  // CommentsFeed's catch block) are silently dropped by the VM, making
+  // runtime failures in RSC components invisible.
+  replayServerAsyncOperationLogs: true,
 };
 
 reactOnRailsProNodeRenderer(config);