fix(acv2): close combined Schema 23 canonical migration contract

[laiqian0239-glitch]

Work package

ACV2-SCHEMA23-CANONICAL-MIGRATION-COMBINED-CLOSURE-V2

Authorized by ordinary two-parent merge 05ba68e784cf06582e5732f49256bd8ed6b928f5 from #376.

Failure-first exact state

Current Head 9d565a29a180db8133f8f763e2d1424d04534872 is the direct child of the authorization merge and changes exactly the three authorization-frozen tests, with zero production code:

• backend/tests/architectureClosureV2/wpA/authorityWriteHost.test.js
• backend/tests/architectureClosureV2/wpA/domainEventProjectionJobsCanonicalMigration.test.js
• backend/tests/batch27DeveloperHandoffV2Closure.test.js

Exact 3-path SHA-256: fbda331336c0f09da7579f29a443b0de85fb573f3ccecd7983c09b11dde4725c.

The tests intentionally require current total R32 Schema 23, preserve historical Schema 22 receipt semantics, assert the new Schema 23 migration receipt, and require domain_event_projection_jobs.event_id to bind to canonical_event_headers without durable-row loss.

No production code may be added until this exact Head records fresh causal RED.

Planned GREEN

After causal RED only, add exactly:

• backend/lib/r32SqliteStore.js
• backend/migrations/architectureClosureV2DomainEventProjectionJobsCanonical.js

These are the same independently reviewed production blobs previously validated on #374; they will be materialized as fresh descendant content under #376 authority, not cherry-picked as authority.

No historical migration rewrite, projection-worker patch, dependency/workflow/package/lock change, rebase, force-push, release or publish.

PR #372 remains frozen at fb1beeb0e39ad4d6263f71b4c995eb5ec663e6e2.

[coderabbitai]

Warning

Review limit reached

@laiqian0239-glitch, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 63 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: 814ebfae-dfd2-4304-a834-1479865615cc

📥 Commits

Reviewing files that changed from the base of the PR and between 05ba68e and d4bb858.

📒 Files selected for processing (5)

• backend/lib/r32SqliteStore.js
• backend/migrations/architectureClosureV2DomainEventProjectionJobsCanonical.js
• backend/tests/architectureClosureV2/wpA/authorityWriteHost.test.js
• backend/tests/architectureClosureV2/wpA/domainEventProjectionJobsCanonicalMigration.test.js
• backend/tests/batch27DeveloperHandoffV2Closure.test.js

---

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.}