reportist/plugins/diagnostics
Dandaedre b268af7cb7
Reportist CI Both renderer plugin suites passed.
Beffroi/reportist/pipeline/head This commit looks good Details
Format Reportist shell entry points consistently
2026-09-16 21:07:18 +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 Own report and diagnostic plugins behind one build CLI 2026-09-16 21:03:17 +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 Format Reportist shell entry points consistently 2026-09-16 21:07:18 +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.

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

Themes are default, cic, and eridani. The integration command build.sh render diagnostic CAPTURE.json --output OUTPUT.pdf invokes this renderer.

analyse.sh remains available when normalized diagnostic JSON v1 and evidence pointers are needed. Its output is independent of the source-faithful PDF path.