Commands  ›  Clash Manager / Reporting  ›  Clash Manager Export Results To Pdf Report

Clash Manager Export Results To Pdf Report

Clash Manager / Reporting writes to model Public API · not yet exposed

Coming soon

Before you run this

Active doc; clash XML present.

After it runs

Single file on disk with .pdf extension but HTML payload.

When to use this

Don't use this when

Actual PDF binary — blocked until Chromium headless lands; structure unchanged when it does.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Read clash XML. 2) Resolve output path (default .mepbridge/qa/reports/clashes_{ts}.pdf). 3) Write HTML payload via BuildSelfContainedClashReportHtml. 4) Open in browser on Human. 5) Emit result with mode=html_as_pdf flag so callers know the artifact format.

What you'll see in the chat

on start
Building clash PDF report (HTML-as-PDF)…
thinking
Loading clash XML…
Writing self-contained HTML payload…
on success
PDF written at {output_path}.
on failure
PDF export failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_manager_export_results_to_pdf_report
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagerexportresultstopdfreport · export clash pdf · qa pdf report

PillarClash Manager / Reporting