fix(freshness-deploy): use file:// for historical-cron put-targets

[cipher813]

Summary

deploy.sh --bootstrap was tripping on the put-targets shorthand when the Input contains JSON. From PR #339 the historical cron's target carries Input={"mode":"historical"}; the shorthand form Id=N,Arn=...,Input={...} confuses argparse on the embedded quotes + comma.

Caught live 2026-05-28 when --bootstrap re-run partial-fired:

ParamValidation: Error parsing parameter '--targets': Expected: '=', received: '"' for input

Switch to a temp-file JSON spec via file://.

Live state

The historical EB cron IS wired live in AWS (target attached manually via direct CLI during this session with the same JSON). First daily firing at 04:00 UTC tomorrow. This commit ensures the next operator who runs --bootstrap from main doesn't trip the same trap.

Verification

aws events list-targets-by-rule --rule alpha-engine-freshness-monitor-historical-cron \
  --query 'Targets[].{Id:Id,Input:Input}'
[{"Id": "1", "Input": "{\"mode\":\"historical\"}"}]

bash deploy.sh --bootstrap --dry-run
DRY: aws events put-targets --rule alpha-engine-freshness-monitor-historical-cron \
     --targets file:///tmp/tmp.KUaF4o3som --region us-east-1

Composes with

• PR feat(freshness-monitor): historical-mode probe — daily gap detection across all artifacts #339 (historical-mode substrate + new EB cron)
• PR feat(freshness-monitor): template-aware trading-day-axis resolution for historical probe #341 (template-aware probe)

🤖 Generated with Claude Code