# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Harness Execution Input API
  version: 1.0.0
extends: openapi/harness-execution-input-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/pipeline/api/pipeline/execution-input/{nodeExecutionId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the runtime input template for a step
      effect: read
      questions:
      - What inputs is a paused pipeline stage waiting for?
      - Can I see the execution-time input template for a step?
      instructions:
      - text: Get the execution input template for node execution {node}.
        slots:
          node: path.nodeExecutionId
      - text: Show which runtime inputs step execution {node} in project {project} needs.
        slots:
          node: path.nodeExecutionId
          project: query.projectIdentifier
      method: generated
      generated: '2026-09-26'
- target: $.paths['/pipeline/api/pipeline/execution-input/{nodeExecutionId}'].post
  update:
    x-apievangelist-phrasing:
      intent: Submit runtime inputs and resume a step
      effect: write
      questions:
      - How do I provide runtime inputs so a waiting pipeline continues?
      - Can I resume a stage that's paused for execution input?
      instructions:
      - text: Submit execution input for node execution {node} and continue.
        slots:
          node: path.nodeExecutionId
      - text: Resume stage execution {node} in project {project} with the provided inputs.
        slots:
          node: path.nodeExecutionId
          project: query.projectIdentifier
      method: generated
      generated: '2026-09-26'
- target: $.paths['/pipeline/api/pipeline/execution-input/variables'].post
  update:
    x-apievangelist-phrasing:
      intent: List variables usable as expressions in a run
      effect: read
      questions:
      - Which variables can I reference as expressions during a pipeline run?
      - Can I get the expression variables for a specific plan execution?
      instructions:
      - text: List expression variables for plan execution {plan_execution}.
        slots:
          plan_execution: query.planExecutionId
      - text: Get runtime variables for execution {plan_execution} in project {project}, org {org}.
        slots:
          plan_execution: query.planExecutionId
          project: query.projectIdentifier
          org: query.orgIdentifier
      method: generated
      generated: '2026-09-26'