Ridu v0.13.0

Ridu 0.13.0

Rich-text blocks now expose their fields inline, and document headers show the number of retained
versions. This release also improves unfinished-edit protection and authorized version counting.

Changes

• Insert rich-text blocks directly into the editor and edit their ordinary fields inline. Collapsing
  a block preserves unfinished input, nested editors retain their own history, and validation opens
  affected blocks. Code and JSON editor shortcuts respect events already handled by child editors.
• Sparse rich-text documents hydrate safely. Unfinished or invalid plugin input marks a document
  as changed, blocks saving with field issues, and participates in navigation protection.
• Collection and global version counts are available through the Go API, REST, and Fetch SDK.
  Document-header badges and history capabilities use authorized counts without fetching snapshots.
• SQLite version lists and counts compile supported snapshot access predicates into SQL. Historical
  shapes, complex paths, and unsupported comparisons retain the existing matcher semantics.
• Embedded schema forms support onChange for external-editor history and serialization.
  createSchemaPayload creates new items using Go-declared defaults and a fresh identity.

Breaking changes and upgrade

Update the Go module and every Ridu npm package to 0.13.0 together, regenerate application
contracts, and rebuild the admin and application binary.

• Custom store.VersionTransaction implementations must add
  CountVersions(context.Context, store.VersionRequest) (int, error).
• Manually implemented RiduClient interfaces must add countVersions and countGlobalVersions.
• Custom PluginFieldBinding implementations and wrappers must implement or forward
  reportPendingEdit. Report issues while displayed input cannot be stored, and clear them when
  that input is stored or discarded.
• FieldAuthoringHost.schemaForm renders an embedded item's body fields. Render schemaHeader
  separately when a custom embedded editor needs its configured editorial-name control.

No database migration or persisted-format conversion is required by these changes. This is a
pre-1 release with breaking extension contracts; keep the coordinated packages aligned.