support templatable success and failure conditions for verification spec

[adityachoudhari26]

a verification spec contains conditions for success or failure, but sometimes these are dependent on the release target. hence these should be optionally templatable

[adityachoudhari26]

@claude implement this feature. follow existing templating patterns, you can see how the argo/tfe agents do it. there should not be too much to change just need to optionally populate the verification spec with the job's dispatch context.

[claude]

Claude finished @adityachoudhari26's task in 4m 38s —— View job • claude/issue-876-20260328-2109 • Create PR ➔

---

Implementing templatable verification spec conditions

• Explore existing templating patterns in argo/tfe agents
• Find verification spec code and understand its structure
• Implement templateVerificationSpecs function in jobdispatch package
• Update Reconcile to apply templating after merging specs
• Add tests for the new templating behavior
• Commit and push

Summary

Added Go template rendering for SuccessCondition and FailureCondition in VerificationMetricSpec, following the same pattern used by the argo and tfe agents.

Changes:

• svc/controllers/jobdispatch/template.go (new) — templateVerificationSpecs renders each spec's conditions using job.DispatchContext.Map() as template data via templatefuncs.Parse + Execute (the same approach as TemplateApplication in argo and templateWorkspace in tfe). Conditions without any {{ }} directives pass through unchanged.

• svc/controllers/jobdispatch/reconcile.go — calls templateVerificationSpecs after MergeAndDeduplicate, before CreateVerifications.

• svc/controllers/jobdispatch/template_test.go (new) — unit tests covering static conditions, templated success/failure conditions, nil dispatch context, empty specs, and an integration-style test through Reconcile.

Example usage:

successCondition: 'result.json.resource == "{{ .resource.name }}"'
failureCondition: 'result.json.env != "{{ .environment.name }}"'

|