HTML artifact

Create a finished HTML explanation or report at an explicit destination when that format helps the requested work. Base the content on verified evidence and adapt the design to the audience, project, and user request. Do not turn an application prototype into a static report.

For a self-contained artifact, embed the CSS, essential JavaScript, data, fonts, and images needed at runtime. Use semantic structure, the correct document language, useful text alternatives, keyboard access, visible focus, and reduced motion where applicable. Preserve existing files unless replacing them is within the requested scope.

Inspect the final file and its referenced assets. Verify factual content and use proportionate browser or visual checks when authorized and useful. Link it from existing project documentation only when it belongs there. Return the final file and report material checks that were not performed.

If the project uses an installed Harness, follow its current coordination instructions when relevant. Do not initialize Harness or assume its commands or state format.