sync: v3.2.0 — Supabase fixes, site edit, WP plugin rename, black formatting

- Supabase: fix filters, count_rows, upsert, anon_key optional, meta_url field
- Dashboard: site edit page + PATCH update route
- WP Plugin: rename SEO API Bridge → Airano MCP SEO Bridge
- supabase/client.py: black formatting fix
- .gitignore: exclude BUILD_REPORT.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

env.example

@@ -98,11 +98,26 @@ WORDPRESS_SITE1_ALIAS=mysite
 # N8N_INSTANCE1_API_KEY=your_n8n_api_key
 # N8N_INSTANCE1_ALIAS=myn8n
 
-# --- Supabase ---
-# SUPABASE_PROJECT1_URL=https://xxxxx.supabase.co
-# SUPABASE_PROJECT1_API_KEY=your_supabase_api_key
-# SUPABASE_PROJECT1_SERVICE_ROLE=your_service_role_key
+# --- Supabase (Self-Hosted or Cloud) ---
+# Works with both self-hosted Supabase and supabase.com cloud projects.
+# For cloud: URL is https://xxxx.supabase.co
+# For self-hosted: URL is your Kong gateway (e.g., http://your-server:8000)
+#
+# SERVICE_ROLE_KEY is required (bypasses RLS, full admin access).
+# ANON_KEY is optional — if omitted, SERVICE_ROLE_KEY is used for all calls.
+#
+# Note: postgres-meta tools (list_tables, execute_sql, get_table_schema, etc.)
+# require the /pg/ Kong route or a direct META_URL. These tools do NOT work
+# on supabase.com cloud (postgres-meta is internal only on cloud).
+# PostgREST/Auth/Storage/Functions tools work on both cloud and self-hosted.
+#
+# SUPABASE_PROJECT1_URL=https://xxxx.supabase.co
+# SUPABASE_PROJECT1_SERVICE_ROLE_KEY=your_service_role_key
+# SUPABASE_PROJECT1_ANON_KEY=your_anon_key
 # SUPABASE_PROJECT1_ALIAS=mysupabase
+#
+# Optional: direct postgres-meta URL for self-hosted when /pg/ is not via Kong:
+# SUPABASE_PROJECT1_META_URL=http://localhost:5555
 
 # --- OpenPanel ---
 # OPENPANEL_INSTANCE1_URL=https://openpanel.example.com