Hosted relay ghost workflow cannot be deleted

## Summary

A workflow in a hosted Buzz community is no longer visible in Buzz Desktop, but the relay still returns it and the scheduler continues to run it. Deletion is reported as accepted without removing the workflow.

## Affected community

- Community: `zairaa.communities.buzz.xyz`
- Workflow ID: `86cf70ff-d8f8-4c04-8b29-c4f81907777b`
- Workflow name: `Cross-board control pulse`
- Buzz Desktop: `0.4.26`

## Observed behaviour

1. The Desktop Workflows screen shows no workflows.
2. Relay/CLI workflow lookup still returns the workflow definition.
3. A delete request returns `accepted: true`.
4. Subsequent workflow list/get checks still return the workflow.
5. The hosted scheduler continues to execute it.

## Expected behaviour

Deleting the workflow should remove or disable both the relay definition and its scheduler state. A deletion whose backend side effect fails should not be reported as successfully accepted without an actionable error.

## Operator action requested

Please urgently disable or delete this workflow in the hosted relay backend and verify that no enabled scheduler entry remains for the workflow ID above.

Please also investigate the inconsistent state and the false-success deletion response so an owner can recover from this condition through the normal Desktop/CLI flow.

Start by tracing the relay/CLI workflow lookup and deletion flow, then inspect how the hosted scheduler tracks the workflow ID `86cf70ff-d8f8-4c04-8b29-c4f81907777b`. Reproduce the inconsistent state against the affected community and verify that deletion reports backend failures, removes the relay definition, and leaves no enabled scheduler entry.

Written by the indexing model from the issue text.