When the Editor Analyzes the Wrong Files: Building the Pipeline That Built This Series

I ran a cross-post editorial pass across five blog posts — checking territory overlap, duplicate quotes, voice consistency, series continuity. The AI reviewer in my IDE produced four findings, cleanly prioritized: one high, two medium, one low. I sent them to a second AI environment for adversarial review. It validated all four. Everything agreed. I was about to execute the edits. Then someone said "take a review to see if that makes sense." I re-read the actual files. Three of four findings were phantom problems. The editorial pass had run against the wrong versions — benchmark drafts from an earlier pipeline stage, not the current drafts it was supposed to be evaluating. The benchmarks had territory encroachment, weak closers, and missing series callbacks. The current drafts had already solved all three problems independently. The edits I was about to make would have introduced problems into clean files to fix issues that only existed in files I wasn't publishing. That moment — confi