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

Clash Manager Export Results To Html Report

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

Coming soon

Before you run this

Active document with a saved clash XML at the canonical path.

After it runs

Single .html file on disk.

When to use this

Don't use this when

Excel / PDF / Word — separate commands.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Load clash XML via ReadWriteClashResultsToXml().ReadResults(). WireError if empty/missing.
2) Resolve output path (resolver or default under doc directory / .mepbridge/qa/reports/).
3) Call BuildSelfContainedClashReportHtml.WriteReport(file, output_path, title, embed_images).
4) Launch default browser (Process.Start) on Human path, skip on Bot.
5) Emit ok + output_path + result_count.

What you'll see in the chat

on start
Building self-contained HTML clash report…
thinking
Loading clash XML…
Writing HTML via BuildSelfContainedClashReportHtml…
on success
HTML report at {output_path}.
on failure
HTML 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_html_report
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagerexportresultstohtmlreport · export clash html · qa html report

PillarClash Manager / Reporting