[Contribution Check Report] PR #22464 — [WIP] Fix regression in CompileMemoryUsage performance

[github-actions]

Contribution Check Report

Field	Value
PR	#22464
Title	[WIP] Fix regression in CompileMemoryUsage performance
Author	@Copilot (copilot-swe-agent)
Verdict	🟢 Aligned
Quality	lgtm
Existing Labels	(none)

---

Checklist Results

Check	Result	Notes
On-topic	✅ yes	Performance regression fix in the workflow compiler — directly relevant to project quality
Follows process	✅ yes	Authored by Copilot coding agent, assigned to core team member pelikhan — exactly the workflow CONTRIBUTING.md prescribes
Focused	✅ yes	All 3 files address the same root cause: YAML library swap (goccy/go-yaml → go.yaml.in/yaml/v3) + benchmark warm-up to exclude one-time cache costs
New dependencies	✅ no	go.yaml.in/yaml/v3 is already a direct dependency in go.mod (v3.0.4); goccy/go-yaml remains in use across the wider codebase
Has tests	✅ yes	compiler_performance_benchmark_test.go updated with warm-up + b.ResetTimer() across all 6 benchmark functions
Has description	✅ yes	PR body contains a fully-checked task list with benchmark numbers (5.6 ms achieved vs 13.4 ms regressed, 7.4 ms historical target)
Diff size	29 lines	27 additions, 2 deletions across 3 files

---

Summary

This is a clean, well-scoped performance fix authored by the Copilot coding agent following the project's prescribed agentic development process. The two changes are tightly coupled — replacing the slower goccy/go-yaml YAML parser with the already-present go.yaml.in/yaml/v3 for schema validation paths, and correctly excluding one-time schema compilation overhead from all benchmark measurements with b.ResetTimer(). The PR body is thorough, all checklist items are marked complete, and tests/lint are confirmed passing. The only marker holding it back from merge is the [WIP] draft status, which the core team reviewer can clear once they're satisfied.

Generated by Contribution Check · ◷

• expires on Mar 24, 2026, 5:19 PM UTC

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #22526

View newer issue

---

This action was performed automatically by the Contribution Check workflow.