v2.2.1 logs list view doesn't show fallback chain, only final serving provider

Description

In v2.2.1, the Logs list view only shows the final provider that served the request, not the fallback chain. Previously, fallback attempts were visible in the list view.

Current behavior

When a request goes through fallbacks (e.g. g4f -> Cline -> Fate), the Logs list page shows only one row with the final successful provider (Fate). It looks like Fate was the first provider tried.

The full fallback chain is only visible when opening the session detail view. Even with the Group view enabled, the list page does not show the intermediate fallback attempts.

Expected behavior

The list view should show the fallback attempts (or at least indicate that fallbacks occurred), as it did in earlier versions.

Evidence that backend data is intact

Querying /api/logs directly shows all three attempts with correct fallback_index values:

1. g4f / GithubCopilot:kimi-k3-base, fallback_index=0, error
2. Cline / moonshotai/kimi-k3, fallback_index=1, error
3. Fate / kimi-k3, fallback_index=2, success

So this is a UI aggregation/rendering issue, not a backend fallback execution issue. The data is in the database; the list view just doesn't render it.

Version

• UI/Service version: v2.2.1
• Deployment: Docker image maximhq/bifrost:v2.2.1

Notes

The v2.2.1 release notes mention "Log and Dashboard Label Truncation" (#7215, #7216, #7217, #7269, #7297) which touched the logs table display, but there is no documented change to fallback chain display. This may be an unintended side effect of that UI change.