Skip to content

docs(operator): mark July-8 ingestion/tenancy batch verified live#528

Merged
BigSimmo merged 1 commit into
mainfrom
claude/july8-migration-batch-live-7d76fb
Jul 12, 2026
Merged

docs(operator): mark July-8 ingestion/tenancy batch verified live#528
BigSimmo merged 1 commit into
mainfrom
claude/july8-migration-batch-live-7d76fb

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

Stamps the July-8 batch operator runbook as verified live. Closes the verification
half of task 1.1 (apply + verify PRs #380/#405/#408/#409 on production).

Docs-only — no code, schema, migration, or behavior change. The migration files
themselves are unchanged.

What was verified (read-only, against production Clinical KB Database sjrfecxgysukkwxsowpy)

All six batch migrations were already applied on live (apply = no-op; live history
carries them plus ~15 later migrations). Batch probes replicated as read-only SQL — all green:

  • retrieval_owner_matches fail-closed truth table (NULL→false, sentinel/owner isolation correct)
  • jsonb_merge_deep deep-merges (R5, fix(ingestion): R5 — deep-merge document metadata instead of full replace #408)
  • complete_ingestion_job accepts p_worker_id lease fence (R1/R2, step 2)
  • R17 ingestion_jobs_one_open_per_document_uidx — partial-unique on (document_id) WHERE status IN (pending,processing), indisvalid/indisready true, queue 0/0

Clinical governance note

No ingestion / answer-generation / retrieval / access / privacy code is touched — this PR
only edits an operator markdown doc. Verification was performed read-only via the Supabase
connector; nothing was written to the database. The one retrieval-affecting migration
(retrieval_owner_matches fail-closed) was proven correct on live and its sentinel path — the
one the golden eval exercises — is unchanged.

Remaining (not in this PR)

Ingestion worker redeploy (Railway) so R5 merge + p_worker_id fences are active
end-to-end — an operator/deployment step, low-urgency (worker code already passes p_worker_id).

🤖 Generated with Claude Code

All six batch migrations (20260708 130000/140000/150000/160001/170000/310000)
are already applied on production Clinical KB Database (sjrfecxgysukkwxsowpy);
apply was a no-op. Verified read-only on live: retrieval_owner_matches
fail-closed truth table, jsonb_merge_deep deep-merge, complete_ingestion_job
p_worker_id lease fence, and the R17 partial-unique index (indisvalid/indisready
true, queue 0/0). Stamp the runbook so the batch is not re-applied; apply steps
retained for staging/DR replay. Remaining: ingestion worker redeploy.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ab500ed2-87b4-4653-b43b-9e89d04b519b

📥 Commits

Reviewing files that changed from the base of the PR and between 33edba1 and c78a4d7.

📒 Files selected for processing (1)
  • docs/operator-apply-july8-batch.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/july8-migration-batch-live-7d76fb
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch claude/july8-migration-batch-live-7d76fb

Comment @coderabbitai help to get the list of available commands.

@supabase

supabase Bot commented Jul 12, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c78a4d7ff5

ℹ️ 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".

Comment thread docs/operator-apply-july8-batch.md
@BigSimmo
BigSimmo enabled auto-merge (squash) July 12, 2026 17:40
@BigSimmo
BigSimmo merged commit 837e310 into main Jul 12, 2026
15 of 16 checks passed
@BigSimmo
BigSimmo deleted the claude/july8-migration-batch-live-7d76fb branch July 13, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant