Omair Saleh
056c47581f
Ships the second dashboard surface — a Pattern Library + Preview Theatre — that presents the 4-section PDP pilot batch back to Umar, compliance, and the board in an editorial format. Adds the full data layer that drives it: 5 source-backed per-SKU drafts at QA 100/100, 15 competitor PDP semantic extracts, PubMed evidence packs, EFSA claims library extension, JV brand voice guide, hand-curated product FAQs, and the Matrixify-ready CSV exports for Lewis. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Apify paid actor preflight
Generated: 2026-05-20T02:31:32.595Z
Ready to run Apify Stage 2 actor: NO
This preflight is a final local guard before any Apify paid actor run. It does not call Apify.
Checks
- [blocked] Explicit paid-run flag set — set JV_SOURCE_ALLOW_PAID=apify-stage2 only when intentionally running Apify Stage 2
- [blocked] Apify token present in environment — APIFY_TOKEN=missing
- [blocked] Spend gate allows Apify Stage 2 — 4/14 spend checks passing
- [blocked] Budget gate allows Apify Stage 2 — 6/9 budget checks passing
- [blocked] DataForSEO review explicitly selected Apify — decision=pending
- [blocked] Named Apify gap documented — no named gap from DataForSEO pilot review
- [pass] First batch stays inside caps — 3 first-batch targets, 4 held, maxActorRuns=1, maxTargets=3, maxRequestsPerBrand=3
- [pass] Actor input matches first batch only — 3 start URLs / 3 first-batch targets, maxRequestsPerCrawl=9, maxCrawlDepth=1
Paid-run rule
- All checks must pass.
APIFY_TOKENmust be a shell environment variable only.JV_SOURCE_ALLOW_PAIDmust equalapify-stage2for the run window.- DataForSEO pilot review must explicitly choose
run_apify_gapfilland name the gap. - Run only the first-batch input template, then stop and inspect dataset quality/cost before any scale-up.