Returns what the Application's automatic-enrollment matcher has been doing.

Read-only companion to the policy above, kept a separate payload because that one is a full-replace PUT. `provisionedLastHour` counts over the same trailing hour and the same grant provenance the cap itself counts, so the two can never disagree. The pending counts break the queue down by which verdict put each sender there — refused by the allowlist, turned away by a spent cap, or queued because provisioning faulted — which are three different problems with three different fixes. Requests queued before those verdicts were recorded carry a sender-shaped reason and are not attributed to the matcher here.

curl -X GET "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/provisioningPolicy/activity"

{
  "networkId": "00000000-0000-0000-0000-000000000000",
  "provisionedLastHour": 0,
  "pendingNotMatched": 0,
  "pendingRateCapped": 0,
  "pendingFaulted": 0
}

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}