Otter Blocks crashes Gutenberg editor with ownerDocument error

Description

I'm experiencing a reproducible Gutenberg editor crash whenever Otter Blocks is active.

Error:
TypeError: Cannot read properties of null (reading 'ownerDocument')

The stack trace is:

compose.min.js → rich-text.min.js → Array.map()

Environment:

WordPress 7.1
Otter Blocks 3.2.5
Neve 4.2.11
No Otter Pro

Could you investigate whether Otter is registering an editor component, Rich Text extension, or DOM/document reference that is incompatible with the current Gutenberg editor environment?

Step-by-step reproduction instructions

Troubleshooting performed:

Deactivating Otter Blocks → Gutenberg editor works
Activating Otter Blocks → editor crashes
WordPress Troubleshooting Mode with only Otter Blocks active → editor still crashes
Neve theme → editor crashes
Twenty Twenty-Six theme → editor crashes
WordPress 7.1 → editor crashes
WordPress 7.0.x → editor crashes
Otter 3.2.5 → editor crashes
Otter 3.2.3 → editor crashes
Creating a completely blank new page → editor crashes immediately
Existing page content is therefore not required to reproduce the issue

This appears to be an Otter Blocks editor initialization issue rather than a page-specific block, theme, or plugin conflict.

Screenshots, screen recording, code snippet or Help Scout ticket

The complete browser console error is:

TypeError: Cannot read properties of null (reading 'ownerDocument')

at compose.min.js
at rich-text.min.js
at Array.map
at compose.min.js

Environment info

No response

Is the issue you are reporting a regression

No

Reproduce the crash in a blank Gutenberg page with only Otter Blocks active, then inspect the browser stack involving compose.min.js, rich-text.min.js, and Array.map(). Compare behavior with Otter deactivated and the listed WordPress versions. Done means the editor loads without the ownerDocument error while Otter Blocks remains active.