next.js

eba3d2bb - Restore separate runtime/dynamic error messages and fix cookies() classification

Restore separate runtime/dynamic error messages and fix cookies() classification Revert the merged bodyMessage/metadataMessage/viewportMessage back to separate runtimeBodyMessage/dynamicBodyMessage etc. so the dev overlay can distinguish runtime APIs from uncached data. Restore the original isRuntimeVariant detection that matches on 'request-time API', 'cookies()', and 'Runtime data' — the tightened check broke classification when the second validation pass overrides with DynamicHoleKind.Dynamic. Also stamp syncDynamicErrorWithStack errors with runtimeBodyMessage since sync dynamic errors are always from runtime APIs. Made-with: Cursor