#What's Changed

[Feature] Connect Supabase from a project's Integrations page. Approve ApiVault for a Supabase organization, then link its projects and choose the ApiVault environment each one receives. Connect Another Organization adds a second one.
[Feature] Linked Supabase projects receive that environment's keys as Edge Function secrets whenever a key changes, on the retry sweep, and with Sync now, which previews what will be created, updated or deleted before anything is written. Functions see the new values as soon as the sync finishes.
[Feature] ApiVault only changes the Supabase secrets it created. A secret you made yourself with the same name is reported as a conflict, and keys beyond Supabase's 100-secret limit are reported as over limit instead of failing the sync.
[Feature] Unlinking deletes the secrets ApiVault created, and disconnecting also revokes ApiVault's access. If Supabase stops accepting ApiVault, the connection shows Access lost with Reconnect, and owners and admins are notified.
[Improvement] The Integrations catalog has a Supabase card, and the audit log's Integrations group names the platform on every entry, such as Linked Supabase Project or Finished Unlinking Supabase Project.
[Improvement] When Remove anyway leaves many variables or secrets behind, the notice names the first ten and counts the rest instead of listing every one; the audit log still records them all.