Business registry failure blocks domain listing for users

[vohmar]

Problem

When the backend request to the business registry (äriregister) fails, the registrant
portal fails to show any domains to the user — including domains the user is directly
associated with (as registrant, admin contact, or tech contact).

Expected Behaviour

A failed or unavailable business registry request should not prevent users from seeing
their directly-associated domains. Domain listing (/api/v1/registrant/domains) must
work independently of the business registry lookup (/api/v1/registrant/companies).

Current Behaviour

If the business registry is unavailable or returns an error, the entire domain list is
empty for the user even though the user's own domains are stored in the registrant API
and can be retrieved without consulting the business registry.

Impact

• Users cannot see or manage their own domains during any business registry outage or
  transient failure.
• This is a hard dependency that degrades the portal's core functionality unnecessarily.

Proposed Fix

• Decouple the business registry request from the domain listing flow on the backend
  (registrant API side).
• If the business registry call fails, the domain listing should still return the user's
  directly-associated domains.
• Optionally show a warning/notice on the Companies page when business registry data is
  unavailable, but this must not block the domain listing page.

Relevant Code

• Frontend domain fetching: src/redux/reducers/domains.js → fetchDomains
• Frontend companies fetching: src/redux/reducers/companies.js → fetchCompanies
• Server proxy routes: server/routes/apiRoute.js → getDomains / getCompanies
• The root cause is likely in the upstream registrant API (API_HOST) where a business
  registry call appears to be interleaved with or block domain lookups.

[sophymarine]

This is a good example of a registry dependency becoming part of the product surface instead of a hidden backend detail. When that lookup fails, the user experience should degrade gracefully, not collapse the whole domain view. OpenRegistry is built around that same concern for compliance workflows: live company registry checks, source-linked filings, and officer or PSC data without inventing a synthetic summary. If you need a direct multi-jurisdiction registry layer to compare against your current implementation, https://openregistry.sophymarine.com/mcp is the relevant endpoint.