Expose scoped RushSession reporter producers

[Sean Larkin (TheLarkInn)]

Part of #5976

Stack parent: #5985

Summary

• accept an optional typed reporter sink/session identity at the frontend-to-engine launch boundary
• expose source-bound scoped reporters/loggers through RushSession and command-bound reporters to Rush actions
• give each plugin a RushSession facade whose package/version/plugin source is derived from trusted loader metadata
• retain legacy terminal/logger APIs and no-sink behavior unchanged
• keep rush-sdk declaration proxy compatibility for the new beta producer types

Validation

• rush install
• rush test --only @rushstack/rush-reporter --only @microsoft/rush-lib --only @rushstack/rush-sdk
• rush build --to @microsoft/rush-lib --to @rushstack/rush-sdk
• rush check
• rush change --verify

Compatibility guarantee

No reporter is created and no structured event is emitted unless the frontend explicitly supplies a sink. Existing RushSession.getLogger(), RushSession.terminalProvider, and visible terminal output remain authoritative and unchanged.

Non-goals

• lifecycle, diagnostic, telemetry, result, or exit-status emission (R3B)
• operation stream wiring (R5)
• reporter selection/configuration or frontend controls (R2)
• terminal API removal (R9)

[Sean Larkin (TheLarkInn)]

Independent R3 review against #5976/RFC phase 3: the slice is correctly limited to the optional frontend-to-engine sink plus trusted Rush/action/plugin producer facades. I found no source-identity spoofing, privacy, no-sink compatibility, error-handling, API, or visible-output defect. Stack-only diff is one commit over #5985; no unresolved review threads are present. Full local stack validation is recorded on child #5992.

[Sean Larkin (TheLarkInn)]

Combined deep review of current head eb6ae446f1.

1. CRITICAL RushFrontend.ts:52-55 passes reporterEventSink, while Rush.launch() reads reporter. The real frontend path produces no structured session or plugin events. Pass reporter: { eventSink, sessionId }.
2. HIGH RushFrontend.test.ts:58-78 asserts the ignored key through an unsafe cast. Test the typed reporter contract and real launch path.
3. HIGH RushSession.ts contains empty source metadata guards that continue with invalid path or version data. Fail explicitly with the repository internal error pattern.

[Sean Larkin (TheLarkInn)]

Rebased the single R3A commit onto #5989 head 62d9e7af04ca0ae9d176ba07b745322288f1be72. Fixed the typed frontend-to-engine reporter: { eventSink, sessionId } handoff, added real launchRushFrontendAsync() to Rush.launch() boundary coverage with one preserved session id, removed unsafe sink-key assertions, and confirmed explicit InternalError source guards. Reporter, rush-lib, rush-sdk, and apps/rush tests and builds pass, along with API review, rush check, and stacked change verification.

[Sean Larkin (TheLarkInn)]

Final combined review of 07f17e4c7f found no critical, high, medium, or useful low issues. The typed frontend-to-engine contract, session identity, source validation, scoped producer boundary, no-sink compatibility, and launch integration coverage are review-clean.

[Sean Larkin (TheLarkInn)]

Deep review of current head 007b113 found no critical, high, or medium actionable issues. The typed reporter sink and authoritative session identity remain isolated and backward compatible. Merge remains gated by #5989 and maintainer approval.