Add Gitea Actions workflows, CI config, and docs

.gitea/ISSUE_TEMPLATE/auth_security.yml

@@ -0,0 +1,59 @@
+name: Authentication & Security
+about: Report a security concern or suggest a security enhancement
+title: "[Security] "
+labels:
+  - security
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **For actual vulnerabilities, do NOT use this template.**
+        Email security@hiddenden.cafe instead. See SECURITY.md.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Summary of the authentication / security concern or enhancement.
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Detailed description (vulnerability, misconfiguration, missing control).
+    validations:
+      required: true
+
+  - type: textarea
+    id: affected
+    attributes:
+      label: Affected Components
+      description: List services, endpoints, or libraries affected.
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction / PoC
+      description: Steps to reproduce. Do NOT include exploit payloads in public issues.
+
+  - type: textarea
+    id: remediation
+    attributes:
+      label: Suggested Remediation
+      description: Concrete steps to fix, including links to standards or CVE info.
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Links to auth standards (OAuth2, OIDC), encryption recommendations, or policy.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: Confirmed requirement with security lead
+        - label: Unit/integration tests planned for fix

.gitea/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,62 @@
+name: Bug Report
+about: Report a bug or unexpected behavior
+title: "[Bug] "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug! Please fill out the sections below.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: How can we reproduce this issue?
+      placeholder: |
+        1. Go to '...'
+        2. Click on '...'
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+    validations:
+      required: true
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, browser, version, etc.
+      placeholder: |
+        - OS: Ubuntu 22.04
+        - Python: 3.11
+        - Version: v1.2.3
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / Screenshots
+      description: Paste any relevant logs or screenshots.

.gitea/ISSUE_TEMPLATE/collaboration_tools.yml

@@ -0,0 +1,47 @@
+name: Collaboration Tools
+about: Request or suggest collaboration tools and integrations
+title: "[Collab] "
+labels:
+  - tooling
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What tool or integration are you suggesting?
+    validations:
+      required: true
+
+  - type: textarea
+    id: current
+    attributes:
+      label: Current Tools
+      description: What tools are currently used and what are the pain points?
+
+  - type: textarea
+    id: suggested
+    attributes:
+      label: Suggested Tools / Integrations
+      description: List candidate tools and why they would help.
+    validations:
+      required: true
+
+  - type: textarea
+    id: criteria
+    attributes:
+      label: Evaluation Criteria
+      description: "How to evaluate: cost, security, ease of use, integration with repo/CI."
+
+  - type: textarea
+    id: pilot
+    attributes:
+      label: Pilot Plan
+      description: Suggested pilot scope (team, duration, KPIs).
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: Stakeholder signoff obtained
+        - label: Pilot resources allocated

.gitea/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,12 @@
+# Issue template chooser configuration
+# See: https://docs.gitea.com/usage/issue-pull-request-templates
+
+blank_issues_enabled: true
+
+contact_links:
+  - name: Security Vulnerability
+    url: https://git.hiddenden.cafe
+    about: >
+      DO NOT open a public issue for security vulnerabilities.
+      Please email security@hiddenden.cafe or see SECURITY.md for
+      responsible disclosure instructions.

.gitea/ISSUE_TEMPLATE/dev_workflow.yml

@@ -0,0 +1,47 @@
+name: Development Workflow Improvement
+about: Suggest improvements to CI, branching, release process, or dev workflow
+title: "[Workflow] "
+labels:
+  - workflow
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Short summary of the workflow improvement.
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: Current pain points and inefficiencies in the dev workflow.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed
+    attributes:
+      label: Proposed Change
+      description: Describe exact changes (branch naming, CI steps, commit message format, etc.).
+    validations:
+      required: true
+
+  - type: textarea
+    id: migration
+    attributes:
+      label: Migration Plan
+      description: How to migrate existing repos/teams, training, or automation required.
+
+  - type: textarea
+    id: risks
+    attributes:
+      label: Risks
+      description: Potential issues and mitigations.
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance Criteria
+      description: How we'll know the workflow is improved (metrics or qualitative feedback).

