fix: audit SQL remediation (worker URL + grants) after main sync#1197
Conversation
- Added security revokes to schema - Implemented deterministic pre-classifier for RAG - Fixed CSS layer order for globals - Resolved test latency and timeout issues - Fixed responsive layout regressions
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 33 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Merge origin/main into execute-system-audit-remediation tip and drop the bad conflict resolutions that removed clinical-notes trust gating, broke the summaryMode stream-required contract, and introduced an unattested RAG pre-classifier. Retain the additive hosted remediation migration that restores the real ingestion-worker URL (replacing main's [REDACTED] fallback), reasserts ISSUE-05 execute revokes, and regenerates the drift manifest from the updated schema.sql.
Record sync-to-main outcome, restored clinical contracts, dropped unattested RAG pre-classifier, and retained SQL URL remediation only.
Reassert service_role EXECUTE after CREATE OR REPLACE for invoke_ingestion_worker and the ISSUE-05 invoker RPCs, align schema.sql trailing ACL with the migration, and regenerate the drift manifest.
Sync with main, fix the ambiguous reviewed-head separator to the established `<head> / squash <sha>` form, record the ledger check in Checks, and drop the exact duplicate row from the union merge.
Summary
Fixes PR #1197 after Bugbot / local review found merge-conflict regressions. Branch is synced to current
main. Product/clinical/RAG surfaces matchmain(trust-gated clinical notes, stream-required summaryMode, no ISSUE-07 pre-classifier). Remaining delta is additive hosted SQL remediation plus ledger.What remains vs main
supabase/migrations/20260725000000_audit_security_remediation.sql— restores realsjrfecxgysukkwxsowpyingestion-worker URL (replacing[REDACTED]fallback from Fix Database↔Supabase interface audit findings (#052, #062, schema hygiene, table-facts latency) #1133), reasserts ISSUE-05 execute revokes andservice_rolegrants, ISSUE-04 table/sequence revokes, and reasserts grants afterCREATE OR REPLACEsupabase/schema.sql— same URL fix + ISSUE-05 revoke/grant trailsupabase/drift-manifest.json— regenerated via Dockerdrift:manifestdocs/branch-review-ledger.md— review/fix recordWhat was removed / restored from bad conflict resolutions
trustGatedAnswerForClinicalNotes+ ClinicalNotes boundary testssummaryMode→400 summary_mode_stream_requiredcontractrag.tsidentical to main)canonicalAuthority/identityAuthorityreferences (undefined → 500)docs/outstanding-issues.mdand process tooling from mainRAG impact: no retrieval behaviour change — tip matches main RAG path; no
src/lib/rag/**delta remains.Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)Verification
npm run check:migration-rolenpm run drift:manifestregenerated (Docker scratch replay)npm run check:branch-review-ledgerRisk and rollout