Add daily_data to _UPSTREAM_MAX_AGE_H (belt-and-suspenders with #53)

[cipher813]

Summary

Closes the stamp-side of the belt-and-suspenders daily-data freshness architecture:

Gate	Catches	Origin
`_UPSTREAM_MAX_AGE_H` stamp check (this PR adds `daily_data: 26`)	"ran and failed today" with structured reason	reads `health/daily_data.json` written by alpha-engine-data#41
Direct `LastModified` on `daily_closes/{date}.parquet` (#53)	"stamp green, blob stale"	head_object in main.py

The stamp alone is insufficient — producer self-reporting can lie. The LastModified check alone misses structured failure state. Having both closes both holes.

Change

One-liner in `executor/main.py:894` — adds `"daily_data": 26` to `_UPSTREAM_MAX_AGE_H`. 26h matches `predictor_inference` since both run at the same weekday 13:05 UTC cadence.

Deploy order — IMPORTANT

1. First: merge alpha-engine-data#41 — data stamps start emitting on next weekday run (Mon 13:05 UTC)
2. Wait for at least one weekday DailyData run to produce `health/daily_data.json`
3. Then: merge this PR — executor begins enforcing the stamp gate

If this merges first, every executor run hard-fails with `daily_data: no health data returned` until DataPhase1 emits its first stamp. Keep this PR blocked until #41 has deployed AND been exercised on a weekday.

Pairs with

• alpha-engine#53 — direct LastModified check on daily_closes.parquet
• alpha-engine-data#41 — emits `health/daily_data.json`
• alpha-engine-predictor#33 — same LastModified check on the predictor side

Test plan

• Full suite: 228 passed / 0 failed
• Pre-push dry-run gate passed
• Post-merge (after [ERROR] executor: Error 10197, reqId 263: No market data during competing live session, contract:  #41 has run on a weekday): next executor run logs `daily_data: ok / age_hours: ` in upstream health check
• Failure injection: if DataPhase1 writes `status: failed` stamp, executor should hard-fail with Telegram notification

🤖 Generated with Claude Code