API Evangelist conversational phrasing for Here CORS API

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Here CORS API
  version: 1.0.0
extends: openapi/here-cors-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: 9
- target: $.paths['/layers/{layerId}'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for generic data ingestion
      effect: read
      questions:
      - Can a browser app send generic data to an ingest layer across origins?
      - Which CORS headers does the generic data ingest endpoint return?
      instructions:
      - text: Run a CORS preflight on the generic data ingest endpoint for layer {layer_id}.
        slots:
          layer_id: path.layerId
      - text: Check the cross-origin headers for ingesting data into layer {layer_id}.
        slots:
          layer_id: path.layerId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/layers/{layerId}/partitions'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for sending partitions to a stream
      effect: read
      questions:
      - Is CORS enabled for posting partition lists to a stream layer?
      - Will a browser preflight succeed before I send partitions?
      instructions:
      - text: Run a CORS preflight for sending partitions to stream layer {layer_id}.
        slots:
          layer_id: path.layerId
      - text: Check the cross-origin headers on the partitions endpoint of layer {layer_id}.
        slots:
          layer_id: path.layerId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/layers/{layerId}/sdiiMessageList'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for sending SDII messages
      effect: read
      questions:
      - Can a web client send SDII message lists cross-origin?
      - What CORS headers come back for the SDII message list endpoint?
      instructions:
      - text: Run a CORS preflight for SDII message lists on layer {layer_id}.
        slots:
          layer_id: path.layerId
      - text: Check the cross-origin headers for sending SDII messages to layer {layer_id}.
        slots:
          layer_id: path.layerId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/problems'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for synchronous tour planning
      effect: read
      questions:
      - Can a browser app submit tour planning problems across origins?
      - Is CORS enabled on the synchronous problems endpoint?
      instructions:
      - text: Run a CORS preflight on the synchronous tour planning problems endpoint.
      - text: Check the CORS headers for submitting routing problems from a browser.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/problems/async'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for async tour planning submission
      effect: read
      questions:
      - Can a web app submit asynchronous tour planning problems cross-origin?
      - Does the async problems endpoint return CORS headers?
      instructions:
      - text: Run a CORS preflight on the async tour planning submission endpoint.
      - text: Check CORS headers for posting async routing problems.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/status/{statusId}'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for a tour planning status check
      effect: read
      questions:
      - Can a browser poll tour planning status cross-origin?
      - Is CORS enabled for checking an async routing request's status?
      instructions:
      - text: Run a CORS preflight for status {statusId}.
        slots:
          statusId: path.statusId
      - text: Check CORS headers on the status endpoint for request {statusId}.
        slots:
          statusId: path.statusId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/problems/{problemId}/solution'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for fetching a tour solution
      effect: read
      questions:
      - Can a web app download a tour planning solution cross-origin?
      - Is CORS enabled on the routing solution endpoint?
      instructions:
      - text: Run a CORS preflight for the solution of problem {problemId}.
        slots:
          problemId: path.problemId
      - text: Check CORS headers for getting problem {problemId}'s solution.
        slots:
          problemId: path.problemId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/problems/{problemId}/cancel'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for cancelling a tour problem
      effect: read
      questions:
      - Can a browser cancel a routing problem cross-origin?
      - Does the problem cancel endpoint support CORS?
      instructions:
      - text: Run a CORS preflight for cancelling problem {problemId}.
        slots:
          problemId: path.problemId
      - text: Check CORS headers on the cancel endpoint of problem {problemId}.
        slots:
          problemId: path.problemId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/matrices'].options
  update:
    x-apievangelist-phrasing:
      intent: Check CORS for routing matrix uploads
      effect: read
      questions:
      - Can a browser upload a routing matrix cross-origin?
      - Is CORS enabled on the matrices endpoint?
      instructions:
      - text: Run a CORS preflight on the routing matrix upload endpoint.
      - text: Check CORS headers for uploading matrices from a web app.
      method: generated
      generated: '2026-10-01'