Add reproducer and sample-request issue templates with README guidance

Add reproducer and sample-request issue templates

Maintainers triaging this app had no structured front door for bug reports
or sample requests. Bug reports landed as free-form prose without the
workflow class, artisan command, package version, or operator-visible
durable failure that turn a report into a runnable reproducer. Sample
requests landed without the pattern name, target Durable Workflow version,
or external dependencies needed to scope the work.

.github/ISSUE_TEMPLATE/ now ships three files:

- bug_report.yml asks for the workflow class, the artisan command that
triggers the failing path, expected vs observed behavior, a redacted
history-export excerpt, the Durable Workflow package version, the sample
app commit, the PHP version, and the queue/cache backend. A contribution
checkbox invites the reporter to open a PR that lands the reproducer
under app/Workflows/Bug/.
- sample_request.yml asks for the pattern name, motivation linked to the
public docs, a sketch of the workflow shape, the minimum Durable Workflow
version, and any external dependencies. A contribution checkbox invites
the reporter to open a PR that lands the sample under app/Workflows/.
- config.yml turns off blank issues and links out to the docs site, the
README sample index, and the workflow/server repos for engine-level and
server-level bugs that do not need the Laravel sample to reproduce.

README.md grows a "Reporting Bugs and Requesting Samples" section that
points operators at the chooser and explains what each template lands so
contributors know up front what good reproducers and sample requests look
like.

Verified:
- bash scripts/check-public-boundary.sh -> exit 0
- python -c 'import yaml; yaml.safe_load(open(f))' for each template

