weekly-cannibalization-fix — 2026-04-23 (HARD FAIL, aborted)

Disposition: ABORTED at preflight. No writes, no GSC API calls, no redirects proposed.

Pending QA items: see /Users/samaguiar/Documents/Codex/_qa-queue/2026-04-23.md

Run report: /Users/samaguiar/Documents/Codex/cannibalization/2026-04-23.md

Preflight result

Required artifact: /Users/samaguiar/Documents/Codex/screaming-frog-ingest/*.md
Max age: 192 hours
Result: MISSING (the directory does not exist)
Allow-missing: not set. Task has no fallback path.
Disposition per guard contract: HARD FAIL, exit 2, no partial report pushed.

Why this matters

The cannibalization task needs Screaming Frog crawl data to cross-reference GSC query/page overlap against actual content overlap (title, H1, intro). Without the SF ingest, a GSC-only run flags false positives and misses true consolidation candidates.

The upstream chain is:

screaming-frog-crawl / technical-seo-crawl-audit
        ↓
screaming-frog-ingest/YYYY-MM-DD.md
        ↓
weekly-cannibalization-fix  (this task)

The chain is broken at the first hop. No ingest output landed in Codex/screaming-frog-ingest/.

Pending QA items (triage at session start in Codex queue, not here)

Q1 — How to resolve the missing SF ingest dependency (recommend: schedule the ingest to write to the expected path and keep this guard).
Q2 — Guard script portability (recommend: make _guards/staleness-guard.sh sandbox-aware so it works in both macOS launchd and Cowork Linux sessions).
Q3 — Confirm the task prompt still matches Sam's intended procedure (recommend: yes, keep the SF cross-reference step).

Full MC options and rationales are in the Codex queue file. This Notion entry is storage-only; Sam triages in the queue per environment-wide Notion-is-not-a-workflow-surface rule (2026-04-23).