reportist/plugins/diagnostics
Dandaedre 7d428f71d9
Reportist CI Both renderer plugin suites passed.
Beffroi/reportist/pipeline/head This commit looks good Details
Add color-only Ravenous palettes to shared themes
2026-09-17 00:15:07 +02:00
..
examples Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
renderer Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
runtime/rules Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
schemas Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
tests Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
tools Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
LICENSE Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
README.md Add color-only Ravenous palettes to shared themes 2026-09-17 00:15:07 +02:00
analyse-all.sh Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
analyse.sh Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +02:00
render.sh Add color-only Ravenous palettes to shared themes 2026-09-17 00:15:07 +02:00

README.md

Diagnostic plugin

The diagnostic renderer consumes a raw WinDiagnostics JSON v1/v2 capture and builds its PDF with renderer/render.typ, renderer/normalize.typ, and renderer/model.typ. It imports graphical elements and palettes from the local Reportist visual module; it does not convert the capture into a report model. From the Reportist repository root:

./build.sh render diagnostic /path/to/capture.json --output diagnostic.pdf --author 'Reviewer' --theme cic

Named themes are listed in the palette catalog.

./build.sh analyze produces normalized diagnostic JSON v1 with evidence pointers when needed. Its output is independent of the source-faithful PDF.

The plugin supplies evidence validation through the same CLI. See the plugin guide for ownership rules and tests.