Skip to content

Add severity levels and diff mode for report comparison - #12

Merged
pd241008 merged 5 commits into
mainfrom
feature/production-structure
Aug 4, 2026
Merged

pd241008 merged 5 commits into
mainfrom
feature/production-structure

Conversation

@pd241008

@pd241008 pd241008 commented Aug 4, 2026

Copy link
Copy Markdown
Owner

No description provided.

Introduce Severity enum (Info/Warning/Critical) with log(), warn(), and
critical() methods; flag() remains an alias for warn(). Plain text prefixes
warnings with [!] and criticals with [CRIT]. JSON output gains
severity_counts and an entries array sorted by urgency. Report is now
Deserialize-able for baseline comparison.
--diff FILE loads a previous JSON report and highlights only new findings
(critical/warning) since that scan plus findings that were resolved.
Works with --json for pipeline consumption and supports --json --out to
write a reusable baseline. Exits 2 when new findings appeared, 0 otherwise.
Adds 6 integration tests: severity markers/counts, JSON entries sorted by
severity, Report JSON round-trip, diff new/resolved findings, diff with no
changes, and diff ignoring info entries. Total test count now 20.
Adds an Example Output section with sample plain-text and JSON reports,
documents severity levels and --diff workflow, and marks all roadmap items
complete in README and PROGRESS.
Edges referencing subgraph ids (LIB --> SCANNER, SCANNER --> PLATFORM)
trigger the mermaid dagre-wrapper crash in older renderers
(mermaid-js/mermaid#4644, fixed in v10.8). Rewrite the diagram so all
edges connect concrete leaf nodes, keeping subgraphs as pure grouping
containers. Verified rendering across mermaid v10.5.1, v10.9.1, and v11.
@pd241008
pd241008 merged commit baca56e into main Aug 4, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant