chore(OMN-14974): vendor delegation reconcile migration

[jonahgabriel]

Summary

• vendor the byte-identical node_projection_delegation/0009a_delegation_events_legacy_schema_reconcile.sql from omnimarket
• satisfy the required source-first migration parity gate for omnimarket#1924
• preserve namespaced migration identity and append-only ordering

Verification

• sync dry-run identified exactly one missing file
• write sync updated exactly one file; subsequent --check passed
• byte comparison against omnimarket#1924 source passed
• focused migration suite: 69 passed
• commit hooks: passed
• governed pre-push unit suite: 22,257 passed, 32 skipped

Deployment safety

This PR vendors source only. The staging repair will use omnimarket#1924 bounded runner through 0022_delegation_events_tenant_id.sql; it will not blindly apply the pending FORCE-RLS migration.

Linear: OMN-14974
Depends on: OmniNode-ai/omnimarket#1924 source file

Evidence-Ticket: OMN-14974
Evidence-Source: OCC#5220
Evidence-Commit: 22453cc51300a555a7f0247ae92876f205745a2f

Omnimarket-Source-Ref: jonah/omn-14974-projection-schema-reconcile

Node-Migration-Source-Ref: jonah/omn-14974-projection-schema-reconcile

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 58b64fa1-a0e3-49db-9ad8-44019417ab8a

📥 Commits

Reviewing files that changed from the base of the PR and between c09f10a and fcbad80.

📒 Files selected for processing (1)

• docker/migrations/forward/nodes/node_projection_delegation/0009a_delegation_events_legacy_schema_reconcile.sql

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14974-vendor-delegation-reconcile

---

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

[github-actions]

⚠️ Hostile Reviewer — DEGRADED (informational)

Blocking findings (critical): 0
Total findings: 0
Models succeeded: none

Note: All reviewer models failed or were unavailable. Degraded results are informational during the pilot phase (OMN-8468/OMN-8524) and do not block merge. Error: all review endpoints [192.168.86.201:8000 192.168.86.201:8001 ] unreachable — preflight short-circuit (no models available)

---

Gate semantics (pilot phase)

Verdict	Meaning	Blocks merge?
passed	No critical findings	No
blocked	CRITICAL findings found	Yes
degraded	All models unavailable (infra)	No (pilot)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8468/OMN-8524)

[jonahgabriel]

Refreshing the pull_request event payload so the existing strict node-migration-sync gate reads the newly declared paired Omnimarket-Source-Ref. Reopening immediately at the same head; no code or evidence hash changes.

[jonahgabriel]

Merge-controller a: cycling close/reopen to force a fresh pull_request event after adding Node-Migration-Source-Ref. Rerunning the old workflow reused the pre-edit event payload and still resolved omnimarket ref dev, so it cannot observe the paired source branch metadata.