Versioned migrations for Rindle-owned database tables.

Create separate normal migrations in your Phoenix or Ecto application. The host owns public.oban_jobs and its public.schema_migrations ledger; install Oban first in its own host migration:

defmodule MyApp.Repo.Migrations.InstallHostOwnedOban do
  use Ecto.Migration

  def up, do: Oban.Migration.up()
  def down, do: Oban.Migration.down(version: 1)
end

Then call Rindle.Migration from a separate host migration. The default call omits :prefix and creates Rindle-owned state in rindle:

defmodule MyApp.Repo.Migrations.InstallRindle do
  use Ecto.Migration

  def up, do: Rindle.Migration.up(version: 1)
  def down, do: Rindle.Migration.down(version: 1)
end

For the explicit public compatibility pairing only, use a public-compiled release and a separate host migration:

defmodule MyApp.Repo.Migrations.InstallPublicRindle do
  use Ecto.Migration

  def up, do: Rindle.Migration.up(version: 1, prefix: "public")
  def down, do: Rindle.Migration.down(version: 1, prefix: "public")
end

Rindle creates and rolls back only its fixed relation set; it never owns public.oban_jobs or public.schema_migrations. Run your normal host migration workflow (mix ecto.migrate) and then verify it with mix rindle.doctor.

For populated public installs, use the host-owned maintenance-window move in Upgrading; do not broaden this fresh-install API.