Preserve active indexing-v3 processing locks during strict-gate seeding

[Copilot]

Summary

• Strict-gate repair could rewrite actively locked indexing_v3_agent_status='processing' rows to deferred/pending metadata during seeding, making them immediately claimable by another worker and duplicating enrichment work.
• Behavior change (repair path): in repair_strict_enrichment_gate_batch, non-passed gate rows now preserve processing state when the existing indexing_v3_agent_locked_at is still within the active lock window; stale/missing locks continue to flow to deferred/pending.
• Parity updates: applied the same logic in both migration SQL and supabase/schema.sql snapshot to prevent drift.
• Regression guard: extended schema assertions to require the active-processing branch and enrichment_status='processing' preservation.

case
when coalesce(d.metadata->>'indexing_v3_agent_status', '') ='processing'and parsed_locked_at >= now() - v_processing_lock_timeout
then ... 'indexing_v3_agent_status', 'processing', 'enrichment_status', 'processing'
else ... 'indexing_v3_agent_status', 'deferred', 'enrichment_status', 'pending'
end

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

• Introduced a local timeout variable (v_processing_lock_timeout) to avoid hard-coded lock-window literals in the repaired function path.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:08fd5df4c8

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:304caefa99

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