[rush reporter][R8] Qualify AI reporter auto-selection
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- build-system, ci-cd, tooling
Research direction
The issue names no files or tests; start by reading parent #5858 and blocked issues #5977 and #5978, then locate the reporter and environment-detection entry points. Done means a deterministic CI corpus, documented and enforced thresholds, machine-readable gate results, protected secrets, correct log paths, and opt-in auto-selection while RUSH_REPORTER=legacy remains authoritative.
Written by the indexing model from the issue text.
Description
Parent: #5858
Blocked by: #5977, #5978
Goal
Prove that the AI reporter improves agent outcomes before enabling environment-based automatic selection.
Scope
- Build a deterministic corpus of representative install, configuration, dependency, build, cache, network/auth, and plugin failures.
- Compare legacy/plaintext/AI output for remediation success, context consumption, determinism, secret handling, and full-log discoverability.
- Validate built-in
COPILOT_CLIdetection plus configuredagentEnvironmentVariables. - Define pass/fail thresholds and store machine-readable gate results.
- Keep auto-selection disabled until the corpus gates pass.
Acceptance criteria
- The corpus is deterministic and runnable in CI.
- AI output never includes classified secrets and does not regress producer privacy.
- Thresholds for remediation quality, output size, determinism, and log-path correctness are documented and enforced.
- Passing the gate enables agent auto-selection only on the opt-in reporter path before Rush 6.
-
RUSH_REPORTER=legacyremains authoritative.
DAG
Unblocks R9.
Part of #5858.
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 48
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/rushstack
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100