Create a polished standalone visual HTML documentation page

Use This Prompt

Create a polished standalone visual HTML documentation page from the project documentation in this workspace. Requirements: read the relevant Markdown/source docs first and preserve technical facts; create a new HTML file, do not overwrite existing docs unless asked; use embedded CSS only so the file is portable; make it presentation-quality, not a plain Markdown export; include a left-side navigation rail; add a strong hero section with the project name, purpose, and current status; add status cards for key versions, components, risks, and confirmations; add inline SVG diagrams where useful to explain the end-to-end process flow, routing or decision logic, external system/database/API interactions, and error handling or framework services; use tables for component inventories, open risks, and next steps; avoid stale claims; verify current component versions, execution evidence, and dependency status before writing; clearly distinguish proven facts from historical notes or old test failures; do not include decorative filler; every visual should help someone understand the system; make it print-friendly and responsive; after creating the HTML, verify the file opens as standalone HTML, the expected headings/sections exist, the diagrams render as inline SVG, no stale risk language remains, and the HTML references current facts from the source docs. Suggested filename: core-project-documentation-visual.html. Tone: professional, executive-readable, and technically accurate. The output should help a new stakeholder understand the complete process quickly without needing to read every raw component XML file.

What It Should Produce