Initial commit

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Report a problem with ditto.site CLI or service behavior
+title: ""
+labels: bug
+---
+
+**What happened**
+<!-- A clear description of the bug. -->
+
+**To reproduce**
+- Surface: <!-- CLI / REST / MCP -->
+- URL cloned (if applicable):
+- Command or API/MCP call:
+- Options (interactions/components/motion/multiPage/verify, …):
+
+**Expected behavior**
+<!-- What you expected instead. -->
+
+**Environment**
+- OS + Node version (`node -v`):
+- Commit / version:
+- Chromium installed (`npx playwright install chromium`)? 
+
+**Logs / artifacts**
+<!-- Relevant output, the validation report, or a run dir. For a "perfect score",
+     check it isn't a blocked/degenerate capture (capture.pollution / capture.blocked). -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/ion-design/ditto.site/security/advisories/new
+    about: Please report security issues privately — do not open a public issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an improvement to ditto.site
+title: ""
+labels: enhancement
+---
+
+**Problem / motivation**
+<!-- What are you trying to do that's hard or impossible today? -->
+
+**Proposed solution**
+<!-- What you'd like to see. -->
+
+**Alternatives considered**
+<!-- Other approaches you thought about. -->
+
+**Scope notes**
+<!-- Does this touch the deterministic compiler (clone fidelity/gates) or only the
+     service layer? Anything that affects clone output should stay deterministic. -->