Custom database schemas are not displayed in Supabase Studio API documentation (self-hosted)

**Describe the bug** In a self-hosted Supabase stack, custom database schemas (e.g., `dsoftautocheck`) are correctly exposed via PostgREST and are accessible via REST API and Postgres Meta endpoints. However, Supabase Studio does not display the tables from these custom schemas in the API documentation panel (API Docs), even though the backend is configured and functioning properly. **To Reproduce** Steps to reproduce the behavior: 1. Create a custom schema in Postgres (e.g., `CREATE SCHEMA dsoftautocheck;`). 2. Grant all necessary permissions to `anon`, `authenticated`, `service_role`, and `supabase_admin`. 3. Add the schema to `PGRST_DB_SCHEMAS` and `PG_META_DB_SCHEMAS` environment variables in `.env` and `docker-compose.yml`. 4. Restart all services (`rest`, `meta`, `studio`). 5. Confirm via API and meta endpoints (`/rest/v1/`, `/pg/schemas`, `/pg/tables?included_schemas=dsoftautocheck`) that the schema and tables are exposed and accessible. 6. Open Supabase Studio and navigate to API Docs or Table Editor. 7. Observe that the tables from the custom schema do not appear in the UI/documentation, even though all backend endpoints return them correctly. **Expected behavior** Custom schemas added to `PGRST_DB_SCHEMAS` and `PG_META_DB_SCHEMAS` and exposed via PostgREST/Meta should be visible in Supabase Studio's Table Editor and API Docs panels, similar to the `public` schema. **Additional context** - Supabase version: (docker images: Studio, PostgREST, Meta, etc. from latest as of Oct 2025) - All permissions and roles confirmed; tables accessible via API but not visible in Studio. - Cache cleared and Studio restarted, but issue persists. **Labels:** bug, documentation --- This issue was reproduced and validated multiple times. Please advise if there is an additional configuration step required or if this is a bug in Supabase Studio.