` links (data:/blob: hrefs included) and script-driven saves are inert for viewers — so never offer a file through a plain link. Artifacts render mermaid diagrams natively — markdown via ```mermaid fences, HTML via `` blocks — no external libraries involved.
-**Size**: The rendered page must be ${MAX_ARTIFACT_BYTES / 1024 / 1024}MB or smaller, and embedded data: URIs count toward that.
+**Size**: The rendered page must be ${MAX_ARTIFACT_BYTES/1024/1024}MB or smaller, and embedded data: URIs count toward that.
**Responsive**: Use relative units, flexbox/grid, `max-width:100%` on images. Wide content (tables, diagrams, code blocks) must scroll inside its own `overflow-x: auto` container — the page body must never scroll horizontally.
diff --git a/system-prompts/tool-description-artifact-supporting-files-guidance.md b/system-prompts/tool-description-artifact-supporting-files-guidance.md
index c63d65a..0ba07fc 100644
--- a/system-prompts/tool-description-artifact-supporting-files-guidance.md
+++ b/system-prompts/tool-description-artifact-supporting-files-guidance.md
@@ -8,5 +8,5 @@ variables:
- "MAX_SUPPORTING_FILE_COUNT"
- "MANIFEST_TOTAL_BUDGET_BYTES"
-->
-**Supporting files**: To publish a multi-file artifact (separate CSS/JS/data/images), pass `files` as a map of published path → source file: `{"app.js": "dist/app.js", "data/points.json": "build/points.json"}`. The published path (the key) is what the HTML references (`