docs(migrations): HELD.md records the four holds discharged 2026-09-02 - #1764
Merged
Conversation
Three held migrations were applied to production today by the owner's explicit instruction, and this file is the only place that records a deliberate non-application — so it must also record the discharge, or the rows read "still held" for as long as anyone looks (exactly what rows 34-35 did for two days before 2026-09-01). Applied, each through the repo-local CLI (`./node_modules/.bin/supabase db query --linked -f <file>`), each in its own transaction with its precondition checked inside the transaction, the `supabase_migrations.schema_migrations` row inserted (`created_by` = "owner-authorized direct apply 2026-09-02 (Claude Fable 5.1 session)"), and a post-check: - 20260901140000_trace_cannot_claim_success_while_blind.sql — the header's md5 precondition held (5bfaba551f001460e12e6477c663d18e, len 1074). Verified after: helm_debug_finalize_trace now carries status_downgraded_from (md5 338d5f344491586a6ab416ed0798548a, len 2021); anon and authenticated cannot EXECUTE, service_role can; ledger row present. The row now marks the header fingerprint STALE with the live value, the way row 35 does. - 20260819050000_drop_duplicate_baseball_decision_log_index.sql — precondition held (surviving sibling index present, table had 0 rows). Verified after: baseball_decision_log_meeting_item_idx gone, sibling present; ledger row present. - 20260819051000_baseball_fk_covering_indexes_wave_k2.sql — verified after: all three covering indexes present (tables held 9, 2 and 2 rows); ledger row present. Rows converted the way rows 34-35 were: status becomes "APPLIED — hold discharged (catalog-verified 2026-09-02)", a new verification cell is inserted ending "Historical reasoning follows.", and the original reasoning is kept. No other row touched. Verified locally, exit codes captured: markdown-lint-ratchet 0 (no regressions), document-inventory --check 0 (inventory unchanged), docs:path-drift 0. The production verification itself was read-only against the live catalog after the apply; this commit does not touch a database. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
Updates to Preview Branch (agent/held-md-applied-20260902) ↗︎
Tasks are run on every commit but only new migration files are pushed.
View logs for this Workflow Run ↗︎. |
20260901120000_integrity_completed_round_zero_scored_holes.sql was applied
to production today by the owner's explicit instruction, after the three
recorded in the previous commit. Same route: the repo-local CLI
(`./node_modules/.bin/supabase db query --linked -f <file>`), one
transaction, the header's md5 precondition checked inside it, the
`supabase_migrations.schema_migrations` row inserted
(`created_by` = "owner-authorized direct apply 2026-09-02 (Claude Fable 5.1
session)"), and a post-check.
Precondition held: live md5 ae683fa1797204f933b261714d3dba84, len 3789,
matched the fingerprint the file's header records. Verified after, against
the live catalog: run_integrity_checks md5 f57c6f68206b56f131240d768e00876e,
len 4315; the body carries check 6 and excludes the four QA fixture ids
0b000000-0000-4000-b000-00000000000{1,2,3,4}; anon and authenticated cannot
EXECUTE, service_role can; ledger row
20260901120000:integrity_completed_round_zero_scored_holes present. A
read-only run of check 6's query with the exclusion immediately before the
apply flagged 0 rows, so the next 07:00 UTC run is expected to pass.
Row 38 converted the way rows 34-37 were: status becomes "APPLIED — hold
discharged (catalog-verified 2026-09-02)", a new verification cell is
inserted ending "Historical reasoning follows.", the original reasoning
(main's #1725 text — the branch was cut from that merge commit, so
`git merge origin/main` was already up to date) is kept, and the header
fingerprint is marked STALE with the live value the way rows 35 and 37 do.
No other row touched.
Verified locally, exit codes captured: markdown-lint-ratchet 0 (no
regressions), document-inventory --check 0 (inventory unchanged),
docs:path-drift 0. This commit touches no database.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
njrini99-code
changed the title
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.
What
supabase/migrations/HELD.mdis the only place that records a deliberate non-application, so it must also record the discharge — otherwise a row reads "still held" for as long as anyone looks (rows 34–35 did exactly that for two days before 2026-09-01). Four holds were discharged today. This PR converts their rows the same way rows 34–35 were converted: status becomes APPLIED — hold discharged (catalog-verified 2026-09-02), a new verification cell is inserted ending "Historical reasoning follows.", and the original reasoning is kept. Rows 36–38 only; nothing else in the repo changes.The four rows
20260901140000_trace_cannot_claim_success_while_blind.sql20260819050000_drop_duplicate_baseball_decision_log_index.sql+20260819051000_baseball_fk_covering_indexes_wave_k2.sqldb queryrather thanmigration upprecisely because of the out-of-order stamp caution the row already carried.20260901120000_integrity_completed_round_zero_scored_holes.sqlgit merge origin/mainwas already up to date). The header's pre-apply md5 is marked STALE with the live value.How they were applied (owner's explicit instruction)
Each through the repo-local CLI (
./node_modules/.bin/supabase db query --linked -f <file>), each in its own transaction, with its precondition checked inside that transaction, thesupabase_migrations.schema_migrationsrow inserted (created_by=owner-authorized direct apply 2026-09-02 (Claude Fable 5.1 session)), and a post-check.Verification (read-only against production
qmnssrrolpinvwjjnufo, 2026-09-02, after each apply)20260901140000— precondition held: live md55bfaba551f001460e12e6477c663d18e, len 1074, matched the file's recorded fingerprint. After: md5338d5f344491586a6ab416ed0798548a, len 2021; body containsstatus_downgraded_from;anonandauthenticatedcannot EXECUTE,service_rolecan. Ledger row20260901140000:trace_cannot_claim_success_while_blindpresent.20260819050000— precondition held: survivingbaseball_decision_log_meeting_item_id_idxpresent; table had 0 rows. After:baseball_decision_log_meeting_item_idxgone, sibling present. Ledger row present.20260819051000— after:baseball_postgame_review_items_timeline_event_id_idx,baseball_postgame_reviews_coach_id_idx,baseball_settings_audit_log_actor_coach_id_idxall present (tables held 9, 2 and 2 rows). Ledger row present.20260901120000(~18:40Z) — precondition held: live md5ae683fa1797204f933b261714d3dba84, len 3789, matched the file's recorded fingerprint. After: md5f57c6f68206b56f131240d768e00876e, len 4315; body carries check 6 and excludes the four fixture ids0b000000-0000-4000-b000-00000000000{1,2,3,4};anonandauthenticatedcannot EXECUTE,service_rolecan. Ledger row20260901120000:integrity_completed_round_zero_scored_holespresent. A read-only run of check 6's query with the exclusion immediately before applying flagged 0 rows, so the next 07:00 UTC run is expected to pass.Gates (run locally in the task worktree after each commit, exit codes captured)
node scripts/markdown-lint-ratchet.mjsdocs/scope; run for the record)node scripts/knowledge/document-inventory.mjs --checkDOCUMENT_AUTHORITY_INVENTORY.mdmatches the tracked tree — no regeneration needednpm run docs:path-driftTwo commits:
ea781cc66(rows 36–37) ande15596e00(row 38). This PR touches no database; the production verification above was read-only and is recorded here so each row's claim is checkable.🤖 Generated with Claude Code