Author: durable-workflow-ops

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,119 @@
+name: Bug reproducer
+description: A reproducer for an upstream Durable Workflow bug, runnable against this sample app.
+title: "[bug] <short description of the failing pattern>"
+labels:
+  - bug
+  - reproducer
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template to file a reproducer that runs inside this sample app.
+
+        A good reproducer is small, deterministic, and isolates the failing pattern: one
+        workflow class, one command to start it, and one expected outcome. If your bug is
+        in the engine itself and does not need Laravel scaffolding, file it on the
+        [`workflow` repo](https://github.com/durable-workflow/workflow/issues/new/choose)
+        instead. If it is in the standalone Durable Workflow server, file it on the
+        [`server` repo](https://github.com/durable-workflow/server/issues/new/choose).
+
+        Reproducers that follow this template land as new sample-app workflows, get
+        wired into CI, and stay reproducible after the bug is fixed.
+
+  - type: input
+    id: workflow_class
+    attributes:
+      label: Workflow class under test
+      description: Fully qualified class name. Existing samples live under `App\Workflows\`.
+      placeholder: App\Workflows\Bug\IssueNNNRepro\IssueNNNWorkflow
+    validations:
+      required: true
+
+  - type: input
+    id: start_command
+    attributes:
+      label: Command to start the reproducer
+      description: An `artisan` command that the reader can run after `composer install` to trigger the failing path.
+      placeholder: php artisan app:bug-issue-NNN
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: What the durable contract is supposed to do. Reference docs, history events, or operator-visible state where possible.
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Observed behavior
+      description: What you actually see. Include workflow status, durable failure type, and the operator surface (Waterline, history export, CLI output) where you observed it.
+    validations:
+      required: true
+
+  - type: textarea
+    id: history_excerpt
+    attributes:
+      label: History excerpt
+      description: |
+        A short, redacted slice of `php artisan workflow:v2:history-export` for the failing run.
+        Trim payload bodies; the event sequence and event kinds are usually enough.
+      render: text
+
+  - type: input
+    id: durable_workflow_version
+    attributes:
+      label: Durable Workflow package version
+      description: Run `composer show durable-workflow/workflow` and paste the resolved version.
+      placeholder: 2.0.0-alpha.5
+    validations:
+      required: true
+
+  - type: input
+    id: sample_app_commit
+    attributes:
+      label: Sample app commit
+      description: Output of `git rev-parse --short HEAD` in your sample-app checkout.
+      placeholder: abc1234
+    validations:
+      required: true
+
+  - type: input
+    id: php_version
+    attributes:
+      label: PHP version
+      description: Output of `php -r 'echo PHP_VERSION;'`.
+      placeholder: "8.3.10"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: backend
+    attributes:
+      label: Queue and cache backend
+      description: Which `QUEUE_CONNECTION` and cache store you used when the bug reproduced.
+      options:
+        - Redis (default sample-app docker compose)
+        - Database (sync queue + database cache)
+        - Other (describe in additional context)
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: Logs, exporter output, related issues, or anything else a maintainer needs to land the reproducer.
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Reproducer contribution
+      options:
+        - label: I am willing to open a pull request that adds this reproducer as a workflow under `app/Workflows/Bug/`.
+          required: false
+        - label: I checked that the bug reproduces against the latest `main` of this repo.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Durable Workflow documentation
+    url: https://durable-workflow.com/docs/2.0/
+    about: Reference for the v2 engine, polyglot worker contracts, and operator tooling.
+  - name: Sample App README
+    url: https://github.com/durable-workflow/sample-app#readme
+    about: How to run the bundled samples and the table of patterns each one demonstrates.
+  - name: Workflow engine bug
+    url: https://github.com/durable-workflow/workflow/issues/new/choose
+    about: Open here when the bug reproduces with a minimal program against the workflow package itself, not this Laravel sample.
+  - name: Standalone server bug
+    url: https://github.com/durable-workflow/server/issues/new/choose
+    about: Open here when the bug reproduces against the standalone Durable Workflow server image, not this Laravel sample.

.github/ISSUE_TEMPLATE/sample_request.yml

@@ -0,0 +1,84 @@
+name: Sample request
+description: Ask for a Durable Workflow pattern that this sample app does not yet demonstrate.
+title: "[sample] <short description of the requested pattern>"
+labels:
+  - sample-request
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template to request a sample workflow that demonstrates a Durable Workflow
+        pattern not yet covered by this app. The current sample index lives in the
+        [README sample table](https://github.com/durable-workflow/sample-app#sample-index).
+
+        Sample requests close when a workflow lands under `app/Workflows/` that exercises
+        the pattern end to end and is wired into both the artisan command list and the MCP
+        config in `config/workflow_mcp.php`.
+
+  - type: input
+    id: pattern
+    attributes:
+      label: Pattern name
+      description: A short name for the pattern. Used as the working title for the sample workflow.
+      placeholder: child workflow with parent-close-policy abandon
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Why this pattern matters
+      description: |
+        What real durable-workflow problem does this pattern solve? Link the public docs
+        page or feature reference that defines it where possible.
+    validations:
+      required: true
+
+  - type: textarea
+    id: shape
+    attributes:
+      label: Suggested workflow shape
+      description: |
+        Outline the workflow class, activities, signals, updates, and the operator-visible
+        outcome you want the sample to demonstrate. Pseudocode is fine.
+    validations:
+      required: true
+
+  - type: input
+    id: durable_workflow_version
+    attributes:
+      label: Minimum Durable Workflow version
+      description: Earliest workflow package version this pattern needs to work on.
+      placeholder: 2.0.0-alpha.5
+    validations:
+      required: true
+
+  - type: dropdown
+    id: external_dependencies
+    attributes:
+      label: External dependencies
+      description: Does the sample need anything beyond the default Laravel + Redis stack?
+      options:
+        - None — runs on the default sample-app stack
+        - Browser automation (Playwright / Node)
+        - LLM provider key (OPENAI_API_KEY or similar)
+        - Additional service (describe in notes)
+    validations:
+      required: true
+
+  - type: textarea
+    id: notes
+    attributes:
+      label: Notes for the implementer
+      description: |
+        Anything that would block the sample from landing today (missing engine feature,
+        upstream contract, docs gap). If a missing feature blocks the sample, link the
+        upstream issue and call it out here so the request can be queued behind that work.
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Sample contribution
+      options:
+        - label: I am willing to open a pull request that adds this sample workflow to `app/Workflows/`.
+          required: false

README.md

@@ -291,6 +291,15 @@ An AI client would typically:
 4. Poll `get_workflow_result` with the `workflow_id` until status is `completed`
 5. Read the `output` field for the workflow result
 6. If status is `failed` or `waiting` longer than expected, call `diagnose_workflow`, then inspect `get_workflow_history` with the `run_id`
+## Reporting Bugs and Requesting Samples
+
+Use the structured templates under [Issues](https://github.com/durable-workflow/sample-app/issues/new/choose) so reproducers and sample requests land with the metadata maintainers need:
+
+- **Bug reproducer.** A reproducer runs in this app: it names the workflow class, the artisan command, the Durable Workflow package version, and the observed durable failure. Reproducers that follow the template land as new workflows under `app/Workflows/Bug/<issue>/` and stay covered by CI after the bug is fixed.
+- **Sample request.** A sample request names the Durable Workflow pattern that is not yet covered, the public docs page that defines it, and the minimum package version it needs. Requests close when a workflow under `app/Workflows/` exercises the pattern end to end and is wired into the artisan command list and `config/workflow_mcp.php`.
+
+Bugs in the workflow engine itself or the standalone Durable Workflow server belong on the [`workflow`](https://github.com/durable-workflow/workflow/issues/new/choose) and [`server`](https://github.com/durable-workflow/server/issues/new/choose) repos respectively; the issue chooser links those out.
+
 ## Public Boundary Checks
 
 This is a public repository. Do not add private tracker names, workspace-only absolute paths, or loop/lane metadata to files or new commit metadata. Run `scripts/check-public-boundary.sh` before publishing changes; CI runs the same scan on pushes and pull requests.