coordinate jobs: daily pipeline orchestrator runs the flow in order

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>

frontend/src/api/admin.ts

@@ -162,6 +162,7 @@ export interface JobStatus {
   label: string;
   enabled: boolean;
   next_run_at: string | null;
+  via_pipeline?: boolean;
   registered: boolean;
   running?: boolean;
   runtime_status?: string | null;

frontend/src/components/admin/JobControls.tsx

@@ -146,10 +146,14 @@ export function JobControls() {
                             ? 'Active'
                             : 'Inactive'}
                   </span>
-                  {job.enabled && job.next_run_at && (
-                    <span className="text-[11px] text-gray-500">
-                      Next run {formatNextRun(job.next_run_at)}
-                    </span>
+                  {job.via_pipeline ? (
+                    <span className="text-[11px] text-gray-500">runs in daily pipeline</span>
+                  ) : (
+                    job.enabled && job.next_run_at && (
+                      <span className="text-[11px] text-gray-500">
+                        Next run {formatNextRun(job.next_run_at)}
+                      </span>
+                    )
                   )}
                   {!job.registered && (
                     <span className="text-[11px] text-red-400">Not registered</span>