Align schema claim gating with migration by joining documents before v3 job claim

[Copilot]

Summary

• Canonical supabase/schema.sql could claim indexing_v3_agent_jobs rows for documents no longer indexed, increment attempts, then drop them in patched_documents, effectively consuming jobs without returning work.

• This updates schema claim eligibility to match migration behavior by enforcing document-state gating before claim/update.

• Schema claim path

  • Added a pre-claim join from indexing_v3_agent_jobs to documents in eligible_jobs.
  • Enforced d.status = 'indexed' at eligibility time (not only during patched_documents update).

• Snapshot guardrail

  • Extended tests/supabase-schema.test.ts assertions to require the schema claim function to include:
    • join public.documents d
    • and d.status = 'indexed'

with eligible_jobs as (
selectj.id, j.document_id, j.attempt_count, j.max_attemptsfrompublic.indexing_v3_agent_jobs j
joinpublic.documents d
ond.id=j.document_idandd.status='indexed'
...
)

Verification

• npm run verify:cheap
• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed
• npm run verify:release before release or handoff confidence claims
• npm run format:check
• npm run check:production-readiness when clinical workflow, privacy, environment, Supabase, source governance, or deployment behavior changed
• npm run check:deployment-readiness when deployment startup, hosting, or rollout behavior changed

Clinical Governance Preflight

Complete this section when the change touches ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output.

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• Change is intentionally surgical: one eligibility join/filter update in supabase/schema.sql plus matching schema snapshot assertions.