.gitea/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,38 @@
+name: Feature Request
+about: Suggest a new feature or improvement
+title: "[Feature] "
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Have an idea? We'd love to hear it!
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / Motivation
+      description: What problem does this feature solve?
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the feature or change you'd like.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Any alternative solutions or workarounds you've considered?
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Screenshots, mockups, links, or anything else.

.gitea/ISSUE_TEMPLATE/performance_improvement.yml

@@ -0,0 +1,61 @@
+name: Performance Improvement
+about: Report a performance problem or request an optimization
+title: "[Performance] "
+labels:
+  - performance
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Short summary of the performance problem or optimization.
+    validations:
+      required: true
+
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed Behavior
+      description: What is currently happening? Include metrics, traces, screenshots.
+    validations:
+      required: true
+
+  - type: textarea
+    id: target
+    attributes:
+      label: Expected Behavior / Target
+      description: "What improvement do we expect? e.g. latency < 200ms, memory < X MB."
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction / Benchmark
+      description: How to reproduce or reference a benchmark (commands, dataset, environment).
+
+  - type: textarea
+    id: optimization
+    attributes:
+      label: Proposed Optimization
+      description: High-level plan or hypothesis for fix/optimization.
+
+  - type: textarea
+    id: measurement
+    attributes:
+      label: Measurement Plan
+      description: "How to measure before/after: specific metrics, dashboards."
+
+  - type: textarea
+    id: risks
+    attributes:
+      label: Risks & Rollback
+      description: Potential risks and fallback plan.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: Baseline metrics captured
+        - label: Benchmark scripts included or linked

.gitea/ISSUE_TEMPLATE/project_requirement.yml

@@ -0,0 +1,68 @@
+name: Project Requirement
+about: Document a project requirement with stakeholders and acceptance criteria
+title: "[Requirement] "
+labels:
+  - requirement
+body:
+  - type: textarea
+    id: overview
+    attributes:
+      label: Overview
+      description: High-level description of the requirement.
+    validations:
+      required: true
+
+  - type: textarea
+    id: stakeholders
+    attributes:
+      label: Stakeholders
+      description: "List stakeholders: product owner, engineers, designers."
+      placeholder: |
+        - Product owner: @username
+        - Engineers: @user1, @user2
+        - Designers: @user3
+
+  - type: textarea
+    id: goals
+    attributes:
+      label: Business Goals
+      description: What this requirement enables for the business or users.
+    validations:
+      required: true
+
+  - type: textarea
+    id: functional
+    attributes:
+      label: Functional Requirements
+      description: List the functional requirements.
+      placeholder: |
+        - Req 1: Description
+        - Req 2: Description
+    validations:
+      required: true
+
+  - type: textarea
+    id: nonfunctional
+    attributes:
+      label: Non-Functional Requirements
+      description: Performance targets, security/compliance constraints, accessibility.
+
+  - type: textarea
+    id: success
+    attributes:
+      label: Success Criteria
+      description: How to measure success.
+
+  - type: textarea
+    id: references
+    attributes:
+      label: Notes & References
+      description: Links to documents, mockups, legal requirements, etc.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: Stakeholders reviewed
+        - label: Acceptance criteria documented

.gitea/ISSUE_TEMPLATE/proposal.md

@@ -0,0 +1,41 @@
+<!-- Title: Proposal / Design RFC -->
+# Proposal: [Short title]
+
+## Summary
+Concise description of the proposal and what outcome you want.
+
+## Problem statement
+What problem are we solving and why is it important? Include links to related issues.
+
+## Goals
+- Primary goals (what success looks like)
+- Non-goals (explicitly out of scope)
+
+## Proposed design
+Describe the design in detail. Include:
+- Architecture diagrams or ASCII art
+- API changes (requests/responses)
+- Data model changes or migrations
+- UX flows or wireframes
+
+## Alternatives considered
+Short list of alternatives and tradeoffs.
+
+## Backwards compatibility & migration plan
+Describe how to migrate existing data and any compatibility impacts.
+
+## Security considerations
+List potential security/privacy implications.
+
+## Testing & rollout plan
+How will this be tested? Phased rollout plan if needed.
+
+## Implementation plan & timeline
+High-level tasks and owners.
+
+## Open questions
+List any unresolved questions.
+
+**Checklist**
+- [ ] Linked related issues
+- [ ] Prototype or PoC (if available)

