fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions

[Copilot]

Resolves 9 github_action_from_unverified_creator_used zizmor findings from the 2026-08-03 static analysis report. All flagged actions are already SHA-pinned by the compiler; this adds # zizmor: ignore[github_action_from_unverified_creator_used] annotations to acknowledge the residual publisher-identity risk.

The core problem: The compiler parses YAML frontmatter and re-marshals it, stripping all comments. Annotations added to source .md files don't survive the round-trip into generated .lock.yml files — they must be re-injected at code generation time.

Compiler changes (pkg/workflow/)

• compiler_yaml_step_conversion.go — New injectZizmorUnverifiedCreatorAnnotations(yamlStr) post-processor with a unverifiedCreatorActionPrefixes list (safedep/, super-linter/, actions-ecosystem/, erlef/, astral-sh/). Inserts a comment line before any matching uses: line, preserving the existing indentation. Called in ConvertStepToYAML() after the YAML marshal/unquote pass — handles custom job steps (super-linter/super-linter).

• compiler_yaml_step_lifecycle.go — Calls injectZizmorUnverifiedCreatorAnnotations() at the top of writeStepsSection() before indentation normalization — handles pre-steps (safedep/pmg).

• safe_outputs_actions.go — Injects the annotation comment slice element before the uses: line in buildActionSteps() — handles safe-output actions (actions-ecosystem/action-add-labels).

• runtime_definitions.go / runtime_step_generator.go — UnverifiedCreator bool field on Runtime; generateSetupStep() injects the comment for erlef/ and astral-sh/ runtimes inline in the GitHubActionStep slice.

Plain (non-compiled) workflow files

• copilot-setup-steps.yml — Annotation added before astral-sh/setup-uv.
• link-check.yml — Annotations added before both gaurav-nelson/github-action-markdown-link-check steps.

Example output (generated lock file)

      - name: Install PMG (Package Manager Guard)
        # zizmor: ignore[github_action_from_unverified_creator_used]
        uses: safedep/pmg@5ac0f275b83d9d5a9342c6aae977ec32fa330daa # v1

All 9 occurrences verified across 8 affected workflow files; 269/269 workflows recompiled cleanly.

• Fixes [static-analysis] Report - 2026-08-03 #49909

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 8.36 AIC · ⌖ 8.38 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 20.5 AIC · ⌖ 9.4 AIC · ⊞ 5.9K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 7.59 AIC · ⌖ 5.99 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 15.3 AIC · ⌖ 9 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 11.5 AIC · ⌖ 11.2 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

[Copilot]

Pull request overview

Addresses issue #49909 by preserving zizmor suppressions for nine SHA-pinned actions from unverified creators.

Changes:

• Adds compiler-time annotation injection across custom, lifecycle, safe-output, and runtime steps.
• Marks affected source workflows.
• Regenerates affected lock files.

Show a summary per file

File	Description
pkg/workflow/safe_outputs_actions.go	Annotates safe-output actions.
pkg/workflow/runtime_step_generator.go	Annotates runtime setup actions.
pkg/workflow/runtime_definitions.go	Marks unverified runtime creators.
pkg/workflow/compiler_yaml_step_lifecycle.go	Processes lifecycle steps.
pkg/workflow/compiler_yaml_step_conversion.go	Adds the YAML annotation injector.
.github/workflows/super-linter.md	Marks the super-linter action.
.github/workflows/super-linter.lock.yml	Regenerates the compiled suppression.
.github/workflows/smoke-codex.md	Marks the label action.
.github/workflows/smoke-codex.lock.yml	Regenerates the compiled suppression.
.github/workflows/shared/pmg.md	Marks the shared PMG action.
.github/workflows/mcp-inspector.lock.yml	Annotates setup-uv.
.github/workflows/link-check.yml	Annotates both link-check actions.
.github/workflows/hippo-embed.lock.yml	Annotates imported PMG.
.github/workflows/dataflow-pr-discussion-dataset.lock.yml	Annotates PMG and updates metadata.
.github/workflows/daily-elixir-credo-snippet-audit.lock.yml	Annotates setup-beam.
.github/workflows/copilot-setup-steps.yml	Annotates setup-uv.

