Ridu v0.12.0

Ridu 0.12.0

This release adds reviewed field-kind changes and migration baseline replacement, moves portable
rich-text values and rendering into the SDK, and improves recovery of unsaved document edits.

Changes

• ridu dev compares field kinds against the schema recorded in the database. Incompatible stored
  values require review; supported development changes can explicitly clear the affected current
  values and version snapshots. Cancellation preserves the accepted server and content. Offline
  migration creation requires an admitted data transform for an incompatible kind change.
• ridu migrate baseline --replace can record a squashed history on a development database that
  already has its schema. It checks schema drift and previously executed data steps, leaves new
  data steps pending, and requires confirmation before replacing a database's recorded head.
• Portable rich-text types and renderRichTextHTML now ship in @riducms/sdk/richtext. Content
  consumers can render without installing the Svelte/Lexical editor; optional Svelte rendering
  remains in @riducms/plugin-richtext/svelte.
• Restored draft notifications include Discard and remain until saving, discarding, or leaving.
  When the saved document has changed, recovery compares the original, local, and latest values
  before the editor chooses Keep yours or Load latest. Saving and publication wait for that choice.
  Recovery retains only fields the editor can currently write and matches repeated content by
  stable identity.
• Reference routes derive from declaration names. Method URLs gain a -method suffix and CLI
  pages a ridu- prefix. Removed routes no longer redirect; the search budget covers the compressed
  index downloaded by visitors.
• The website lockfile updates devalue to 5.9.4, addressing the shared-memory serialization,
  string-expansion, and asynchronous-rejection advisories in versions through 5.9.2.

Breaking changes and upgrade

Update the Go module and every Ridu npm package to 0.12.0 together, regenerate application
contracts, and rebuild with the matching CLI.

• Import rich-text document types and HTML rendering from @riducms/sdk/richtext. The rich-text
  plugin's /document and /render entry points and portable root exports have been removed.
• Declare package_manager explicitly in ridu.toml, for example package_manager = "bun".
• Replace schema.Manifest.WithoutAdminPresentation with StorageSchema,
  mongodb.CreateArtifactWithOptions with CreateArtifact, and
  postgres.BuildArtifactWithPreviousPlanner with BuildArtifact. PostgreSQL's builder accepts
  compiled data-transform descriptors. Removed manifest plugin version/range fields and migration
  auth-identity canonicalization contracts are no longer supported.
• Legacy planner 1.0.0 histories, unsupported PostgreSQL planner versions, databases without a
  recorded schema, and legacy migration encodings are no longer accepted. Preserve required
  content and backups and recreate affected databases and history with this release. Baseline
  replacement does not convert unsupported history or establish an unknown schema.
• History and readiness compare the storage schema rather than application names, labels, admin
  settings, endpoint metadata, or plugin build metadata. Rebuild all application binaries after
  updating contracts or replacing history. Stop application processes and writers before approving
  baseline replacement at a recorded head; binaries built from the old history then fail readiness.
• Update links to changed reference URLs; old route aliases and the unused highlight= code
  annotation alias have been removed.

This is a pre-1 release with breaking contracts. Manifest, artifact, and plugin format counters
remain in their current families; regenerate with the coordinated release rather than mixing
packages or relying on old encodings.