.gitea/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,30 @@
+name: Question / Support
+about: Ask a question or get help
+title: "[Question] "
+labels:
+  - question
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Need help? Ask away! For security issues, please see SECURITY.md instead.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: Your Question
+      description: What do you need help with?
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: What have you tried? What documentation have you read?
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment (if relevant)
+      description: OS, version, setup details.

.gitea/ISSUE_TEMPLATE/repo_management.yml

@@ -0,0 +1,45 @@
+name: Repository Management
+about: Request repo maintenance (archiving, renaming, structure changes)
+title: "[Repo] "
+labels:
+  - repo-management
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What repo maintenance or management change is needed?
+    validations:
+      required: true
+
+  - type: textarea
+    id: current
+    attributes:
+      label: Current State
+      description: Describe current repo structure, branches, tags, etc.
+
+  - type: textarea
+    id: change
+    attributes:
+      label: Requested Change
+      description: What you want changed and why.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps
+      description: Step-by-step plan to complete the change (who will run each step).
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Dependencies & Impact
+      description: Other repos, CI pipelines, or services that will be affected.
+
+  - type: textarea
+    id: rollback
+    attributes:
+      label: Rollback Plan
+      description: How to undo if something goes wrong.

.gitea/ISSUE_TEMPLATE/task_todo.yml

@@ -0,0 +1,51 @@
+name: Task / To-Do
+about: Track a task with subtasks, owner, and effort estimate
+title: "[Task] "
+labels:
+  - task
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Detailed description of the task and expected outcome.
+    validations:
+      required: true
+
+  - type: input
+    id: assignee
+    attributes:
+      label: Owner
+      description: Who is responsible for this task?
+      placeholder: "@username"
+
+  - type: textarea
+    id: subtasks
+    attributes:
+      label: Subtasks
+      description: Break down the work into subtasks.
+      placeholder: |
+        - [ ] Subtask 1 — description
+        - [ ] Subtask 2 — description
+        - [ ] Subtask 3 — description
+    validations:
+      required: true
+
+  - type: input
+    id: effort
+    attributes:
+      label: Estimated Effort
+      description: "Time estimate, e.g. 2d, 4h."
+      placeholder: "e.g. 4h, 2d"
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: List any blocking issues or PRs.
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance Criteria
+      description: What needs to be true for this task to be considered done.

.gitea/ISSUE_TEMPLATE/ux.yml

@@ -0,0 +1,61 @@
+name: User Experience (UX)
+about: Report a UX problem or suggest a UX improvement
+title: "[UX] "
+labels:
+  - ux
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: One-line summary of the UX issue or suggestion.
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Describe the Problem
+      description: Where in the product does this occur? Who is affected?
+    validations:
+      required: true
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: User Impact
+      description: Explain the user pain, frequency, and severity.
+
+  - type: textarea
+    id: current
+    attributes:
+      label: Current Behavior
+      description: What a user sees now (include screenshots or steps).
+
+  - type: textarea
+    id: proposed
+    attributes:
+      label: Proposed Change
+      description: Detailed description of the UX change or recommendation.
+    validations:
+      required: true
+
+  - type: textarea
+    id: mockups
+    attributes:
+      label: Mockups / Prototypes
+      description: Attach or link to designs.
+
+  - type: textarea
+    id: accessibility
+    attributes:
+      label: Accessibility Considerations
+      description: Color contrast, keyboard navigation, screen reader notes.
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Acceptance Criteria
+      options:
+        - label: Usability tested with users
+        - label: Accessibility checks passed