Problem
The control-plane/ package has zero PagerDuty/alerting references anywhere in it. A provisioning failure during a real pilot needs to actually page someone, not silently fail.
Area
control-plane/, src/services/notify-pagerduty.ts.
Proposal
Wire the existing PagerDuty pattern into control-plane's provisioning failure paths.
⚠️ Required pattern — read src/services/notify-pagerduty.ts before starting, same as #7666. Reuse it exactly — do not build a second alerting mechanism.
Deliverables
Test Coverage Requirements
control-plane/** — confirm this package's current coverage.include scoping before assuming src/**'s gate applies identically; mock the PagerDuty call, no live paging in tests.
Resources
control-plane/src/tenant-provisioning-driver.ts, control-plane/src/provisioning.tssrc/services/notify-pagerduty.ts (the required pattern)
Boundaries
Extends the existing alerting pattern only.
Contributor-eligible. Reuse notify-pagerduty.ts exactly — a PR that builds a new alerting path does not satisfy this issue.
Problem
The
control-plane/package has zero PagerDuty/alerting references anywhere in it. A provisioning failure during a real pilot needs to actually page someone, not silently fail.Area
control-plane/,src/services/notify-pagerduty.ts.Proposal
Wire the existing PagerDuty pattern into control-plane's provisioning failure paths.
Deliverables
control-plane/callsnotify-pagerduty.ts's existing integration.Test Coverage Requirements
control-plane/**— confirm this package's currentcoverage.includescoping before assumingsrc/**'s gate applies identically; mock the PagerDuty call, no live paging in tests.Resources
control-plane/src/tenant-provisioning-driver.ts,control-plane/src/provisioning.tssrc/services/notify-pagerduty.ts(the required pattern)Boundaries
Extends the existing alerting pattern only.
Contributor-eligible. Reuse
notify-pagerduty.tsexactly — a PR that builds a new alerting path does not satisfy this issue.