chore(issues): record the migration-replay vs schema.sql mirror gap on #QCNE6N - #2492
Conversation
…nding Root-caused from live-drift run 33484535655 on main at d307494. CI's db-reset-verify job replays the migration chain and regenerates the drift manifest, but only asserts that schema.sql did not change without a manifest refresh. Nothing asserts that the replayed chain equals schema.sql, so a migration that edits a function body without a matching schema.sql edit clears every pre-merge gate and only surfaces post-merge in live-drift. Append-only inbox request; the canonical ledger is untouched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_1e41c388-1956-41e8-b3a2-c1504a724dc1) |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…QCNE6N The finding queued in the previous commit is already an open row. #QCNE6N (P2, 2026-08-23) records that CI never diffs the replayed migration chain against supabase/schema.sql, and already proposes the same containerised two-database fix. Caught by checking the ledger after queueing rather than before. Retract the duplicate add via the inbox's own cancel action, and reissue the 2026-09-01 evidence as an update to #QCNE6N: live-drift run 33484535655 is the first time this gap has actually produced a live/repo divergence, which moves the row from theoretical to demonstrated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BigSimmo
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 243b861d92
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Summary
addrequest via the inbox's owncancelaction.updateto the existing open row#QCNE6Ninstead.No product code, no database migration, no schema change. The canonical ledger
docs/outstanding-issues.mdis untouched; these are immutable request files underdocs/outstanding-issues-inbox/, to be applied later by a serializednpm run issues:reconcile.What happened
The first commit on this branch queued an
addfor a pre-merge verification gap found while classifying today'slive-driftfailure. That gap is already an open row:#QCNE6N(P2, 2026-08-23) records that CI never diffs the replayed migration chain againstsupabase/schema.sql, and already proposes the same containerised two-database fix. The duplicate was caught by checking the ledger after queueing rather than before, and is retracted in the same session it was created.The later commits cancel that request and reissue its content as an update to
#QCNE6N. Theaddrequest file is left in place rather than deleted, because the inbox is append-only andcancelis its designed retraction path; reconciliation drops the cancelled request.The evidence added to
#QCNE6Nlive-driftrun33484535655(2026-09-01, onmainatd3074946a) is red with exactly one unexpected finding:public.correct_clinical_query_terms(text,real)def_hashmanifeste2356565…versus live2ebaf978….The cause is a mirror gap, not a live-database problem. Migration
20260831100000(merged in PR #2477) redefined that function with a duplicatedand length(canonical) between 4 and 40predicate, andsupabase/schema.sqlwas never updated to match. The drift manifest is generated by replayingschema.sqlinto the pinned Postgres image, so the manifest and live disagree even though live is exactly what the applied migration created.That makes
#QCNE6Ndemonstrated rather than theoretical. The onlydb-reset-verifyassertion that runs today iscommitted.schema_sha256 === generated.schema_sha256, which catches an unrefreshed manifest but not a chain-versus-mirror divergence. Behaviour impact of this instance is nil — the duplicated predicate is a boolean no-op — but it cost a red daily alarm and a remediation PR, and it is the second occurrence of the failure class behind the original#316root cause.The remediation for the drift itself is a separate change and is not in this PR.
Verification
Documentation and ledger paperwork only.
npx prettierreports all three added files unchanged (already formatted). No unit, build, browser, or provider-backed check was run, because this diff contains no executable code and there is no realistic changed failure path in append-only JSON request files.npm run check:ledger-write-disciplinein CI is the gate that governs this path.No live Supabase, OpenAI, or Railway access was used at any point in producing this PR.
🤖 Generated with Claude Code