feat(cli): make Registry diffs human-readable - #8
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #7
User problem
The first real Registry startup Collector works, but the default Diff output leads with opaque internal identity instead of showing a recognizable startup value, its decoded data, and where it was observed.
What changed
systemdiff diffoutput a calm, factual Registry startup summary;systemdiff diff --technicalfor Collector version/scope, canonical identity, native Registry evidence, hashes, decode status, before/after values, coverage, and diagnostics;--jsonDiff v1 document unchanged;Before / after UX
Before, the terminal primarily displayed an
ArtifactKeyand opaque canonical hash. The default output now names the Registry value, reports Added/Modified/Removed/Inconclusive factually, shows decoded command/value data when available, and displays the readable Registry location. Technical and JSON evidence remain explicit modes.Validation
cargo fmt --all --checkcargo clippy --locked --workspace --all-targets -- -D warningscargo test --locked --workspace --all-targets— 88 passedcollectorsgit diff --checkExplicit non-goals
No Services or Scheduled Tasks Collector, session/baseline/history workflow, release pipeline, schema change, rules/risk scoring, Authenticode, redaction implementation, GUI/Tauri, installer, updater, or package-manager work is included.