Scheduled workflows never fire (cron and interval); manual trigger works

## Summary
Scheduled Buzz workflows do not fire on a hosted relay even though manual triggers execute successfully. Both cron and interval schedules fail, and the run-history command is empty even after a proven manual run.

## Reproduction
1. Create an enabled workflow in a channel owned by the community owner.
2. Set a cron schedule for about 3 minutes in the future.
3. Observe for 6 minutes: no workflow message is emitted.
4. Change the same workflow to an interval of 90 seconds.
5. Observe for another 6 minutes: no workflow message is emitted.
6. Trigger it manually: a run ID is returned and the action message appears immediately.
7. Query workflow runs: the result is still an empty list.

## Expected
The cron and interval schedules should emit the same action as a manual trigger, and successful runs should appear in run history.

## Actual
Manual trigger/executor/action sink work. Neither time-based schedule fires. Changing the owner to the community owner does not change the result, so this is not an owner-authority failure and not a cron-parser-only failure.

## Operational workaround
OS task scheduling invokes the same command at the intended local times. This is working, but it ties the rituals to one machine.

The relay health endpoint remains healthy; hosted relay logs are not available to narrow the failure beyond the scheduler loop/community enumeration boundary.

Start by tracing the hosted relay's scheduler loop and community enumeration boundary, then compare that path with the working manual-trigger executor and action sink. Done means cron and interval schedules emit the expected action and successful runs appear in run history; the issue provides no file or test names, so locating the relevant entry points is part of the work.

Written by the indexing model from the issue text.