[scuffi]

Moves Gardener to v0.1.20, and rewrites the tasks here to match it.

What 0.1.20 changes
Gardener told the model its work was a proposal ("you propose, a separate job applies"), and that showed up in its comments: "I propose…", "the fix I'd make…". 0.1.20 tells it that it acts by adding steps, which a trusted job applies in order, stopping at the first failure. Text in a step is published as written once the earlier steps have applied. So the model writes the finished reply, in the team's voice, stating what it verified and decided as fact; it never writes that a later step is done, and treats claims in the issue as unverified until it checks them. Chat summaries are described as one line of plain text.

What changes in this repository

• Direct steps: every task says what to do ("Create the branch…", "Commit your edits…", "Open the pull request…", "Reply to each thread…", "Merge it…") instead of "Propose…". The instruction to "describe proposals, not finished work" is gone: a reply is posted after the steps before it, so it says what was done.
• Replies read like a maintainer's note: a short opening line (a brief thanks, or what was done), then a few bullets or bold-labelled lines instead of one paragraph. triage uses the cause (path:line), the fix and what happens next when there's more than a sentence to say; mention-reply, fix and pr-review-fix use a line, then bullets.
• dependabot-merge gets the same wording; a failing-checks comment lists each check as a short bullet.
• Version: .gardener/SKILL.md and the gardener:generate script move to 0.1.20. The workflow pin is unchanged (0.1.20 uses the same task workflow), and the lockfile and workflows are regenerated with 0.1.20; only the task bundle hashes change.
• Deployment: the runtime moves to 0.1.20 once this merges.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 53c9598

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@cloudflare/computer@282

commit: 53c9598