See PhoenixKitProjects.Extensions.Registry.catalog/0.

@spec disable(map() | binary(), String.t(), keyword()) ::
  {:ok, PhoenixKitProjects.Schemas.ProjectModule.t()} | {:error, term()}

Disables an extension instance for a project. The row (and its config) survives — see the moduledoc. Creates an explicit disabled row when the enablement was implicit (catalog default_enabled), so "turn tasks off" works on a project that never had a row.

@spec enable(map() | binary(), String.t(), keyword()) ::
  {:ok, PhoenixKitProjects.Schemas.ProjectModule.t()} | {:error, term()}

Enables an extension for a project (upserts the instance row).

Options: :actor_uuid, :instance_key, :config (whitelisted), :name. Returns {:ok, row} or {:error, reason}. Unknown extension keys are rejected ({:error, :unknown_extension}); an extension whose site module is disabled is rejected ({:error, :module_disabled}) — enabling something that can't render is a config trap.

@spec enabled?(map() | binary(), String.t(), String.t()) :: boolean()

Whether one extension is effectively enabled for a project.

Accepts a project struct or uuid. The intersection rule from the moduledoc applies; unknown keys are always false (fail-closed).

@spec enabled_for_project(binary()) :: [
  {PhoenixKitProjects.Extensions.Extension.t(),
   PhoenixKitProjects.Schemas.ProjectModule.t() | nil}
]

The extensions EFFECTIVELY enabled for a project: catalog availability ∩ (explicit row OR catalog default). Returns [{%Extension{}, %ProjectModule{} | nil}] — the row is nil when enablement comes from default_enabled with no explicit row yet.

@spec enabled_map(binary()) :: %{required(String.t()) => boolean()}

The effective enablement of EVERY catalog extension for a project — its DEFAULT instance, which is what enabled?/2 asks about; a named instance is enabled?/3's business — as %{ext_key => boolean}, from ONE list_rows/1 read: an explicit row wins, otherwise the catalog default; an unavailable extension (its module off) is false however its row reads — the same answer enabled?/3 gives per key, for the callers that need all of them at once (Features.gates/1, the Modules panel, the members page: each used to ask per extension, per flag, on every mount and broadcast).

@spec get_row(binary(), String.t(), String.t()) ::
  PhoenixKitProjects.Schemas.ProjectModule.t() | nil

One enablement row (or nil).

See PhoenixKitProjects.Extensions.Registry.get/1.

@spec list_rows(binary()) :: [PhoenixKitProjects.Schemas.ProjectModule.t()]

All enablement rows for a project (enabled AND disabled — panel UI needs both).

See PhoenixKitProjects.Extensions.Registry.list/0.

See PhoenixKitProjects.Extensions.Registry.refresh/0.

@spec update_config(map() | binary(), String.t(), map(), keyword()) ::
  {:ok, PhoenixKitProjects.Schemas.ProjectModule.t()} | {:error, term()}

Updates one instance's config, whitelisted against the extension's config_schema keys. Unknown keys are silently dropped (never written); the stored map is REPLACED by the whitelisted input merged over it, so omitted known keys survive.