fix: four defects found by Payload's own e2e suites (0.1.2)

[Mheaus]

Stacked on #2. Found by running Payload's own e2e suites against the adapter (Payload monorepo at v4.0.0-canary.39, PAYLOAD_FRAMEWORK=react-router).

Problem

loadAdminPage renders the admin view to the end, decodes the Flight stream, and React Router sends the decoded tree to the browser a second time. Decoding sets the key-validation flag of some elements back to 0, so in development React logged "Each child in a list should have a unique key prop. Check the render method of RouteId" for lists that were valid. Payload's e2e harness fails a test on any console error: 6 of the 15 auth tests failed on it.

Fix

markKeysValidated sets the flag again on the decoded tree, through arrays and resolved lazy nodes, in development only. React still validates keys when the view first creates its elements, so a real missing key is still reported on the server console.

Second fix: process in pre-bundled browser dependencies

processInClient replaces process.env and process.cwd() in browser code, but Vite pre-bundles node_modules dependencies before any plugin transforms them. A Next.js package that a Payload config imports then throws process is not defined in the browser: next/link reads process.env.__NEXT_ROUTER_BASEPATH. Payload's fields suites import next/link in their nav component, so every test of each suite failed (fields__collections__Array: 0/34).

The same replacement now runs as a Rolldown plugin of the client environment's dependency optimizer; server environments keep the real process. fields__collections__Array: 34/34, against 31/34 on TanStack Start on the same machine. New unit test.

Third fix: admin metadata

loadAdminPage kept only the title and description of Payload's page metadata. Robots (noindex, nofollow by default), Open Graph, Twitter cards and the configured favicons were missing: 8 admin tests failed. toAdminPageMeta now converts the whole MetaConfig (ported from @payloadcms/tanstack-start, MIT, credited in LICENSE) and AdminPage renders the tags. The admin metadata group: 17/18, the last one is a dev-server WebSocket drop.

Fourth fix: version-diff components inside the Payload monorepo

@vitejs/plugin-rsc wraps every exported capitalized function of a CSS-importing module as a server component. The Lexical diff converters are such functions, so the wrapper broke them and rich text diffs showed "unknown node". stripDistStyleImports removes their CSS imports, but its pattern did not match the /packages/<pkg>/src/ paths of the Payload monorepo. Published installs were not affected. The versions diff group: 45/46, the failure is shared with Next.js.

The full per-suite comparison with Next.js is in docs/COMPAT.md.

Results

• Payload auth suite on React Router: 14/15 (was 1/15). Next.js on the same machine and database (SQLite): 14/15, with the same failing test, which comes from the suite itself.
• Adapter unit tests: 19/19 (three new). Demo bench: 36/36 on the production build and on vite dev.
• Version 0.1.2.

🤖 Generated with Claude Code