[rush reporter][R3] Emit shadow RushSession lifecycle and diagnostics #5976
Description
Activity
- addedenhancementThe issue is asking for a new feature or design changeThe issue is asking for a new feature or design change
on Aug 28, 2026 - added a parent issue
on Aug 28, 2026 TheLarkInn commented
on Aug 28, 2026 MemberAuthorMore actionsR3 implementation is complete and stacked in order: #5985 -> #5988 -> #5991 -> #5992. I independently reviewed #5988 and #5991 against this issue/RFC phase 3; no parent-slice defect required rewriting those branches. #5992 adds the exhaustive parity/integration matrix and fixes logical-cancellation derivation while preserving legacy output and authoritative process exit behavior. Local reporter/rush-lib/rush/rush-sdk tests, builds, API review,
rush check, and change verification pass. Current blocker: #5985 has green CI and squash auto-merge enabled but still requires maintainer approval. Child PRs remain on their parent branches with only CLA checks; they must be retargeted to main one at a time after each parent merges, then pass full CI and approval before enabling squash auto-merge. The issue should remain open until all four PRs merge and parity is revalidated on main.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNeeds triage
Parent: #5858
Blocked by: #5974
Goal
Connect
rush-libto the reporter event contract in shadow mode, with no visible output change.Scope
RushSession, actions, and plugins without exposing concrete reporters.AlreadyReportedErrorcorrelation while the legacy renderer remains authoritative.Acceptance criteria
DAG
Unblocks R4, R5, and R7.
Part of #5858.