Lexical error #17 (v=list) in admin editor when post created via REST API

Describe the Bug

When creating a post via the REST API with a valid Lexical JSON structure
containing list and listitem nodes, the admin editor throws
Minified Lexical error #17; v=list when opening the post for editing.

The content renders correctly on the public frontend — only the admin
editor fails to parse the editor state.

Environment

• Payload version: 3.x (latest)
• Next.js: 15
• @payloadcms/richtext-lexical: latest
• Database: PostgreSQL
• Node: 20.x
• Template: website

Steps to Reproduce

1. Get a JWT token:

POST /api/users/login
{ "email": "your@email.com", "password": "yourpassword" }

2. Create a post via REST API:

POST /api/posts
Authorization: JWT <token>
Content-Type: application/json

{
  "title": "Test list bug",
  "slug": "test-list-bug-1",
  "_status": "published",
  "content": {
    "root": {
      "type": "root",
      "format": "",
      "indent": 0,
      "version": 1,
      "direction": "ltr",
      "children": [
        {
          "tag": "ul",
          "type": "list",
          "start": 1,
          "format": "",
          "indent": 0,
          "version": 1,
          "listType": "bullet",
          "direction": "ltr",
          "children": [
            {
              "type": "listitem",
              "value": 1,
              "format": "",
              "indent": 0,
              "version": 1,
              "direction": "ltr",
              "children": [
                {
                  "text": "Example item",
                  "type": "text",
                  "format": 0,
                  "version": 1
                }
              ]
            }
          ]
        }
      ]
    }
  }
}

3. Open /admin/collections/posts/{id}
4. Observe Lexical error #17 (v=list) in browser console

Expected Behavior

Admin editor renders the post without errors. The JSON structure sent
is identical to what GET /api/posts returns for posts created via
the admin UI.

Actual Behavior

Minified Lexical error #17; visit https://lexical.dev/docs/error?code=17&v=list

Additional Notes

• Public frontend (/posts/{slug}) renders the content correctly
• The listitem structure is identical to posts created via the admin UI
• Issue persists after clean rebuild (rm -rf .next && npm run build)
• UnorderedListFeature and OrderedListFeature are registered in both
  the collection editor and the root lexical config
• The vendor chunk hash does not change between builds regardless of
  feature config changes