feat: shared dual-arch Docker build workflow (GitHub runners, no ARC)

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,33 @@
+name: Bug Report
+description: Create a bug report to help us improve
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Do not report security vulnerabilities here. Any such issue will be deleted on sight.
+        Report them privately via [GitHub security advisories](https://github.com/EduIDE/.github/security/advisories/new) instead - see SECURITY.md.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+  - type: input
+    attributes:
+      label: Cluster provider
+      description: The cluster provider (e.g. Minikube, AWS, GKE, Azure, Docker Desktop). Please include your OS when using a local cluster. If you are using Terraform, please include the configuration files if possible.
+  - type: input
+    attributes:
+      label: Version
+      description: The used version. Such as the helm chart version or the commit id the bug was discovered on
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Additional information to analyze the bug such as logs, screenshots, screencasts.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/orgs/EduIDE/discussions
+    about: Ask questions about using or running EduIDE here.
+  - name: Documentation
+    url: https://eduide.github.io/Docs/
+    about: Guides for students, instructors, administrators and developers.
+  - name: Report a security vulnerability
+    url: https://github.com/EduIDE/.github/security/advisories/new
+    about: Report privately. Do not open a public issue for security problems.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,30 @@
+name: Feature request
+description: Suggest an idea for this project
+labels: enhancement
+body:
+- type: textarea
+  validations:
+    required: true
+  attributes:
+    label: Is your feature request related to a problem? Please describe.
+    description: A clear and concise description of what the problem is. E.g. I'm always frustrated when [...]
+- type: textarea
+  validations:
+    required: true
+  attributes:
+    label: Describe the solution you'd like
+    description: A clear and concise description of what you want to happen.
+- type: textarea
+  validations:
+    required: true
+  attributes:
+    label: Describe alternatives you've considered
+    description: A clear and concise description of any alternative solutions or features you've considered.
+- type: input
+  attributes:
+    label: Cluster provider
+    description: The cluster provider (e.g. Minikube, AWS, GKE, Azure, Docker Desktop) the feature is for. Leave out if the feature is not related to (a) specific provider(s).
+- type: textarea
+  attributes:
+    label: Additional information
+    description: Any additional information to describe the feature such as screenshots, diagrams, etc.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,36 @@
+<!--
+Org-wide default. A repository can override this with its own
+.github/PULL_REQUEST_TEMPLATE.md.
+-->
+
+## What and why
+
+<!-- What changes, and what problem it solves. Link the issue if there is one. -->
+
+## How it was verified
+
+<!--
+Say what you actually ran, not what you intended to run.
+Examples:
+  - helm template for all environments, diff empty except labels
+  - deployed to test2 via /deploy, started a session end to end
+  - unit tests: N passing
+If it was not verified, say so.
+-->
+
+## Deployment impact
+
+<!-- Delete the lines that do not apply. -->
+
+- [ ] Changes a Helm chart (chart `version` bumped)
+- [ ] Changes a published image
+- [ ] Requires a config change in EduIDE-deployment
+- [ ] Requires a cluster-level change (CRDs, Gateway, ClusterRoles)
+- [ ] None of the above
+
+## Risk and rollback
+
+<!--
+What breaks if this is wrong, and how do you undo it?
+"helm rollback" is a fine answer. "Not sure" is also a fine answer - say it.
+-->

.github/workflows/auto-assign.yml

@@ -0,0 +1,48 @@
+# Reusable: assign a pull request to its author.
+#
+# GitHub does NOT inherit workflows from the org .github repository - only
+# community health files (issue templates, PR template, SECURITY.md, and so on)
+# are inherited. So this cannot simply replace the copies in each repository.
+# Instead each repository keeps a short caller:
+#
+#   name: Auto Assign PR Author
+#   on:
+#     pull_request:
+#       types: [opened, reopened, ready_for_review]
+#   jobs:
+#     auto-assign:
+#       uses: EduIDE/.github/.github/workflows/auto-assign.yml@v1
+#
+# That keeps the logic in one place while respecting the platform constraint.
+
+name: Auto Assign PR Author
+
+on:
+  workflow_call:
+
+jobs:
+  auto-assign:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+      - name: Auto assign PR author
+        uses: actions/github-script@v7
+        with:
+          script: |
+            // Dependabot and other bots do not benefit from being assigned.
+            const login = context.payload.pull_request.user.login;
+            if (context.payload.pull_request.user.type === 'Bot') {
+              core.info(`Skipping bot author ${login}`);
+              return;
+            }
+            if (context.payload.pull_request.assignees.length > 0) {
+              core.info('PR already has assignees; leaving them alone.');
+              return;
+            }
+            await github.rest.issues.addAssignees({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: context.issue.number,
+              assignees: [login],
+            });