Add propose-event issue form and thin issue-to-pr workflow

The issue form carries the ote-event label (a labels= URL param only
applies with triage permission, which proposers don't have). The
workflow filters by label at job level — on: issues can't — and also
listens to pull_request closed so the reusable workflow can delete
ote/* branches after merge. All logic stays in ote-tools.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: hhkaos

.github/ISSUE_TEMPLATE/propose-event.yml

@@ -0,0 +1,17 @@
+# Issue form used by the OTE editor's "propose change" flow. The editor
+# prefills this template via URL params; the `ote-event` label below is what
+# triggers the issue-to-pr workflow. The label must come from the template:
+# a `labels=` URL param only applies if the issue author has triage
+# permission on the repo, which event proposers normally don't.
+name: Propose an event
+description: Propose a new event or a change to an existing one. Prefer the editor linked from the dashboard — it fills this form for you.
+labels: [ote-event]
+body:
+  - type: textarea
+    id: event-json
+    attributes:
+      label: Event JSON
+      description: The full OTE event document. The editor generates this — you rarely need to write it by hand.
+      render: json
+    validations:
+      required: true

.github/workflows/issue-to-pr.yml

@@ -0,0 +1,19 @@
+# Turns an `ote-event` issue (opened by the OTE editor) into a pull request,
+# and cleans up the `ote/*` branch after the PR is merged (the pull_request
+# closed event). All logic lives in OpenTechEvents/ote-tools — this file only
+# calls it. @main will become @v1 once the reusable workflows stabilise.
+name: Issue to PR
+on:
+  issues:
+    types: [opened, edited]
+  pull_request:
+    types: [closed]
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+jobs:
+  issue-to-pr:
+    # `on: issues` can't filter by label, so the label check lives here.
+    if: github.event_name == 'pull_request' || contains(github.event.issue.labels.*.name, 'ote-event')
+    uses: OpenTechEvents/ote-tools/.github/workflows/issue-to-pr.yml@main

README.md

@@ -127,6 +127,13 @@ request, so mistakes can't reach your published feed. The **editor** linked
 from your dashboard (create/edit events via a form, proposed as a PR to your
 repo) is coming in phase 2.
 
+**Propose an event without touching JSON**: anyone can fill in the
+[OTE editor](https://tools.opentechevents.org/editor?repo=your-user/your-repo)
+(replace `your-user/your-repo` with your fork, or just follow the link from
+your dashboard). It generates the event JSON and opens a prefilled issue in
+your repo; a workflow validates it and turns it into a pull request for you
+to review and merge. No git, no JSON editing, no write access needed.
+
 ## Updates
 
 The thin workflows track `OpenTechEvents/ote-tools@main` (pinned to `@v1` once