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]

Autofix assessment

This run was triggered on PR opened, but there are no inline review comments to address on this PR yet.

Checked:

• Pull request review comments API — empty
• Review threads (GraphQL) — empty
• PR reviews — empty

No code changes were made. Re-run when a reviewer leaves an inline comment on the diff.

  

_{Sent by Cursor Automation: Autofix PR review comments}

[cursor]

PR Risk Assessment

Risk level: Low

Evidence (diff-based)

Area	Change
Files	4 schema data modules only (src/data/schemas/v0/pipeline.ts, v0/template.ts, v1/pipeline.ts, v1/template.ts)
Runtime code	None — no changes to tools, registry, auth, dispatch, or infra
Schema changes	Mechanical upstream sync: adds ChangeAdvisorStepNode/ChangeAdvisorStepInfo; adds agent alias for template in v1 schemas; relaxes serviceReferences required constraint on load-test templates; adds deprecation note on template.agent
Lines	+499 / −8

Rationale

• Automated daily sync from harness/harness-schema via .github/workflows/sync-schemas.yml — established, recurring pattern (prior syncs #692, #651, #597, etc.).
• Blast radius limited to bundled JSON Schema validation served by harness_schema; no shared service or dispatch logic modified.
• Changes mirror upstream Harness platform schema definitions; validation relaxations (serviceReferences) are intentional upstream behavior.
• No CODEOWNERS file; no assigned reviewers.

Decision

✅ Approved — Low risk; no reviewers required.

  

_{Sent by Cursor Automation: Assign PR reviewers}