Apply support-safe path redaction to recovery commands and status config

[Widthdom]

Summary

Machine-shareable content_recovery commands from excerpt/inspect embed username, repository, DB, and binary absolute paths. status --config similarly exposes user log paths without the redaction controls used by config/doctor.

Audit IDs: Q-14 and O-29.

Existing issue relationship

Residual/follow-up to closed #4313's status/support-safe path contract.

Expected behavior

Shareable output is support-safe by default, with one explicit way to request executable unredacted local commands when needed.

PR scope

One PR should apply the shared path-sensitivity/redaction contract to these surfaces.

Implementation guide for Codex 5.6 sol xhigh

• Use the existing structured path redactor; do not regex-replace rendered command strings.
• Separate display/recovery template from local resolved execution values.
• Define --redact-paths/--show-paths behavior consistently and annotate when a redacted command needs local substitution.
• Cover home/repo/DB/binary/log/temp paths, spaces, Windows drives/UNC, and JSON/human modes.
• Add regressions, update docs, run full tests, and add a bilingual changelog fragment referencing Improve status, config, report, and export diagnostics for support-safe workflows #4313.

Acceptance criteria

• Default shared JSON contains no user-specific absolute path.
• Explicit unredacted mode remains safely quoted and usable.
• Redaction behavior matches config/doctor/status policies.

[Widthdom]

Work started on branch fix-issue4860.

[Widthdom]

Draft PR opened: #4957