Ridu v0.11.2

Ridu 0.11.2

This patch treats a migration that is not needed as a successful CLI outcome.

Fixes

• ridu migrate create now exits successfully when the schema is unchanged or only admin
  presentation settings changed. It prints No migration needed with the reason and writes
  no artifact. Genuine planning, validation, and safety failures still return an error.
• ridu upgrade recognizes this successful no-op and does not report that a migration was
  created. New migrations still print their creation details and require the ordinary review
  and application workflow.
• PostgreSQL, SQLite, and MongoDB migration planning and development rename handling now use
  typed current-schema outcomes rather than matching error text.

Upgrade

Update the Go module and all Ridu npm packages to 0.11.2 together, regenerate application
contracts, and rebuild with the matching CLI. Scripts that call ridu migrate create should
expect exit code zero when nothing needs migrating. This patch changes no public API signatures,
manifest/protocol versions, plugin contracts, or persisted migration encodings. Keep existing
migration artifacts and database ledgers; these fixes require no new application migration.