[isaacroldan]

WHY are these changes introduced?

This PR is part of the gardener cleanup and removes two things.

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).

The gardener Slack notifications are being retired. On 2026-10-30 Isaac decided to remove them. In this repo they posted only devtools-gardener-labelled items and every Dependabot PR to #devtools-gardener-backlog. Each post was a bare linked title, and together they made up most of the channel's noise. From now on, the Torrent gardener-triage routine (GARDTRI) will surface new issues and Dependabot PRs.

WHAT is this pull request doing?

Remove 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.

Remove the gardener Slack notifications. This deletes both notification workflows:

• .github/workflows/gardener-notify-event.yml: stashed the event payload when devtools-gardener was applied or when Dependabot opened a PR.
• .github/workflows/gardener-notify-slack.yml: ran on workflow_run, added devtools-gardener to Dependabot PRs and posted a linked title to Slack.

After merge, Dependabot PRs will no longer get the devtools-gardener label automatically. Nothing else in the repo depends only on these two workflows. I grepped for gardener-notify, GARDENER_SLACK, SLACK_GARDENER and devtools-gardener and checked helper scripts, label/config files and docs. This PR doesn't touch the devtools-gardener label, the other workflows or the Torrent gardener-triage routine (GARDTRI).

Secrets and variables the removed workflows used (none are deleted here; removing them is left to the maintainers):

• secrets.SLACK_GARDENER_BOT_TOKEN: used by gardener-investigate-issue.yml and gardener-notify-slack.yml, which are both removed here. maintenance-prs.yml on main still uses it (Remove maintenance-prs workflow and automated task prompts #9047 removes that workflow).
• vars.GARDENER_SLACK_CHANNEL_ID: used by the same two workflows. Once this PR merges, nothing else in the repo uses it.

This is separate from #9008 (merged), which removed gardener-backlog-prs.yml. This PR doesn't touch that file. It only changes workflows, so there's no changeset.

How to manually test your changes?

There is nothing to test locally because this only deletes workflows. After merge:

• Gardener - Investigate Issue, Gardener - Notify Event and Gardener - Notify Slack should no longer show up as workflows defined on main.
• Labelling an issue or PR devtools-gardener, or Dependabot opening a PR, should no longer post to Slack.

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