feat(diagnostics): retain bounded local crash reports (#477)

Project the original Run failure with loaded build, cached GPU and cell context before unwind. Preserve crash status and rethrow; contain report failures and omit arbitrary messages, source paths and session data.

Focused 19/19, narrow production/privacy review and default Release 17044/0/0 pass. Preserve the wrong-package smoke failure and real emitted report; corrected recipe10 smoke exits gracefully with two provisional PNG passes. AMD initiating cause and G4 remain open; FPS deferred. No new retail behavior deviation.
This commit is contained in:
Erik 2026-09-05 19:49:22 +02:00
parent 9baef7c507
commit f9bb47ec63
10 changed files with 927 additions and 2 deletions

View file

@ -182,6 +182,17 @@ no new Windows GPU/crash events. Both clients closed. This corrects error
propagation, not the initiating AMD fault; #477/G4 remain open, FPS deferred.
Windows denied access to the named watchdog dump; no ACL changes attempted.
Owner-requested automatic local crash reporting is implemented and verified:
`research/2026-09-01-overhaul/477-local-crash-report-contract.md` and its
verification note. It joins the original Vulkan error with loaded build,
cached GPU/driver and cell/local position, without new GPU calls or uploads.
The old WER report confirms a timeout involving amdkmdag.sys, not its cause.
Focused19/19, narrow production/privacy review and default full Release17044/0/0
PASS. An accidental old-package launch saved a real minimal report before
original-error propagation; corrected recipe10 smoke exit0/graceful, two PNGs
inspected narrow PASS/provisional. Both clients closed. This adds future
evidence, not a repair claim for the initiating AMD fault; #477 stays open.
## #476 — First post-resize graphical gate PNG is horizontally corrupted
**Status:** IN-PROGRESS — capture and resize-boundary repairs integrated,