Day One of the Content Pipeline: What Broke and What I Fixed

Ahnii! Yesterday's post walked through automating a content pipeline with GitHub Actions and Issues. The idea: a daily scheduled job scans recent commits and closed issues across several repos, filters out the noise, and opens what's left as GitHub issues labeled stage:mined. One of those issues looks something like this: Title: [content] feat: add SovereigntyProfile to Layer 0 Body: ## Source Commit `abc1234` in `waaseyaa/framework` ## Content Seed feat: add SovereigntyProfile to Layer 0 ## Suggested Type text-post Those issues are raw material. You curate them into drafts, produce the copy, and publish. That surfacing step is what the rest of this post calls mining. This post is about what happened the first time I actually ran that pipeline. The short version: it works, but the first real run turned up three problems no amount of planning could have caught. Here are the three fixes and the meta-lesson underneath them. Day One Output: 20 Issues, Too Much Noise The mining workflow fir