Revert: AI summary enrichment backfill (slice 3) (#113) - #114
Merged
Conversation
This reverts commit 8fadf84.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Auto-revert of #113. Post-merge production verification (mcpfind-recovery-driver, per Step 4 of the SKILL.md gate pipeline) found that every
/servers/[slug]detail page began returning HTTP 404 on mcpfind.org immediately after the merge, while/serversand/categorieslist pages remained healthy (HTTP 200).Root cause
apps/web/lib/queries.ts'sSERVER_DETAIL_COLUMNSwas changed toselect()two new columns (ai_summary,ai_summary_generated_at) added by migrationsupabase/migrations/006_ai_summary.sql. That migration file was added to the repo but was never applied against the live production Supabase database — this repo's CI/CD has no migration-apply step. The Supabase query for the detail page therefore fails at runtime (columns don't exist in the live schema),getServerBySlugreturns null, and the page callsnotFound().This is a case of green CI / green Vercel preview masking a real production integration failure — build-time type-checks and tests don't hit the real production database schema, so nothing caught the missing-migration gap before merge.
What this PR does
Straight
git revertof the squash-merge commit8fadf84378dbe88dfffa62ae88188151fe0630cf— removes the migration file, the backfill script, and the page/query changes. No manual conflict resolution needed (clean revert).Follow-up (not in this PR)
Before re-attempting slice 3: migration 006 needs an actual apply step against production Supabase (e.g.
supabase db pushor equivalent), and the column-select change should only ship once the columns provably exist live — ideally the Validator's pre-merge check should include a live schema check against production Supabase, not just CI type-check + Vercel preview build success.🤖 Generated by the mcpfind-recovery-driver auto-merge harness.