#1725 I _think_ I might like a guard in the trigger yaml

Problem Statement

I've been working to merge the 4 separate extensions I made for my news-feed into one extension that contains all the workflows, models, reports, and extra bits.

Along the way, deepseek split my workflow into 3, but also left a 4th "full" workflow that calls everything in one. And it added triggers to run on schedule to the shipped yaml.

now that i've finally pulled it to the swamp serve box, it's set up to run all 4, when it probably makes more sense to not - they're overlapping. but I do like the idea of it all being defined, just disabled.

Proposed Solution

add a guard to trigger

trigger: guard: ${ false } # have I mentioned that guard doesn't remind me if true means do it, or if true means don't? schedule: 0 */4 * * *

Alternatives Considered

well, qwen just went and put a guard on all the steps in that workflow, which works, but isn't my intent, as that means the user can't call that workflow manually either.

I could just comment it out - and that's what I'd do if you tell me it's impossibbru, or unreasonabubble.

Additional Context