feat: add replicator service with NATS JetStream

.github/ISSUE_TEMPLATE/bug.yml

@@ -6,13 +6,12 @@ body:
   - type: textarea
     id: report
     attributes:
-      label: Report
-      description: What happened + expected + minimal repro (in one block). Link logs if big.
+      label: What happened
+      description: Describe the bug and what you expected to happen
       placeholder: |
-        What happened:
-        Expected:
-        Repro:
-        Logs/links:
+        **Observed:**
+        **Expected:**
+        **Steps to reproduce:**
     validations:
       required: true
 
@@ -24,10 +23,31 @@ body:
     validations:
       required: true
 
+  - type: dropdown
+    id: deployment
+    attributes:
+      label: Deployment
+      options:
+        - Local (native)
+        - Local (Docker)
+        - Testnet
+        - Mainnet
+        - Other
+    validations:
+      required: true
+
   - type: input
-    id: env
+    id: os
+    attributes:
+      label: OS / Arch
+      placeholder: "e.g., macOS arm64, Linux x86_64"
+    validations:
+      required: false
+
+  - type: textarea
+    id: logs
     attributes:
-      label: Environment
-      placeholder: "OS/arch + how you run it (docker/native) + anything relevant"
+      label: Logs / Links
+      description: Relevant logs, stack traces, or links
     validations:
       required: false

.github/ISSUE_TEMPLATE/feature.yml

@@ -4,13 +4,17 @@ title: "feat: "
 labels: ["enhancement"]
 body:
   - type: textarea
-    id: request
+    id: problem
     attributes:
-      label: Request
-      description: Problem + proposal + acceptance criteria (keep it short).
-      placeholder: |
-        Problem:
-        Proposal:
-        Acceptance criteria:
+      label: Problem
+      description: What pain point does this solve? Why is it needed?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed Solution
+      description: How should this work?
     validations:
       required: true

.github/ISSUE_TEMPLATE/good-first-issue.yml

@@ -0,0 +1,30 @@
+name: Good First Issue
+description: Small, well-scoped task for new contributors
+title: ""
+labels: ["good first issue"]
+body:
+  - type: textarea
+    id: task
+    attributes:
+      label: Task
+      description: What needs to be done
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: Background, relevant files, or pointers to get started
+    validations:
+      required: false
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance Criteria
+      description: How do we know this is done?
+      placeholder: |
+        - [ ]
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +1,20 @@
 <!--
-PR title must match:
-  type(scope): summary
+PR title must match: type(scope): summary
 Types: feat|fix|docs|chore|refactor|test|perf|ci|build
 Examples:
   fix: avoid panic on empty slot
   feat(rpc): add getFoo endpoint
 -->
 
 ## Summary
--
+<!-- One sentence. Link to issue if applicable. -->
 
-## Compatibility
-- [ ] No breaking changes
-- [ ] Config change (describe):
-- [ ] Migration needed (describe):
 
-## Testing
-- [ ] tests (or explain)
+## Breaking Changes
+- [ ] None
+- [ ] Yes — migration path described below
+
+
+## Test Plan
+<!-- How you verified this works. e.g., "unit tests", "ran locally against testnet", "existing tests pass" -->
 
-## Checklist
-- [ ] docs updated (if needed)
-- [ ] closes #