docs: enforce vgraph demo artifact delivery

skills/vgraph-development-assistant/SKILL.md

@@ -70,7 +70,7 @@ Before writing code, choose the surface:
 
 ## Demo Artifact Defaults
 
-When the user asks for a standalone, previewable, or showcase-style VGraph demo page, such as an HTML demo, runnable visualization, structure diagram, knowledge map, or code-tab page, create a runnable standalone HTML demo instead of only pasting code in chat, unless the user explicitly asks for a snippet/config only. Read `references/examples/demo-html-page.md` for the page shell and readability patterns.
+When the user asks for a standalone, previewable, or showcase-style VGraph demo page, such as an HTML demo, runnable visualization, structure diagram, knowledge map, or code-tab page, treat a runnable artifact as the deliverable. Create or update an actual HTML/demo file instead of only pasting code in chat, unless the user explicitly asks for a snippet/config only. Read `references/examples/demo-html-page.md` for the page shell, readability patterns, and delivery gate.
 
 For simple examples, API usage, configuration help, or debugging answers, prefer a focused TypeScript snippet unless a runnable page would materially improve verification.
 
@@ -82,6 +82,8 @@ For knowledge-system or structure-map demos, preserve semantic shape before visu
 
 After creating a standalone HTML demo, verify that it renders without console errors. If the environment supports browser preview, start or reuse a local static/dev server and provide the accessible URL; if browser preview is unavailable, say what validation was skipped and why.
 
+Do not produce the final answer for a standalone/demo-page request until these are true: a file was created or updated, the user has a consumable path/link, the answer explains how to open or verify it, and the chat response summarizes rather than dumping the full source. If any item is missing, continue implementation or state the concrete blocker instead of presenting the task as complete.
+
 ## VGraph-Specific Anti-Patterns
 
 - Do not use `TreeGraph` with edge lists; tree edges are derived from `children`.

skills/vgraph-development-assistant/references/examples/demo-html-page.md

@@ -1,6 +1,19 @@
 # Standalone HTML Demo Page
 
-Use this pattern when the user asks for a standalone, previewable, or showcase-style VGraph demo, such as an HTML demo, runnable visualization, structure diagram, knowledge map, or code-tab page. For simple API usage, configuration help, or debugging answers, prefer a focused TypeScript snippet unless a runnable page materially improves verification.
+Use this pattern when the user asks for a standalone, previewable, or showcase-style VGraph demo, such as an HTML demo, runnable visualization, structure diagram, knowledge map, or code-tab page. This is an artifact task: the deliverable is a runnable file, not only chat code.
+
+For simple API usage, configuration help, or debugging answers, prefer a focused TypeScript snippet unless a runnable page materially improves verification. If the request says "create", "generate", "build", "show", "make a demo", "previewable", "HTML", "page", "knowledge map", "structure diagram", or "runnable visualization", classify it as an artifact task unless the user explicitly asks for a snippet/config only.
+
+## Delivery gate
+
+Before the final answer for an artifact task, verify all items:
+
+- A standalone HTML/demo file was created or updated.
+- The response gives the user a consumable path, link, or preview URL.
+- The response explains how to open or validate the demo.
+- The response summarizes the implementation and does not paste the full source into chat.
+
+If any item is false, do not present the task as complete. Continue creating the artifact or state the exact blocker.
 
 ## Demo page requirements