workflow_call safe_outputs can download unprefixed agent artifact name

[strawgate]

Bug

In workflow_call-compiled lock files, agent artifacts can be uploaded with a prefixed name but later downloaded using an unprefixed name.

Example mismatch observed after recompilation:

• Upload: ${{ needs.activation.outputs.artifact_prefix }}agent
• Download (conclusion path): agent

Impact

When the unprefixed download misses, the follow-up setup step does not set GH_AW_AGENT_OUTPUT, which can break downstream safe-output processing in that job path.

Expected

All safe_outputs download steps should use the same prefixed artifact naming contract as the corresponding upload step in workflow_call context.

Note

The same lock file can contain another download step that correctly uses the prefixed name, suggesting inconsistent generation across code paths.

[strawgate]

Additional downstream impact observed from this artifact-prefix mismatch.

In strawgate/kb-yaml-to-lens run 23094882183, the workflow completed green, but conclusion still created a failure issue:

• https://github.com/strawgate/kb-yaml-to-lens/actions/runs/23094882183
• [aw] Issue Triage failed strawgate/kb-yaml-to-lens#1240

Relevant evidence from logs:

• Agent succeeded but produced no safe outputs
• Checking for existing issue with title: "[aw] Issue Triage failed"
• Created new issue #1240

This happened even though the agent output contained safe-output content/candidate data and safe_outputs processing ran, so the artifact download mismatch in conclusion appears to contribute to false-positive failure issue creation.