neotoma has tenant isolation gap in relationship query endpoints
## Summary
The `/list_relationships` and `/retrieve_graph_neighborhood` endpoints call `getAuthenticatedUserId` (confirming a valid session exists) but do not pass the resolved user ID into the Supabase query as an `.eq("user_id", userId)` filter. As a result, queries return rows from all users rather than scoping to the authenticated caller's data.
## Affected code
**`/list_relationships`** (`src/actions.ts`):
- Calls `getAuthenticatedUserId` but does not apply `.eq("user_id", userId)` to the relationships query
- Uses `.or()` string interpolation for entity ID matching without input validation
**`/retrieve_graph_neighborhood`** (`src/ac
Neotoma: Unauthenticated Inspector/API access via reverse-proxy loopback auth bypass
Neotoma provides versioned records that persist across agent runs. From 0.6.0 to before 0.11.1, Neotoma can treat public reverse-proxied requests as local when the app receives them over a loopback socket and no Bearer token is present. In affected deployments, the REST auth middleware can resolve unauthenticated requests as the local development user, making the hosted Inspector and related API surface reachable without credentials. This vulnerability is fixed in 0.11.1.