chore: invoke bulk invoice schema migration

[turip]

Overview

Invoke the set-based multi-customer invoice migration function for existing schema-level-1 invoices.

This PR is stacked on top of #4727, which introduces om_func_migrate_customer_invoices_to_schema_level_2_bulk(TEXT[]).

Changes

• Lock all existing billing customer-lock rows for the duration of the migration.
• Materialize the distinct locked customers that still have schema-level-1 invoices in a transaction-local temporary table.
• Pass the complete customer-ID array to the bulk migration function in a single call.
• Keep the migration irreversible because migrated invoice storage cannot be safely reconstructed as schema level 1.

This layer intentionally contains no detailed-line copying logic or explicit ANALYZE. The temporary table is dropped automatically when the transaction commits.

Validation

• atlas migrate --env local lint --latest 1
• atlas migrate validate --env local
• git diff --check

Greptile Summary

This PR migrates existing invoices to schema level 2 in one transaction. The main changes are:

• Locks existing billing customer-lock rows during migration.
• Materializes affected customer IDs in a temporary table.
• Calls the bulk invoice migration function once with the complete array.
• Marks the migration as irreversible.

Confidence Score: 5/5

No additional merge-blocking issue requires a separate code change.

• No distinct production failure was found beyond the issue already identified for this migration path.

Important Files Changed

Filename	Overview
tools/migrate/migrations/20260717062142_migrate_invoices_to_schema_level_2.up.sql	Adds the transactional lock, temporary customer set, and bulk migration call.
tools/migrate/migrations/20260717062142_migrate_invoices_to_schema_level_2.down.sql	Documents that migrated invoice data cannot be restored safely.
tools/migrate/migrations/atlas.sum	Registers the new forward migration checksum.

_{Reviews (3): Last reviewed commit: "chore: invoke bulk invoice schema migrat..." | Re-trigger Greptile}

Context used:

• Context used - CLAUDE.md (source)
• Context used - AGENTS.md (source)

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 41cb7b64-0b61-4f5f-9837-ce668bb8385a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/invoke-bulk-invoice-schema-level-2-migration

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Missing Lock Rows Skip Invoices

The inner join excludes every schema-level-1 invoice whose customer has no billing_customer_locks row. Because these rows are created lazily and invoices predate the lock table, an untouched historical customer can be omitted, leaving its invoices at schema level 1 after this irreversible migration.

Context Used: AGENTS.md (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: tools/migrate/migrations/20260716150457_migrate_invoices_to_schema_level_2.up.sql
Line: 10-13

Comment:
**Missing Lock Rows Skip Invoices**

The inner join excludes every schema-level-1 invoice whose customer has no `billing_customer_locks` row. Because these rows are created lazily and invoices predate the lock table, an untouched historical customer can be omitted, leaving its invoices at schema level 1 after this irreversible migration.

**Context Used:** AGENTS.md ([source](https://app.greptile.com/openmeter/github/openmeterio/openmeter/-/custom-context?memory=eb020e3b-8e3b-45ea-a8b7-4006b2b2065b))

How can I resolve this? If you propose a fix, please make it concise.