Create issue templates for more structured collaboration

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,25 @@
+name: Bug Report
+description: Report something that isn't working correctly.
+labels: ["bug"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What is the bug? Include steps to reproduce if applicable.
+    validations:
+      required: true
+  - type: textarea
+    id: root-cause
+    attributes:
+      label: Root cause
+      description: What is causing the bug? Include relevant code snippets.
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which files, modules, or components are affected?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/build.yaml

@@ -0,0 +1,25 @@
+name: Build
+description: Propose a build system or dependency change.
+labels: ["build"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What build system or dependency change is needed?
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this change needed?
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which build files, configs, or dependencies are affected?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/cicd.yaml

@@ -0,0 +1,25 @@
+name: CI/CD
+description: Propose a CI/CD pipeline change.
+labels: ["cicd"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What CI/CD change is needed?
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this change needed? What does it improve?
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which workflows, pipelines, or config files are affected?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,25 @@
+name: Feature Request
+description: Propose a new feature or capability.
+labels: ["feature"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What is the feature? Describe the desired behavior.
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this feature needed? What problem does it solve?
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which files, modules, or components would be affected?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/refactor.yaml

@@ -0,0 +1,25 @@
+name: Refactor
+description: Propose a code restructuring without behavior change.
+labels: ["refactor"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What should be restructured and what does the end state look like?
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this restructuring needed?
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which files, modules, or components are affected?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/test.yaml

@@ -0,0 +1,25 @@
+name: Test
+description: Add or improve test coverage or test infrastructure.
+labels: ["test"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What needs to be tested or what test infrastructure is needed?
+    validations:
+      required: true
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this test work needed? What gap does it fill?
+    validations:
+      required: true
+  - type: textarea
+    id: affected-code
+    attributes:
+      label: Affected code
+      description: Which files, modules, or components are affected?
+    validations:
+      required: false

.readthedocs.yaml

@@ -6,30 +6,20 @@ version: 2
 
 # Set the OS, Python version and other tools
 build:
-  os: "ubuntu-22.04"
+  os: "ubuntu-24.04"
   tools:
     python: "3.11"
+  jobs:
+    post_install:
+      - python -m pip install --group docs
 
 # Build documentation in the docs/ directory with Sphinx
 sphinx:
   configuration: docs/conf.py
 
-formats:
-  - epub
-
-# Specify the Python requirements file
+# Install the project
 python:
   install:
-    - requirements: docs/requirements.txt
     - method: pip
       path: .
 
-# Version management:
-# Documentation is immutable per release. Each git tag (v0.1.0, v0.2.0, etc.) produces
-# a frozen snapshot of the docs as they were at that release.
-#
-# - Tags (v0.1.0, v0.2.0, ...): Immutable doc snapshots
-# - main/master branches: Development version docs (always latest)
-#
-# This ensures historical accuracy: users viewing old version docs see them exactly
-# as they were released, not retrospectively updated.