rc6: gateway routes account-scoped paths to auth_service (labels/contacts/inboxes 404, UI shows empty)

[dvlexp]

Version

1.0.0-rc6 (self-hosted, Docker Swarm, microservices)

Summary

After upgrading rc5 → rc6, several resources render empty in the UI although the data is intact in the DB (contact tags/labels not showing in the conversation sidebar, contact search returning nothing, the merge screen finding no contacts, inbox list empty).

Root cause

rc6 migrated crm_service routes from account-scoped (/api/v1/accounts/{account_id}/X) to global (/api/v1/X), but the deployed frontend still calls the account-scoped paths for ~7 resources: labels, contacts, contacts/search, contacts/filter, inboxes, agent_bots, automation_rules.

The gateway makes this worse: the nginx location regex for the auth service is roughly

location ~ ^/api/v1/(auth|profile|users|...|account) { proxy_pass $auth_service; }

The account alternative has no trailing anchor, so it matches ^/api/v1/accounts/... as a prefix and nginx (first-match by file order among regex locations) forwards all account-scoped requests to auth_service, which doesn't serve them → 404. The vendor's own ^/api/v1/accounts$ / ^/api/v1/accounts/[^/]+/webhooks blocks below it become dead code.

Expected

Frontend and backend contract should match; account-scoped requests for these resources should reach crm_service (or the frontend should call the global paths).

Impact

High — core CRM workflows (tags, contact search, merge, inbox list) appear broken to end users on a clean rc6 deploy, even though the data exists.