fix: tighten "Upload Safe Outputs" step presence check in integration test

[Copilot]

TestStepOrderingValidation_SecretRedactionBeforeUploads was failing because the substring check "name: Upload Safe Outputs" is a prefix match — it also hits the still-valid steps "Upload Safe Outputs Items" and "Upload Safe Outputs Assets".

Change

Updated the check to use the exact step-name pattern "- name: Upload Safe Outputs\n", consistent with the identical assertion in agentic_output_test.go:

// Before — prefix match, unintentionally catches sibling steps
if strings.Contains(contentStr, "name: Upload Safe Outputs") { ... }

// After — exact step name, consistent with agentic_output_test.go
if strings.Contains(contentStr, "- name: Upload Safe Outputs\n") { ... }

[Copilot]

Pull request overview

Fixes a flaky integration test assertion that incorrectly matched step names sharing the "Upload Safe Outputs" prefix.

Changes:

• Tightened the step presence check to match the exact YAML step line ("- name: Upload Safe Outputs\n").
• Added clarifying comment explaining why exact matching is required (avoids false positives on sibling steps).

Show a summary per file

File	Description
pkg/workflow/step_order_validation_integration_test.go	Updates the integration test to use an exact step-name match, preventing false positives from similarly named steps.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0