[FEATURE] Add "triaged" or "acknowledged" label for issue status visibility

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Issue reporters have no visibility into whether their report has been seen, reviewed, or added to internal tracking. Currently, the only signals are:

• Automatic duplicate detection comments
• 30-day stale bot warnings
• Eventual closure (often automatic)

This creates a "black hole" experience where reporters don't know if:

• Their issue was even read by a human
• It's being tracked internally
• They should wait or give up

Related: #15692 discusses this communication gap from the community perspective.

Proposed Solution

Add a triaged or acknowledged label that indicates "this issue has been reviewed and added to internal tracking."

This provides a minimal signal that:

1. A human has seen the issue
2. It's on the radar (even if not prioritized)
3. The reporter's effort wasn't wasted

The label can be applied manually during review or via automation after internal triage.

Alternative Solutions

• Do nothing: Continue current state where reporters have no visibility
• Comment on every issue: Higher effort, creates notification noise
• Public roadmap: Helpful but doesn't address individual issue status
• GitHub Discussions: Separates conversations but doesn't solve the "am I being heard?" problem (#14040)

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

1. User encounters a bug and searches existing issues
2. Finds similar reports but none have any official response
3. Creates a well-researched issue with reproduction steps
4. Receives automatic duplicate detection comment (not human)
5. Waits... no signal of human review
6. After 30 days, gets stale bot warning
7. Wonders: "Did anyone even see this?"

With triaged label:

• Step 5 becomes: Sees triaged label added → knows it's on the radar
• Even if not fixed immediately, the feedback loop is closed

Additional Context

Prior art:

• github/copilot-cli uses triaged label effectively
• This is standard practice for developer tools with public issue trackers

Cost:

• Minimal: one label definition
• Can integrate with existing internal triage workflow

Benefit:

• Closes the feedback loop with minimal effort
• Reduces "is anyone seeing this?" duplicate reports
• Builds trust with the community

---

✍️ Author: Claude Code (Dev Container) with @carrotRakko

Note: This issue was written and submitted by an AI agent (Claude Code), with human review and approval.