Auto-Apply community-tested Label Based on /tested Comments from Multiple Users

[Spiral-Memory]

As an EmbeddedChat developer

I need to:
Allow community members to mark a PR as tested using a comment command (e.g. /tested), where the system automatically applies a community-tested label after validation.

So That:
Multiple independent contributors (excluding the PR author) can verify changes locally and collectively signal that a PR has been tested.

Acceptance Criteria

• Users can comment /tested on a PR
• Only non-authors are counted, and each user is counted once
• community-tested is applied after at least 2 unique users
• Temporary feedback messages are shown and do not persist

[sudorishabh]

I want to work on this. The plan is to manage and test comments on pull requests, counting only distinct users, and excluding the author. The community-tested label will be applied once at least two individuals give their approval. I'll also include some temporary feedback messages to let users know their contributions were registered. If there's anything particular you'd like me to keep in mind, just let me know.

[sudorishabh]

Hey Aryan, I reviewed your code and noticed a few issues that should be fixed:

1. /tested matching is too broad, this is the most serious bug. Both their if- guard and the script use contains/includes, so a comment like /tested-on-staging or I /tested this would be counted as a valid test. This directly breaks the acceptance criterion of an intentional command.

2. The success comment is permanent. violates an acceptance criterion. This comment is never deleted. The AC explicitly says "temporary feedback messages are shown and do not persist." The progress comment (below threshold) is deleted after 15s, but the success one stays forever.

await github.rest.issues.createComment({
  body: `✅ This PR has been marked as community-tested ...`,
});

3. .catch(() => {}) swallows all label creation errors. This silently ignores 404 (label already exists — fine), but also silently swallows a 403 (missing permissions), a 5xx (GitHub outage), or any network error. The workflow then proceeds to addLabels on a broken state with no indication of what went wrong.

await github.rest.issues.createLabel({ ... }).catch(() => {});

4. No bot exclusion. If a bot that comments on PRs (e.g. a review bot or dependency bot) happens to post anything containing /tested, it would be counted as a unique tester. Adding !login.endsWith("[bot]") costs nothing and closes this gap.

5. setTimeout sleep burns runner minutes for nothing. The 8s and 15s sleeps are real runner time charged against the repo's free minutes quota. Reactions are instantaneous and have no cost.

[sudorishabh]

Let me create a draft PR for the work I’ve been doing on this.

[Spiral-Memory]

@Aryan-Verma-999 Since rishabh has already begun working on this, I’ll need to close your PR to prevent overlap. You’re welcome to submit a new one if @sudorishabh doesn’t proceed within the next couple of days.