feat: semantic search with Qdrant + Ollama embeddings

- Add SemanticSearchService with embed() + searchQdrant() methods
- Add GET /api/search/semantic endpoint (?q=query&k=5)
- Wire SemanticSearchService into router and cmd/server/main.go
- Add SemanticSearch React page with results + similarity scores
- Add 'Semantic Search' nav link in App.tsx
- Add unit tests with mocked Ollama + Qdrant HTTP servers (4 tests, all passing)
- Add GitHub issue templates (bug report, feature request)
- Add pull request template

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,57 @@
+name: Bug Report
+description: Report something that is broken or not working as expected
+labels: ["bug"]
+title: "[Bug] "
+body:
+
+- type: markdown
+  attributes:
+    value: |
+      ## Bug Description
+      Describe what broke and what you expected to happen.
+
+- type: textarea
+  id: repro
+  attributes:
+    label: Steps to Reproduce
+    placeholder: |
+      1.
+      2.
+      3.
+  validations:
+    required: true
+
+- type: textarea
+  id: expected
+  attributes:
+    label: Expected Behavior
+    placeholder: What should happen instead.
+
+- type: textarea
+  id: actual
+  attributes:
+    label: Actual Behavior
+    placeholder: What actually happens.
+
+- type: input
+  id: version
+  attributes:
+    label: UMM Version / Commit
+    placeholder: e.g., v2.0 or git commit hash
+
+- type: textarea
+  id: logs
+  attributes:
+    label: Relevant Logs
+    description: Paste any error messages or relevant log lines
+
+- type: textarea
+  id: env
+  attributes:
+    label: Environment
+    description: OS, Docker version, database version, etc.
+    placeholder: |
+      - OS:
+      - Docker:
+      - PostgreSQL:
+      - Go (if running locally):

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,29 @@
+name: Feature Request
+description: Suggest a new feature or improvement
+labels: ["enhancement"]
+title: "[Feature] "
+body:
+
+- type: markdown
+  attributes:
+    value: |
+      ## Feature Description
+      Describe the feature you'd like and why it would be useful.
+
+- type: textarea
+  id: usecase
+  attributes:
+    label: Use Case
+    placeholder: Who would use this and what problem does it solve?
+
+- type: textarea
+  id: alternatives
+  attributes:
+    label: Alternatives Considered
+    placeholder: What other approaches did you consider?
+
+- type: textarea
+  id: context
+  attributes:
+    label: Additional Context
+    placeholder: Screenshots, mockups, or any other relevant information.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## Description
+
+Brief summary of what this PR does.
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Testing
+
+Describe what testing you performed.
+
+- [ ] Tested locally (go test ./...)
+- [ ] Tested in Docker Compose dev environment
+- [ ] Verified frontend builds (npm run build)
+
+## Checklist
+
+- [ ] My code follows the project conventions (see AGENTS.md)
+- [ ] I have self-reviewed my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new compiler or lint warnings
+- [ ] I have added tests that prove my fix is effective or my feature works
+- [ ] New and existing unit tests pass locally with my changes