API Evangelist conversational phrasing for Datadog Policies API

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Datadog Policies API
  version: 1.0.0
extends: openapi/datadog-policies-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/api/v2/on-call/escalation-policies/{policy_id}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update an On-Call escalation policy
      effect: write
      questions:
      - Can I change the steps or targets of an On-Call escalation policy?
      - Is it possible to edit who gets paged next in an escalation policy?
      instructions:
      - text: Update escalation policy {policy_id} with {data}.
        slots:
          policy_id: path.policy_id
          data: requestBody.data
      - text: Edit the steps of On-Call escalation policy {policy_id}.
        slots:
          policy_id: path.policy_id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/v2/remote_config/products/cws/policy/{policy_id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update a Workload Protection policy
      effect: write
      questions:
      - Can I enable or rename a Workload Protection agent policy?
      - Is updating Workload Protection policies supported on the US1-FED site?
      instructions:
      - text: Update Workload Protection policy {policy_id} with {data}.
        slots:
          policy_id: path.policy_id
          data: requestBody.data
      - text: Edit the Workload Protection agent policy {policy_id}.
        slots:
          policy_id: path.policy_id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/v2/restriction_policy/{resource_id}'].post
  update:
    x-apievangelist-phrasing:
      intent: Set who can access a resource
      effect: write
      questions:
      - How do I restrict who can edit a specific dashboard?
      - Can an admin accidentally lock themselves out of a resource's restriction policy?
      - Which resource types support restriction policies?
      instructions:
      - text: Set the restriction policy on {resource_id} to {data}.
        slots:
          resource_id: path.resource_id
          data: requestBody.data
      - text: Update access bindings for resource {resource_id} allowing self lockout {allow_self_lockout}.
        slots:
          resource_id: path.resource_id
          allow_self_lockout: query.allow_self_lockout
      method: generated
      generated: '2026-10-01'