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: no inline review comments to address

Checked PR #823 (chore/sync-schemas) for unresolved inline review threads via the GitHub API and GraphQL. 0 review threads and 0 inline review comments were found.

The trigger event was pull_request opened, not a pull_request_review_comment event, so there is no specific reviewer feedback to act on in this run.

Action taken: No code changes — the diff is an automated upstream schema sync (+330 lines adding optional reuse fields to v0 pipeline/template schemas) with no requested fixes.

If a reviewer leaves inline comments later, re-run this automation (or trigger on pull_request_review_comment) to apply targeted fixes.

  

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

[cursor]

PR Risk Assessment: Low (re-evaluated after sync update)

Decision: Existing approval retained — risk unchanged after new push; no reviewer assignment required.

Re-evaluation trigger

This PR was updated (synchronize) since the prior approval (f367704). Delta since last approval: +12 lines in 2 files.

Evidence (diff-based)

Factor	Assessment
Files changed	2 (src/data/schemas/v0/{pipeline,template}.ts)
Total diff	+342 / −0 (additive only)
Delta since approval	+12 lines — two new step-type $ref entries (GitleaksScanNode, SonarqubeScanNode)
Runtime logic	None — schema data only
Infra / auth	No changes
Blast radius	Limited to harness_schema validation surface

What changed (full PR)

1. Adds optional reuse field definitions (string or <+input> expression) across multiple v0 pipeline/template step schemas.
2. Registers GitleaksScanNode and SonarqubeScanNode in step-type unions.

All changes mirror upstream harness/harness-schema via the existing sync-schemas workflow — consistent with prior merged sync PRs (#813, #803).

Re-approval logic

• Prior assessment: Low → approved.
• New changes are additive schema registrations only; risk level remains Low (not elevated to Medium+).
• No approval revocation required.
• No re-approval posted (existing approval still valid).

Reviewers

Not required at Low risk. No CODEOWNERS file; 0 reviewers currently assigned.

  

_{Sent by Cursor Automation: Assign PR reviewers}