MARCELODeterministic snapshots
Regular files receive streamed SHA-256 fingerprints and stable relative paths for repeatable comparison.
08 · Focused project · 1.0.1 released · Rust
ConfigTrace
A standalone configuration-evidence engine that records what actually changed around a game or application session without turning a diagnostic helper into another heavyweight background monitor.
FOCUSED / RELEASE1.0.1
RuntimeRUST
CrashScope sample · avg WS4.96 MB
CrashScope sample · peak WS4.99 MB
Measured avg CPU0%
1.0.1 · RELEASED · PRIVACY FIX VALIDATED
The design choice
Keep the evidence provider independent from the product consuming it.
ConfigTrace is useful on its own, and CrashScope 1.2 includes ConfigTrace 1.0.1 as its optional external configuration-evidence provider. The integration boundary is process isolation plus schema-versioned JSON/JSONL contracts rather than a direct Rust/C# ABI.
That keeps lifecycle, failure isolation and versioning explicit: CrashScope can launch ConfigTrace for a monitored session, consume bounded evidence, and stop it without duplicating its parsing logic or letting provider failure take down the host.
Semantic evidence
Record meaningful state changes, not raw filesystem noise.
Field-level diffs
JSON and common INI/CFG-style files expose structured value changes instead of only whole-file hashes.
Privacy-aware redaction
Version 1.0.1 fixes sensitive-key recognition for camelCase/PascalCase values such as apiToken, accessToken, clientSecret, sessionId and APIKey while keeping change fingerprints useful.
Event-driven journal
Native filesystem notifications wake the watcher, then a settle window and semantic resnapshot turn noisy writes into stable JSONL change records.
Validated integration overhead
Small enough to stay a sidecar.
These figures come from CrashScope 1.1's final active provider validation sample, not a universal performance claim.
measured average CPU0%
average working set4.96 MB
peak working set4.99 MB
average private memory0.91 MB
provider journalPASS
plaintext test secretNOT FOUND
validated commitb629c970
release stateRELEASED 1.0.1
CrashScope boundary
Correlation evidence, never automatic causation.
CrashScope 1.2 can report that HDR, renderer or another configuration field changed a measured amount of time before an incident. ConfigTrace alone does not justify claiming that the change caused the incident.
The schema-v1 snapshot/diff and live-journal contracts remain the stable integration boundary used by CrashScope 1.2, while ConfigTrace stays independently usable as a standalone utility.
Release provenance
A small maintenance release with a concrete reason.
Validated commit
b629c970dfc14fca5df1e0ef2b0d1d07d0d8c56c
Windows EXE SHA-256
fe1c470a58402e82e97ee529c6a6b02822430da70e65ffc5fc5a71359ad4e521
Release ZIP SHA-256
9374128c42e3bf3e1fd8f48bdddd7485e421da543c80f54d454985e1bcccbafe
1.0.1 change
Fix camelCase sensitive-key redaction originally discovered during CrashScope 1.1 integration.
Focused utility · 1.0.1
A tiny Rust process with a deliberately stable boundary.
ConfigTrace shows systems work at a small scale: filesystem events, deterministic state, privacy constraints, integration contracts, measured resource use and a maintenance release driven by a real integration finding.