[WIP] When multiple pipelines run in parallel against the same repo, they crea

[bamdadd]

⚠️ This is a draft PR created by Lintel after a pipeline failure.
The automated workflow could not complete successfully. An engineer should review the changes, fix any issues, and mark the PR as ready.

Summary

Implement a new domain feature following the established event-sourcing CQRS monorepo patterns: define contracts first, implement persistence and projections, create an independently installable API package, wire into the app composition root, and validate with unit and integration tests.

Changes

• Audit existing codebase structure and document gaps
• Define domain types, commands, and events in contracts package
• Implement persistence and store layer for new domain
• Implement event store integration and projections for new domain
• Create new domain API package with FastAPI routers
• Wire new API package into app composition root
• Write unit tests for contracts, persistence, and projections
• Write integration and Postgres-backed tests for new API package
• Lint, typecheck, and validate full pipeline

Context

When multiple pipelines run in parallel against the same repo, they create branches from the same base. The second PR to merge will have conflicts with the first. This causes silent failures or broken PRs.

Implementation:

1. Before raise_pr stage, rebase the working branch on latest main and re-run tests
2. If rebase conflicts, mark the pipeline as needs_rebase and re-queue it
3. Add an optional per-repo concurrency limit (default 1) so pipelines targeting the same repo are serialised
4. Store repo lock state in the pipeline metadata so the executor can check before starting implement

---

Raised by Lintel 🤖

[bamdadd]

Closing stub PR from failed pipeline. Will retry with ingest fix.