[isaacroldan]

WHY are these changes introduced?

Gardener - Investigate Issue (.github/workflows/gardener-investigate-issue.yml) has never done anything in this repo:

• It has 0 runs ever, and it has been disabled_manually since 2026-10-26.
• Its trigger label, devtools-investigate-for-gardener, has been applied 0 times in Shopify/cli.
• It pins anthropics/claude-code-action@36a69b6 (v1.0.134, which bundles Claude Code 2.1.161). That is the same pin that now breaks maintenance-prs: runs 40249213977 and 40426069655 fail with Claude Code 2.1.161 does not support this model; version 2.1.280 or newer is required. If anyone re-enabled this workflow, it would fail the same way.

The evidence comes from a read-only inventory of Dev Experience automations collected on 2026-10-27 (workflow state, run history and label usage via gh).

WHAT is this pull request doing?

Deletes .github/workflows/gardener-investigate-issue.yml. No docs or agent files reference this workflow. The investigating-github-issues skill stays, because it is general-purpose and not specific to this workflow.

This is separate from #9008, which removes gardener-backlog-prs.yml. This PR doesn't touch that file.

How to manually test your changes?

There is nothing to test locally because this only deletes a workflow. After merge, Gardener - Investigate Issue should no longer show up as a workflow defined on main.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add