chore: auto-sync harness schemas

[github-actions]

Automated schema synchronization from harness/harness-schema.

This PR updates both v0 and v1 JSON schemas used by the MCP server to match the latest definitions upstream.

[cursor]

Stale comment

Risk Assessment: Very Low (re-evaluated after sync)

Decision: No action required — prior approval stands; risk unchanged.

Trigger

PR synchronized to commit e469ee8 (force-push/rebase; prior approval was on 1d6028d, not an ancestor). Re-assessed from the current diff only.

Evidence (diff-based)

Signal	Finding
Files changed	2 — src/data/schemas/v0/pipeline.ts, src/data/schemas/v0/template.ts
Lines	+2,014 / −247
Runtime logic	None — no changes under src/tools/, src/registry/, src/client/, workflows, or infra
Author	github-actions[bot] via scheduled sync-schemas.yml
CODEOWNERS	None
Reviewers assigned	0

What changed

Upstream harness/harness-schema mirrored into bundled v0 pipeline and template schemas:

• Widened validation — several name fields now use oneOf to accept Harness expression syntax (<+...>) alongside existing identifier patterns (permissive, not tightening).
• Expanded step definitions — fuller *StepInfo blocks for Azure Container Apps rollback, Google Cloud Run deploy/rollback, and Google/AWS Agent Runtime traffic/deploy/rollback steps.
• New service spec — AiAgent / AiAgentServiceSpec with AwsAgentCore and GoogleAgentRuntime platform variants.
• New field — llmConnectorRef added in pipeline schema.

Schemas are reference data consumed by harness_schema and MCP resources; they do not alter server dispatch, auth, or API execution paths.

Reviewers

Not required (Very Low risk).

Approval

Existing approval retained — risk level unchanged (Very Low → Very Low). No re-approval posted per policy.

---

Automated risk assessment — conclusions derived from the diff only.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale comment

Risk Assessment: Very Low (re-evaluated after sync)

Decision: No action required — prior approval stands; risk unchanged.

Trigger

PR synchronized to commit 3e3d4706 (rebased onto 22bac922; prior approval on 1d6028d is not an ancestor). Re-assessed from the current diff only.

Evidence (diff-based)

Signal	Finding
Files changed	2 — src/data/schemas/v0/pipeline.ts, src/data/schemas/v0/template.ts
Lines	+2,022 / −255
Runtime logic	None — no changes under src/tools/, src/registry/, src/client/, workflows, or infra
Author	github-actions[bot] via scheduled sync-schemas.yml
CODEOWNERS	None
Reviewers assigned	0

What changed

Upstream harness/harness-schema mirrored into bundled v0 pipeline and template schemas:

• Widened validation — several name fields now use oneOf to accept Harness expression syntax (<+...>) alongside existing identifier patterns; delegate-selector patterns widened to allow : (permissive, not tightening).
• Expanded step definitions — fuller *StepInfo blocks for Azure Container Apps rollback, Google Cloud Run deploy/rollback, and Google/AWS Agent Runtime traffic/deploy/rollback steps.
• New service spec — AiAgent / AiAgentServiceSpec with AwsAgentCore and GoogleAgentRuntime platform variants.
• New field — llmConnectorRef added in pipeline schema.

Schemas are reference data consumed by harness_schema and MCP resources; they do not alter server dispatch, auth, or API execution paths.

Reviewers

Not required (Very Low risk).

Approval

Existing approval retained — risk level unchanged (Very Low → Very Low). No re-approval posted per policy.

---

Automated risk assessment — conclusions derived from the diff only.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale comment

Risk Assessment: Very Low (re-evaluated after sync)

Decision: No action required — prior approval stands; risk unchanged.

Trigger

PR synchronized to commit 5479d138 (rebased onto 22bac922; prior approval on 1d6028d is not an ancestor). Re-assessed from the current diff only.

Evidence (diff-based)

Signal	Finding
Files changed	4 — src/data/schemas/v0/pipeline.ts, src/data/schemas/v0/template.ts, src/data/schemas/v1/pipeline.ts, src/data/schemas/v1/template.ts
Lines	+2,042 / −275
Runtime logic	None — no changes under src/tools/, src/registry/, src/client/, workflows, or infra
Author	github-actions[bot] via scheduled sync-schemas.yml
CODEOWNERS	None
Reviewers assigned	0

What changed

Upstream harness/harness-schema mirrored into bundled schemas:

v0 (pipeline + template):

• Widened validation — several name fields now use oneOf to accept Harness expression syntax (<+...>) alongside existing identifier patterns; delegate-selector patterns widened to allow : (permissive, not tightening).
• Expanded step definitions — fuller *StepInfo blocks for Azure Container Apps rollback, Google Cloud Run deploy/rollback, and Google/AWS Agent Runtime traffic/deploy/rollback steps.
• New service spec — AiAgent / AiAgentServiceSpec with AwsAgentCore and GoogleAgentRuntime platform variants.
• New field — llmConnectorRef added in pipeline schema.

v1 (pipeline + template):

• Field rename — sequential → parallel with updated descriptions (upstream alignment; schema metadata only, no server logic change).

Schemas are reference data consumed by harness_schema and MCP resources; they do not alter server dispatch, auth, or API execution paths.

Reviewers

Not required (Very Low risk).

Approval

Existing approval retained — risk level unchanged (Very Low → Very Low). No re-approval posted per policy.

---

Automated risk assessment — conclusions derived from the diff only.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk Assessment: Very Low (re-evaluated after sync)

Decision: No action required — prior approval stands; risk unchanged.

Trigger

PR synchronized to commit d3b459ed (rebased onto 22bac922; prior approval on 1d6028d is not an ancestor). Re-assessed from the current diff only.

Evidence (diff-based)

Signal	Finding
Files changed	4 — src/data/schemas/v0/pipeline.ts, src/data/schemas/v0/template.ts, src/data/schemas/v1/pipeline.ts, src/data/schemas/v1/template.ts
Lines	+2,066 / −285
Runtime logic	None — no changes under src/tools/, src/registry/, src/client/, workflows, or infra
Author	github-actions[bot] via scheduled sync-schemas.yml
CODEOWNERS	None
Reviewers assigned	0

What changed

Upstream harness/harness-schema mirrored into bundled schemas:

v0 (pipeline + template):

• Widened validation — several name fields now use oneOf to accept Harness expression syntax (<+...>) alongside existing identifier patterns; delegate-selector patterns widened to allow : (permissive, not tightening).
• Expanded step definitions — fuller *StepInfo blocks for Azure Container Apps rollback, Google Cloud Run deploy/rollback, and Google/AWS Agent Runtime traffic/deploy/rollback steps.
• New service spec — AiAgent / AiAgentServiceSpec with AwsAgentCore and GoogleAgentRuntime platform variants.
• New field — llmConnectorRef added in pipeline schema.

v1 (pipeline + template):

• Field rename — sequential → parallel with updated descriptions (upstream alignment; schema metadata only, no server logic change).

Schemas are auto-generated reference data consumed by harness_schema and MCP resources; they do not alter server dispatch, auth, or API execution paths.

Reviewers

Not required (Very Low risk).

Approval

Existing approval retained — risk level unchanged (Very Low → Very Low). No re-approval posted per policy.

---

Automated risk assessment — conclusions derived from the diff only.

  

_{Sent by Cursor Automation: Assign PR reviewers}