add client issue and release scaffolding

.gitea/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,17 @@
+name: Bug report
+description: Report a reproducible client defect.
+title: 'bug: '
+labels: [bug]
+body:
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction and expected behavior
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Client version or commit
+    validations:
+      required: true

.gitea/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,18 @@
+name: Feature request
+description: Propose a client-side change.
+title: 'feature: '
+labels: [enhancement]
+body:
+  - type: textarea
+    id: behavior
+    attributes:
+      label: Desired behavior and affected states
+    validations:
+      required: true
+  - type: checkboxes
+    id: plan
+    attributes:
+      label: Planning
+      options:
+        - label: I checked PLAN.md and this does not silently change an existing decision.
+          required: true

.gitea/workflows/release-check.yaml

@@ -0,0 +1,17 @@
+name: Client release check
+
+on:
+  workflow_dispatch:
+  push:
+    tags: ['v*.*.*']
+
+jobs:
+  release-check:
+    runs-on: debian-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+      - run: test -s CHANGELOG.md && npm ci && npm run format:check && npm run check && npm run build

CHANGELOG.md

@@ -0,0 +1,8 @@
+# Changelog
+
+Notable client changes are recorded here using the Keep a Changelog format.
+Stable release entries require explicit user authorization.
+
+## [Unreleased]
+
+- Add administrator backup inventory and manual backup controls.