Review details

Tip

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

• Files reviewed: 16/16 changed files
• Comments generated: 2
• Review effort level: Balanced

[pelikhan]

@copilot fix https://github.com/github/gh-aw/actions/runs/30834160543/job/91755554193?pr=50015

[gh-aw-bot]

@copilot sous-chef triage:

Two review threads are still open and CI is not in a clean merge-ready state.

• Please address unresolved review feedback first:
  • fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)
  • fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)
• After pushing fixes, run the pr-finisher skill and summarize merge readiness.
• If any checks need to be rerun after your changes, include that status in your handoff.

Generated by 👨🍳 PR Sous Chef · run: https://github.com/github/gh-aw/actions/runs/30835268189

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 8.36 AIC · ⌖ 8.38 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot fix https://github.com/github/gh-aw/actions/runs/30834160543/job/91755554193?pr=50015

Addressed in 2be0bcf. I fixed annotation injection to skip YAML block-scalar payload content and added regression tests for block-scalar and post-block-scalar behavior; targeted tests and make agent-report-progress now pass locally.

[Copilot]

@copilot sous-chef triage:

Two review threads are still open and CI is not in a clean merge-ready state....

pr-finisher triage complete.

• ✅ Reviews — both referenced threads are outdated and their underlying issues are already addressed on HEAD 2be0bcf (yamlBlockScalarState guard is in place; dataflow-pr-discussion-dataset.lock.yml manifest includes actions/setup-python).
• ✅ Checks (local) — make fmt && make lint && make test-unit && make test all passed locally in this run.
• ❓ Checks (CI) — current PR check run is still in progress (copilot: https://github.com/github/gh-aw/actions/runs/30837216611/job/91765235176). CI on this HEAD remains unverified until maintainers re-trigger/complete checks.
• ✅ Mergeable — PR is OPEN, not draft; mergeable state reports unstable pending checks/review-thread resolution.

Actions taken in this pass: validated review-thread concerns against current HEAD and ran full local validation suite; no additional code changes were required.

Hand-off: please re-trigger/complete CI as needed and resolve the two outdated review threads to reach merge-ready state.

[gh-aw-bot]

@copilot sous-chef triage:

There are still two unresolved review threads, but your follow-up indicates the fixes are already on the current head.

• Please resolve or otherwise close out these threads after confirming they are fully addressed:
  • fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)
  • fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)
• After thread cleanup, re-run the pr-finisher skill and post a concise merge-readiness summary for the current head.
• CI/review state still appears non-merge-ready, so include any remaining blocker in that handoff.

Generated by PR Sous Chef · run: https://github.com/github/gh-aw/actions/runs/30838483274

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 20.5 AIC · ⌖ 9.4 AIC · ⊞ 5.9K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot sous-chef triage:

There are still two unresolved review threads, but your follow-up indicates the fixes are already on the current head....

• ❌ Reviews — 2 outdated review threads remain unresolved in GitHub UI (r3706062697, r3706062796). I confirmed both concerns are already addressed on current HEAD 2be0bcf (block-scalar guard + manifest includes actions/setup-python).
• ✅ Checks (local) — make fmt, make lint, TEST_UNIT_RUN_FULL=1 make test-unit, make test, and make recompile passed.
• ❓ Checks (CI) — stale after agent run; current PR check shows one copilot run still in progress and prior failed CI log (job 91755554193) points to TestHashConsistencyAcrossLockFiles, which is now passing locally on current HEAD.
• ✅ Mergeable — PR is OPEN, not draft; mergeable state remains unstable due to pending CI/thread state.

Actions taken: re-triaged PR/checks, reviewed failing CI logs, reran full local validation suite, and verified no additional code changes were required.
Hand-off: resolve the two outdated review threads in GitHub and re-trigger CI from a maintainer context before merge.

[gh-aw-bot]

