v3.20.1

Bug Fixes

• @byline/richtext-lexical — a schema field's editorConfig now merges over the
  registered editor config instead of replacing it wholesale. Previously, setting
  editorConfig on a rich-text schema field discarded the config baked in at registration
  via lexicalEditor() — including its extensions graph — and silently fell back to the
  built-in extension list, so registration-time changes (an added AI extension, removed
  Insert-menu extensions, …) vanished for any field that carried its own settings. The new
  resolveEditorConfig helper merges layer by layer: the field layer (JSON-safe
  settings + lexical, merged per-key including settings.options) wins for the keys it
  can express, while the registered layer's extensions graph survives a field-level
  settings override. Field configs without an editorConfig are unaffected.

All other @byline/* packages bumped to 3.20.1 in lockstep with no behavioural changes this cycle.