[plan] Fix actionlint `matched_command` undefined in `pre_activation` outputs for 37 workflows

[github-actions]

Context

From discussion #17412 — Static Analysis Report 2026-02-21.

Problem

Actionlint reports 37 expression type errors across 37 compiled workflow files because the pre_activation job's outputs: block (once added) does not include matched_command. Jobs that reference needs.pre_activation.outputs.matched_command fail actionlint type checking.

Error: property "matched_command" is not defined in object type {activated: string}

This is a related but separate fix to the outputs: block issue — it affects workflows that use slash-command matching and reference matched_command specifically.

Affected Workflows (first 20 of 37)

agent-performance-analyzer, agent-persona-explorer, ai-moderator, auto-triage-issues, breaking-change-checker, changeset, ci-doctor, code-scanning-fixer, code-simplifier, daily-file-diet, daily-issues-report, daily-observability-report, daily-safe-output-optimizer, daily-team-status, daily-testify-uber-super-expert, dependabot-burner, dev-hawk, example-custom-error-patterns, firewall-escape, issue-monster ... and 17 more.

Steps

1. Confirm fix from the pre_activation outputs issue also adds matched_command to the outputs block
2. Check if the compiler conditionally emits matched_command only for slash-command workflows — if so, ensure the output is always declared (or declared when needed)
3. Run make recompile and verify actionlint passes for all 37 affected workflows
4. Run make agent-finish before committing

Acceptance Criteria

• All 37 workflows with matched_command expression errors pass actionlint after recompile
• Compiler correctly emits matched_command in pre_activation outputs for applicable workflows
• All existing tests pass (make test-unit)

Generated by Plan Command for issue #discussion #17412

• expires on Feb 23, 2026, 12:57 PM UTC