provider-brand-display-reuse

To add a new provider's brand logo, you update the centralized brand label mappings and billing type branches. This extends brand detection through getAPIProvider() so the footer, top logo, and status line display the new provider consistently.

The best way to ensure consistent provider branding is to reuse existing brand display patterns centrally. Derive the brand label solely from getAPIProvider() and propagate it to getLogoDisplayData() and the status line without duplicating logic.

Yes, you can debug and customize per-provider display labels without touching authentication logic. The Skill relies on getAPIProvider() to determine brand labels for the UI while keeping routing and auth logic untouched.

No, adding a new provider does not require updating multiple scattered components. You extend brand detection in a centralized utility, which automatically updates the footer, top logo, and status line provider field consistently.

The brand label may show incorrectly if the brand label mappings and billing type branches are not updated. Ensure the centralized utility correctly maps the new provider through getAPIProvider() to update getLogoDisplayData().

You need to update brand detection logic when adding a new provider's branding to the terminal UI. Update the centralized utility's brand label mappings to ensure the footer, top logo, and status line reflect the new provider.