repo
A thin relay service that manages repository provider integrations (Azure Repos, GitHub) and ingests their webhook events (code pushes and pull requests) to resume the governed SDLC workflow. It normalizes a provider's webhook payload and forwards the raw pushed branch plus the programme id to resume the workflow; the workflow itself decides release-vs-feature. repo-service is a RELAY, not a decision-maker — it never runs verification or compliance itself. Providers follow a state lifecycle: Pending -> Active (after a successful connectivity test) -> Disabled. Provider credentials (accessToken, webhookSecret) are write-only — never returned in responses.