Improve flight-finder report links and cron workflow
This commit is contained in:
@@ -9,6 +9,12 @@ Use this skill instead of the old `docs/prompts/dfw-blq-2026.md` prompt when the
|
||||
|
||||
The deliverable target is always a PDF report plus email delivery when the report is complete.
|
||||
|
||||
PDF output rule:
|
||||
|
||||
- Render aggregator booking links for every quoted fare.
|
||||
- Render direct-airline booking links when they were actually captured.
|
||||
- If a direct-airline link was not captured for a quote, say so explicitly in the report instead of implying one exists.
|
||||
|
||||
Freshness rule:
|
||||
|
||||
- Never reuse cached flight-search captures, prior same-day report payloads, earlier workspace artifacts, or previously rendered PDFs as the primary evidence for a new run.
|
||||
@@ -131,4 +137,4 @@ Rules:
|
||||
|
||||
## Prompt migration rule
|
||||
|
||||
The old DFW↔BLQ prompt is legacy input only. Do not treat it as the execution engine. Convert its hardcoded logic into the typed request model and run the skill workflow instead.
|
||||
The old DFW↔BLQ prompt is legacy input only. Do not treat it as freeform execution prose. Its file should contain a literal `use flight finder skill with the following json payload` request so manual runs and scheduled runs stay aligned.
|
||||
|
||||
Reference in New Issue
Block a user