e982487abd
Jobs were independent 24h timers with no ordering, so the scanner could run on stale OHLCV, and manual runs desynced the offsets. New daily_pipeline job runs the data→signal flow in dependency order: OHLCV → fundamentals → sentiment → R:R scan → outcome eval (+paper close) → market regime. Each step keeps its own enable flag and runtime status; a failing step is logged and the pipeline continues. The member jobs are registered PAUSED (no auto-fire) so they only run via the pipeline — but stay manually triggerable from Admin → Jobs (shown as "runs in daily pipeline"). Alerts (hourly), ticker universe sync, and backtest keep their own independent cadence. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>