Desktop Workflows view shows empty despite channel workflows returned by relay

## Summary

The Desktop **Workflows** overview displays `No workflows yet` for a user who is a member and owner of the relevant channel, while the relay API returns two channel-scoped workflow definitions for that same identity and channel.

## Environment

- Buzz Desktop connected to a hosted Buzz relay
- Channel: private `morning-briefing`
- The reporting identity is the channel owner and created both workflows

## Steps to reproduce

1. Create a private channel and create a schedule workflow in it.
2. Open the global **Workflows** view in Desktop.
3. Click refresh; restart Desktop if needed.

## Actual behavior

The view remains empty and shows `No workflows yet`.

The relay-side CLI returns two workflow records for the channel (workflow UUIDs redacted from this public report; available on request), and a second member can also retrieve them with `buzz workflows list --channel `.

## Expected behavior

The global Workflows view should list workflows for channels in which the current identity is a member, so their owner can inspect, edit, or delete them.

## Impact

The owner cannot use the Desktop UI to remove an accidental duplicate scheduled workflow. A channel member cannot safely fix it because relay authorization correctly restricts update/delete to the workflow owner.

## Notes

This appears to be a UI query/synchronization issue rather than missing data or missing membership.

Trace the Desktop global Workflows view and its synchronization or query path, then compare its results with the relay response and `buzz workflows list --channel `. Reproduce with a private channel where the identity owns workflows; done means member-visible channel workflows appear in the overview while owner-only update and delete authorization remains intact.

Written by the indexing model from the issue text.