v0.13.9 — the driver verdict outlives the folder it was read in
The driver verdict is remembered for the machine now, and Remove stops deleting the evidence. (#69)
v0.13.8 was supposed to install renodx-dlss5-4.55 on a machine whose log reports the 616.64 driver fault. @sempie27's install log after updating:
[7/9] DLSS 5 add-on + models
ok: host64/renodx-dlss5.addon64 (renodx-dlss5-4.70)
Still the faulting build — and the reason is circular in a way I set up myself. I told him to press Remove and then Install, and Remove deletes host64\dlss5-feed-host.log, the one file carrying the verdict the next Install reads.
Two changes:
- When a log states the fault, it is recorded once under the tool's own settings directory, against the driver version that produced it. Later installs consult that, a fresh game folder with no log inherits it, and a driver update retires it by itself and drops the stale record.
- Remove no longer deletes
ReShade.logordlss5-feed-host.log. Those are evidence, not installed files; taking them out made every subsequent diagnosis worse.
The decision itself is now a small function with its two pieces of state passed in, so the tests exercise it against a temp file and a fixed driver string rather than whatever the build machine happens to have installed.
SHA-256 of dlss5oneclick.exe: acc3f641777f01c34fab4b532e52d5d69528e521cd0140ba47ae7a00b88c3d09
