[scuffi]

Moves Gardener to v0.1.19, which fixes merge-conflict and commit runs that fail after the model runs npm install.

What 0.1.19 fixes

• Commits after npm install: packages under the ignored node_modules/ often ship their own .gitattributes, and Gardener's working-tree capture refused any run that created one. Every commit or merge whose model installed dependencies failed at finish_task. That is what failed the conflict fix on dofs, rpc, computer, computerd: Build with tsdown #252 (run). New attributes files in ignored directories that hold no tracked files are now skipped, since they govern nothing a capture can include.
• Clearer failures: a failed finish_task was reported as "may have run out of output tokens". The run now says the call failed and leads with the capture's reason, and the model is told to fix the cause and call finish_task again.

What changes in this repository

• Version pins only: the workflows move to the 0.1.19 release. No task content or bundle hash changes.
• Deployment: the runtime is already on 0.1.19.

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: 56bb0dd

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

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[pkg-pr-new]

Open in StackBlitz

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

commit: 56bb0dd