chore: initialize EverOS 1.0.0

md-first memory extraction framework for AI agents.

Markdown is the single source of truth; SQLite holds state and LanceDB
provides the rebuildable vector + BM25 + scalar index. The codebase follows
a single-direction DDD layering (entrypoints -> service -> memory -> infra,
with component / core / config cross-cutting) enforced by import-linter.

Engineering surface:
- Coding conventions in .claude/rules/ (path-scoped) and workflows in
  .claude/skills/ (/commit, /new-branch, /pr).
- GitHub Actions CI runs make lint + test + integration; pre-commit mirrors
  the gates locally (ruff, hygiene hooks, gitlint commit-msg).
- Commit messages follow Conventional Commits, enforced by gitlint.
- make lint also enforces datetime two-zone discipline and OpenAPI drift.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,54 @@
+name: Bug report
+description: Report a reproducible problem in EverOS
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: Thanks for helping improve EverOS. Clear reproduction steps make bugs much faster to fix.
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - methods/EverCore
+        - methods/HyperMem
+        - benchmarks/EverMemBench
+        - benchmarks/EvoAgentBench
+        - use-cases
+        - documentation
+        - other
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: What happened?
+      description: Describe the bug and the behavior you expected.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. Go to ...
+        2. Run ...
+        3. See ...
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      placeholder: |
+        OS:
+        Python:
+        Node:
+        Docker:
+        Commit:
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs or screenshots
+      render: shell

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: EverOS Discussions
+    url: https://github.com/EverMind-AI/EverOS/discussions
+    about: Ask questions, share ideas, and discuss roadmap topics.

.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,22 @@
+name: Documentation issue
+description: Report unclear, missing, or outdated documentation
+title: "[Docs]: "
+labels: ["documentation"]
+body:
+  - type: input
+    id: page
+    attributes:
+      label: Page or file
+      placeholder: README.md, methods/EverCore/docs/...
+    validations:
+      required: true
+  - type: textarea
+    id: issue
+    attributes:
+      label: What should be improved?
+    validations:
+      required: true
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested wording or structure

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,40 @@
+name: Feature request
+description: Suggest an improvement or new capability
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - architecture methods
+        - benchmarks
+        - use cases
+        - developer experience
+        - documentation
+        - other
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or opportunity
+      description: What user need, research gap, or workflow pain does this address?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: Describe the change you would like to see.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context

.github/ISSUE_TEMPLATE/use_case.yml

@@ -0,0 +1,37 @@
+name: Use-case proposal
+description: Propose an app, demo, or integration for use-cases/
+title: "[Use Case]: "
+labels: ["use case"]
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What does the use case demonstrate?
+    validations:
+      required: true
+  - type: textarea
+    id: memory
+    attributes:
+      label: Memory behavior
+      description: What should the agent remember, retrieve, or evolve over time?
+    validations:
+      required: true
+  - type: textarea
+    id: stack
+    attributes:
+      label: Stack and dependencies
+      description: List frameworks, services, models, or external APIs.
+  - type: textarea
+    id: run
+    attributes:
+      label: Run path
+      description: How should a new developer run or inspect it?
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Contribution checklist
+      options:
+        - label: I can include a README with setup instructions.
+        - label: I can avoid committing secrets, generated output, dependency folders, and image files.
+        - label: I can include `.env.example` if configuration is needed.