@copilot sous-chef triage:

This PR is not yet in a clean merge-ready state.

• Please refresh the branch if needed, address remaining review/CI blockers, then run the pr-finisher skill and post a concise merge-readiness summary for the current head.

Generated by PR Sous Chef · run: https://github.com/github/gh-aw/actions/runs/30841444939

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 7.59 AIC · ⌖ 5.99 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot sous-chef triage:

This PR is not yet in a clean merge-ready state....

• ❌ Reviews — 2 outdated review threads are still unresolved in GitHub UI (r3706062697, r3706062796), though both concerns are already fixed on current HEAD 2be0bcf.
• ✅ Checks (local) — make fmt, make lint, TEST_UNIT_RUN_FULL=1 make test-unit, make test, make recompile, and make agent-report-progress all passed.
• ❓ Checks (CI) — latest copilot check is still in progress (91780889723); prior failing CI run (30834160543, job 91755554193) failed TestHashConsistencyAcrossLockFiles, which is now passing locally on current HEAD.
• ✅ Mergeable — PR is OPEN and not draft; state remains unstable pending thread cleanup / CI completion.

Actions taken: refreshed triage for current head, inspected CI logs, and reran full local validation. No new code changes were required.
Hand-off: resolve the two outdated review threads and re-trigger/complete CI from a maintainer context before merge.

[github-actions]

PR Triage: #50015

• Category: chore
• Risk: low
• Score: 46/100 (Impact 20 + Urgency 10 + Quality 16)
• Recommended action: batch_review
• Batch: pr-batch:security-fixes

Adds zizmor unverified-creator lint-suppression annotations for 9 already SHA-pinned actions. Lint-only change, not a behavior/security fix itself.

Generated by 🔧 PR Triage Agent · auto · 51.1 AIC · ⌖ 4.08 AIC · ⊞ 8K · ◷

[gh-aw-bot]

@copilot This PR is still not merge-ready. Please address the remaining review feedback, fix the failing check, refresh the branch if needed, then run the pr-finisher skill and summarize merge readiness.

Unresolved reviews:

• fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment) — avoid injecting zizmor annotations into YAML block-scalar payloads such as run: | scripts; reuse the block-scalar state and skip payload content.
• fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment) — regenerate/correct the manifest so actions/setup-python is still tracked everywhere it is emitted.

Failed checks:

• JS Tests (shard 4/4): https://github.com/github/gh-aw/actions/runs/30835526776/job/91775226624

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 15.3 AIC · ⌖ 9 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot This PR is still not merge-ready. Please address the remaining review feedback, fix the failing check, refresh the branch if needed, then run the pr-finisher skill and summarize merge readi...

Validated current head fed2e73:

• The block-scalar injection concern is fixed in 2be0bcf (yamlBlockScalarState guard in injectZizmorUnverifiedCreatorAnnotations).
• actions/setup-python is present in /home/runner/work/gh-aw/gh-aw/.github/workflows/dataflow-pr-discussion-dataset.lock.yml manifest and resolved manifest section.
• The referenced failing JS check (30835526776 / 91775226624) is from PR Fix dynamic dispatch_workflow ref forwarding and prevent ref leakage into inputs #50042, not this PR branch.

I also re-ran local validation on this branch: make fmt && make lint && make test-unit && make test && make recompile — all pass.

No additional code changes were required in this pass.

[gh-aw-bot]

@copilot sous-chef triage:

Unresolved review threads remain:

• copilot-pull-request-reviewer: fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)
• copilot-pull-request-reviewer: fix(security): inject zizmor unverified-creator annotations for all 9 SHA-pinned third-party actions #50015 (comment)

Please address the unresolved review feedback, refresh the branch if needed, then run the pr-finisher skill and post a concise merge-readiness summary for the current head.

Generated by PR Sous Chef · run: https://github.com/github/gh-aw/actions/runs/30848087243

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 11.5 AIC · ⌖ 11.2 AIC · ⊞ 8.3K · ◷
_{Comment /souschef to run again}

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.84.4