docs: establish the OSS contribution front door

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,147 @@
+name: Bug report
+description: Berd does something other than what it says it does
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time. A report we can reproduce without asking you
+        anything is worth a great deal to us.
+
+        Before you start, please read
+        [the bug report section of CONTRIBUTING.md](https://github.com/block/berd/blob/main/CONTRIBUTING.md#bug-reports).
+        You're welcome to have an agent help you fill this in — see
+        [Using an agent](https://github.com/block/berd/blob/main/CONTRIBUTING.md#using-an-agent).
+
+        **Do not report security vulnerabilities here.** Use
+        [SECURITY.md](https://github.com/block/berd/blob/main/SECURITY.md).
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Before filing
+      description: All three are required. Please actually do them.
+      options:
+        - label: I searched [open and closed issues](https://github.com/block/berd/issues?q=is%3Aissue) for duplicates.
+          required: true
+        - label: I reproduced this on the [latest release](https://github.com/block/berd/releases).
+          required: true
+        - label: This is one bug, not several bundled together.
+          required: true
+
+  - type: input
+    id: duplicate-search
+    attributes:
+      label: Closest existing issue
+      description: Link the nearest thing you found, or write "none found".
+      placeholder: "#123, or none found"
+    validations:
+      required: true
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: What's broken
+      description: One or two sentences. Save the detail for the fields below.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      description: |
+        Numbered, starting from a freshly launched Berd. Include the model and
+        provider, whether the chat had prior history, and anything about your
+        setup that might matter.
+      value: |
+        1. Launch Berd
+        2.
+        3.
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected to happen
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: What actually happened
+    validations:
+      required: true
+
+  - type: dropdown
+    id: frequency
+    attributes:
+      label: How often does it happen?
+      description: This changes how we chase it more than almost anything else.
+      options:
+        - Every time — reliably reproducible
+        - Intermittently — happens often but not always
+        - Once — I have not been able to reproduce it
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Berd version
+      description: 'Settings → About. If Berd will not launch, write "cannot launch".'
+      placeholder: "0.6.0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating system
+      options:
+        - macOS (Apple Silicon)
+        - macOS (Intel)
+        - Linux
+        - Windows
+    validations:
+      required: true
+
+  - type: input
+    id: model
+    attributes:
+      label: Model and provider
+      description: If the bug involves a chat or an agent turn. Otherwise "n/a".
+      placeholder: "Claude Sonnet 4.5 via Anthropic"
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        The lines around when the problem happened — not the whole file, not a
+        screenshot of text. **Scrub anything private first**: logs can contain
+        file paths, prompt text, and project names.
+
+        macOS `~/Library/Logs/xyz.block.berd/` · Linux
+        `~/.local/share/xyz.block.berd/logs/` · Windows
+        `%LOCALAPPDATA%\xyz.block.berd\logs\`
+
+        If there is genuinely nothing relevant, write "no relevant log output"
+        so we know you looked.
+      render: text
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Screenshots, recordings, or other context
+      description: |
+        Required for anything visual — a few seconds of capture saves an hour of
+        back-and-forth. Drag files in to attach them.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +1,14 @@
-blank_issues_enabled: true
+# The normal GitHub UI does not offer a blank issue: a well-formed issue is the
+# supported way to participate in Berd, so the forms ask for what we need to act
+# on it. API-created issues remain subject to the same policy. See CONTRIBUTING.md.
+blank_issues_enabled: false
+contact_links:
+  - name: Questions about using Berd
+    url: https://github.com/block/berd/blob/main/README.md
+    about: The README covers setup, building, and how Berd is put together. The issue tracker is not a support channel.
+  - name: Security vulnerabilities
+    url: https://github.com/block/berd/blob/main/SECURITY.md
+    about: Please report privately — never as a public issue.
+  - name: How to participate
+    url: https://github.com/block/berd/blob/main/CONTRIBUTING.md
+    about: What we accept, what makes a good issue, and why we don't take outside pull requests.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,117 @@
+name: Feature request
+description: You want Berd to do something it doesn't, or to do something existing noticeably better
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We want to understand the **problem**, not just the solution you have in
+        mind — the problem often has a better answer than the one you'd have
+        asked for.
+
+        Before you start, please read
+        [the feature request section of CONTRIBUTING.md](https://github.com/block/berd/blob/main/CONTRIBUTING.md#feature-requests).
+        You're welcome to have an agent help you fill this in — see
+        [Using an agent](https://github.com/block/berd/blob/main/CONTRIBUTING.md#using-an-agent).
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Before filing
+      description: All three are required. Please actually do them.
+      options:
+        - label: I searched [open and closed issues](https://github.com/block/berd/issues?q=is%3Aissue) for duplicates.
+          required: true
+        - label: I am using a recent [release](https://github.com/block/berd/releases) and this doesn't already exist.
+          required: true
+        - label: This is one request, not several bundled together.
+          required: true
+
+  - type: input
+    id: duplicate-search
+    attributes:
+      label: Closest existing issue
+      description: Link the nearest thing you found, or write "none found".
+      placeholder: "#123, or none found"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Is this new, or an improvement?
+      options:
+        - New capability — Berd can't do this at all today
+        - Improvement — Berd does this, but badly
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: The problem, in your terms
+      description: |
+        What were you trying to get done, and what made it hard? Describe the
+        situation, not the feature. Lead with this.
+    validations:
+      required: true
+
+  - type: textarea
+    id: today
+    attributes:
+      label: What you do today
+      description: |
+        Your current workaround, however ugly — or "nothing, I gave up". This
+        tells us how much the gap actually costs you.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: What you'd like to see
+      description: Your proposed change. Rough is fine.
+    validations:
+      required: true
+
+  - type: textarea
+    id: why-core
+    attributes:
+      label: Why this belongs in Berd itself
+      description: |
+        Berd is extensible on purpose. Could this be a
+        [skill](https://github.com/block/berd/tree/main/.agents/skills), an
+        agent, an extension, or an automation instead? If it could and you still
+        think it should be built in, say why. If it genuinely can't be done from
+        outside, say that — it's a strong argument.
+    validations:
+      required: true
+
+  - type: textarea
+    id: non-goals
+    attributes:
+      label: Non-goals
+      description: |
+        What are you explicitly **not** asking for? This is the most useful line
+        in a feature request and almost nobody writes it — it tells us where the
+        edges of your idea are.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you considered
+      description: Including the ones you rejected, and why.
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Mockups, prior art, or other context
+      description: |
+        Screenshots, sketches, or examples of other tools that get this right.
+        Drag files in to attach them.
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,3 +1,9 @@
+<!--
+  Berd does not accept pull requests from outside authorized repository
+  collaborators, and outside PRs are closed automatically. If that's you: please don't
+  spend time on a patch. Open an issue instead — https://github.com/block/berd/blob/main/CONTRIBUTING.md
+-->
+
 ## Summary
 <!-- What does this change and why? -->