Agentic news workflows were no-op'ing on scheduled (cron) runs because force_generation defaulted to false and the bash skip logic treated unset env vars as "don't force."

Changes

• Default force_generation/force_translation to true in all 10 workflow .md and .lock.yml files
• Fix bash default for schedule runs — ${EP_FORCE_GENERATION:-} → ${EP_FORCE_GENERATION:-true} so cron-triggered runs (where github.event.inputs is empty) force generation instead of skipping
• Fix breaking news conditional — != "true" → = "false" to match the same semantics
• Fix translate workflow — was unconditionally passing --skip-existing; now respects force_translation flag

The core issue: for workflow_dispatch, the default value populates the input. For schedule triggers, github.event.inputs.force_generation is empty, not the default. So this:

# Before: empty string != "true" → always skips on schedule runs
if [ "${EP_FORCE_GENERATION:-}" != "true" ]; then
  SKIP_FLAG="--skip-existing"
fi

# After: empty string defaults to "true" → only skips on explicit false
if [ "${EP_FORCE_GENERATION:-true}" != "true" ]; then
  SKIP_FLAG="--skip-existing"
fi

Investigation: no hardcoded dates found

All workflows use dynamic dates ($TODAY, timeframe: "today"/"one-week"). The DATE GUARD warnings and analysis-before-noop mandates are already in place.