Brave Search API

### App
Brave Search API

### Summary:
Brave Search account is listable but fails on /proxy with "App record not found"

### Details:
On March 26, 2026, we reproduced the following:

1. Listing connected accounts succeeds for `brave_search_api`:
- We call the Connect accounts flow for the user/app combination above.
- It returns account `apn_vMhVbvp`.
- The returned account metadata shows:
- `app.name_slug = "brave_search_api"`
- `app.name = "Brave Search API"`
- `healthy = true`
- `connect.proxy_enabled = false`

2. Proxying a request with that same account fails:
- We then call the Connect proxy route using that same connected account
to proxy:
`GET
https://api.search.brave.com/res/v1/web/search?q=Brave+Search+API&count=1`
- Pipedream responds upstream with HTTP 400:
`{"error":"App record not found"}`

3. On our side this surfaces as:
- app/container logs: HTTP 502 wrapping the upstream Pipedream 400
- public edge response: HTTP 504, with an App Platform page indicating
`via_upstream (502 -)`

Why this seems wrong/confusing
- The account is real, healthy, and listable for `brave_search_api`.
- Its canonical app slug also matches `brave_search_api`.
- But the same account cannot be used with the Connect proxy route.
- The returned metadata also says `connect.proxy_enabled = false`.

### Screenshots:
No screenshots included