[GH-ISSUE #5485] [Feature] Generate a redacted diagnostic report for support requests #3339

New issue

Open

opened 2026-10-31 00:39:19 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:39:19 +00:00

Owner

Originally created by @jayykernel on GitHub (Oct 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/5485

Problem

When a setup or provider issue occurs, a useful report may require REA's version, Node/platform details, relevant readiness results, and selected provider versions. Collecting that context manually can lead to incomplete reports or accidental sharing of unrelated local details.

This differs from auditing an exported Evidence bundle for target secrets: the proposed report is about installation and diagnostic context, not target analysis content.

Proposed change

Add an opt-in command that generates a support report from version information and scoped readiness/doctor checks. Redact or omit sensitive values by default and show the report before it is written or copied.

Acceptance criteria

The report records the REA/runtime/platform versions and only the explicitly requested readiness checks.
Credentials, tokens, target paths, usernames, and arbitrary environment variables are excluded by default.
The command does not open targets or run an analysis provider unless a specific check explicitly requires it and the user approves.
The report includes a schema/version marker and can be saved as JSON.
Tests assert that representative secret-like values and private paths are not serialized.

This is a support-usability proposal, not a claim that current diagnostics leak secrets.

Originally created by @jayykernel on GitHub (Oct 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5485 ### Problem When a setup or provider issue occurs, a useful report may require REA's version, Node/platform details, relevant readiness results, and selected provider versions. Collecting that context manually can lead to incomplete reports or accidental sharing of unrelated local details. This differs from auditing an exported Evidence bundle for target secrets: the proposed report is about installation and diagnostic context, not target analysis content. ### Proposed change Add an opt-in command that generates a support report from version information and scoped readiness/doctor checks. Redact or omit sensitive values by default and show the report before it is written or copied. ### Acceptance criteria - The report records the REA/runtime/platform versions and only the explicitly requested readiness checks. - Credentials, tokens, target paths, usernames, and arbitrary environment variables are excluded by default. - The command does not open targets or run an analysis provider unless a specific check explicitly requires it and the user approves. - The report includes a schema/version marker and can be saved as JSON. - Tests assert that representative secret-like values and private paths are not serialized. This is a support-usability proposal, not a claim that current diagnostics leak secrets.

bsakaguchi referenced this issue

2026-10-31 00:40:20 +00:00

[GH-ISSUE #5654] [Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #3425

bsakaguchi referenced this issue

2026-10-31 01:08:54 +00:00

[PR #3339] test(javascript): cover missing package-manifest companions staying unknown #5718