Improve flight-finder report links and cron workflow

docs/flight-finder.md

@@ -11,6 +11,7 @@ Reusable flight-search report skill for OpenClaw. It replaces the brittle one-of
 - use bounded search phases across KAYAK, Skyscanner, Expedia, and a best-effort airline direct cross-check
 - normalize pricing to USD before ranking
 - produce a report payload first, then render PDF/email only when the report is complete
+- render booking links in the PDF for each recommended fare, including airline-direct links when they were actually captured
 - behave safely on WhatsApp-style chat surfaces by treating status nudges as updates, not resets
 - require a fresh bounded search run for every report instead of reusing earlier captures
 
@@ -27,6 +28,15 @@ Reusable flight-search report skill for OpenClaw. It replaces the brittle one-of
   - If omitted, no VPN change happens.
 - If VPN connect or verification fails, the run falls back to the default market and records a degraded warning instead of hanging.
 - Direct-airline cross-checking is currently best-effort, not a hard blocker.
+- The PDF should show:
+  - the captured booking/search link for every quoted fare
+  - the airline-direct link only when `directBookingUrl` was actually captured
+  - an explicit “not captured in this run” note when direct-airline booking was unavailable
+
+## DFW ↔ BLQ daily automation
+
+- The 6 AM DFW ↔ BLQ automation should invoke `flight-finder` directly with the structured JSON payload.
+- The legacy file at `workspace/docs/prompts/dfw-blq-2026.md` should mirror that exact direct skill invocation, not old prose instructions.
 
 ## Helper package