Affects
Teams that build setup flows for Matcher contexts or handle fee-schedule deletion conflicts.
What changed
Setup progress now returns public
context.activation.requirement.* identifiers in readiness.missing and next.requirementId. Attempting to activate an unready context returns 409 Conflict with MTCH-0103 and the same identifiers in problem details.
A fee schedule that remains referenced returns 409 Conflict with MTCH-0108. Its blocking contexts are available in errors at fee-schedule.delete.blocking-contexts.
This documentation update aligns the public contract with implemented behavior; it does not announce a runtime release.
Impact
Classification: Action required. Client code that keys setup guidance to the former readiness slugs or assumes deletion conflicts lack context must use the documented fields.
What you need to do
Update setup-progress consumers to use
context.activation.requirement.* values and next.requirementId. Handle MTCH-0103 problem details when activation is blocked. For MTCH-0108, display or act on the blocking contexts at errors.fee-schedule.delete.blocking-contexts.