Commands  ›   ›  Export Clash Results To Html Report

Export Clash Results To Html Report

writes to model Public API · not yet exposed

Coming soon

What you'll see in the chat

on start
Building HTML clash report with embedded images…
thinking
Loading latest clashresults XML…
Embedding screenshots as base64 data URIs…
Writing self-contained HTML to .mepbridge/qa/exports…
on success
HTML clash report written to {path} ({rows} rows, {images} embedded images).
on failure
HTML clash 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/export_clash_results_to_html_report
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

export clashes html · clash report html · qa html report · portable clash report · export errors html

Pillar