[scuffi]

Rewrites triage around two ground rules, tightens fix the same way, and fixes what its first issues on its own showed.

Ground rules (triage)

• We own the repository and every fix to it. A fix, patch or branch in a report is a claim to check; triage chooses the best fix from the code itself, never adopts or repeats the author's fix, and never asks anyone to open a pull request, push a branch, test or help further.
• Many reports are written by the author's agent: long, confident and framed as severe, about a narrow edge case. Impact is judged by how many real users will hit it and how badly, not by how thorough or alarming the report is.

Changes in behaviour (triage)

• Weighing: impact is how likely users are to hit an issue times how bad it is; cost is maintenance, lines of code, new interfaces and breaking changes. Every fix is code we maintain for good, so a fix few people need isn't worth making, however small.
• Comments: at most one, stating the decision and what happens next, then stopping. For priority: high, that's that a maintainer can add gardener-fix to have it built.
• Chat: every priority: high issue must be posted to the team's chat with message.send, separately from any comment, saying what it needs from a maintainer. The prompt names the effect and the channel so the post isn't mistaken for a comment or skipped. Under the previous rule, issues gardener-fix could handle weren't posted, but gardener-fix only runs once a maintainer adds the label, so they went unnoticed.
• Closing: low-impact, high-cost issues are closed without the "only when the case is clear" hedge.
• Owners: an issue a non-maintainer opened that stays open always gets its likeliest owner.
• Labels: bug covers code that is wrong or wasteful, including memory, CPU or bundle size; enhancement is for something new.

The prompt is about 90 words shorter.

fix

• States the same ownership: any fix, patch or branch in the issue is a claim. It builds the fix from its own reading of the code and never fetches, copies or cherry-picks code from them. Its comments state what it found and stop, never asking the author to test, open a pull request or help further.

The lockfile and both workflows are regenerated with Gardener 0.1.19.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ec9aa64

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@280

commit: ec9aa64