## Bug Report

### Version Tested on v1.86.0, v1.86.1, v1.87.0-rc.2 — all affected.

### Description Setting `object_permission` on a project via `/project/update` always returns 500. The same field works correctly on `/key/update` and `/team/update`.

### Minimal Repro

```bash curl -X POST http://<litellm-host>/project/update \ -H "Authorization: Bearer <admin-key>" \ -H "Content-Type: application/json" \ -d '{ "project_id": "<valid-project-id>", "object_permission": { "mcp_servers": ["<valid-mcp-server-id>"] } }' ```

Response: ```json {"error":{"message":"Could not find field at `createOneLiteLLM_ObjectPermissionTable.data`","type":"internal_server_error","param":"None","code":"500"}} ```

A plain update without `object_permission` (e.g. just `description`) returns 200.

### Stack Trace (from pod logs)

``` litellm_enterprise/proxy/management_endpoints/project_endpoints.py:682 await prisma_client.db.litellm_objectpermissiontable.create(data=object_permission_data)

prisma.errors.FieldNotFoundError: Could not find field at `createOneLiteLLM_ObjectPermissionTable.data` ```

### Root Cause

`project_endpoints.py` calls `litellm_objectpermissiontable.creat…