docs: launch README, demo scripts, and issue templates

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,78 @@
+name: Bug report
+description: Something doesn't work the way the docs say it should
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing. The most useful thing you can include is the output of
+        `ecluse validate` and `ecluse ls --json` — most issues are visible there.
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What you expected, and what you got instead.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. ecluse init --mode hybrid
+        2. ecluse up feat-foo
+        3. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: config
+    attributes:
+      label: .ecluse.toml
+      description: Redact anything sensitive.
+      render: toml
+    validations:
+      required: true
+
+  - type: textarea
+    id: diagnostics
+    attributes:
+      label: Diagnostics
+      description: Output of `ecluse validate` and `ecluse ls --json`.
+      render: shell
+
+  - type: input
+    id: version
+    attributes:
+      label: ecluse version
+      description: Output of `ecluse --version`
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: OS
+      options:
+        - macOS (Apple Silicon)
+        - macOS (Intel)
+        - Linux
+        - Windows (WSL2)
+    validations:
+      required: true
+
+  - type: dropdown
+    id: runtime
+    attributes:
+      label: Container runtime
+      options:
+        - OrbStack
+        - Docker Desktop
+        - Colima
+        - Podman
+        - Native Docker (Linux)
+        - None (host mode)
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Question or idea
+    url: https://github.com/hefgi/ecluse/discussions
+    about: Questions, workflow ideas, and "how would I do X" go in Discussions.
+  - name: Documentation
+    url: https://ecluse.ai
+    about: Configuration reference, command reference, and known limits.

.github/ISSUE_TEMPLATE/stack_support.yml

@@ -0,0 +1,45 @@
+name: Stack didn't work
+description: ecluse init detected the wrong thing, or your stack needs config it can't express
+labels: ["stack-support"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Detection getting a repo wrong is treated as a bug here, not user error. The more
+        stacks reported, the better detection gets — so these are genuinely welcome.
+
+  - type: input
+    id: stack
+    attributes:
+      label: Stack
+      placeholder: Rails 7 + Postgres + Sidekiq, or Next.js monorepo with Turborepo
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected ecluse to do
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: What it actually did
+      description: Include the `ecluse init` output if detection was wrong.
+    validations:
+      required: true
+
+  - type: textarea
+    id: config
+    attributes:
+      label: Generated .ecluse.toml (and your corrected version, if you fixed it)
+      render: toml
+
+  - type: textarea
+    id: compose
+    attributes:
+      label: Relevant docker-compose.yml
+      description: Only the parts that matter. Redact secrets.
+      render: yaml