feat: promote all indexed documents public regardless of validation status

[BigSimmo]

Summary

Removes the clinical_validation_status gate that kept ~130 unverified indexed documents private. Public access is already keyed on owner_id IS NULL; this change updates promotion tooling and adds a follow-up migration so the full indexed corpus can be made public.

Changes

• scripts/promote-public-documents-batch.ts — promote any owned indexed document, not only locally_reviewed / approved.
• scripts/promote-public-documents.ts — same candidate filter removal; updated operator guidance.
• supabase/migrations/20260706120000_promote_remaining_indexed_documents_public.sql — one-shot migration to promote all remaining owned indexed documents and cascade owner_id = null to related artifact tables.

The earlier migration 20260705220000_promote_locally_reviewed_documents_public.sql is left as-is (already applied on live).

Post-merge rollout

On the linked Supabase project (sjrfecxgysukkwxsowpy):

npm run promote:public-documents:batch
# or
npx supabase db push --linked

Expected result: all ~2,065 indexed documents public (owner_id IS NULL); ~130 currently unverified owned docs promoted.

Notes

• Read APIs (withOwnerReadScope) were already validation-status agnostic — this fixes promotion/data, not route logic.
• Source governance warnings for unverified sources in answers are unchanged (clinical safety).

  

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy due to reaching the limit of concurrent preview branches.
Go to Project Integrations Settings ↗︎ if you wish to update this limit.

---

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

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Batch promotion skips artifact cascade
  • Updated promoteBatch to set metadata.public_corpus and null owner_id on all eight artifact tables so batch promotion matches the migration cascade.

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 6b47aa1. Configure here.}