feat: monorepo optimization and enhancement

.github/CODEOWNERS

@@ -0,0 +1,21 @@
+# Default owners for everything
+* @RepliMap/core-team
+
+# Web frontend
+/apps/web/ @RepliMap/frontend-team @RepliMap/core-team
+
+# API backend
+/apps/api/ @RepliMap/backend-team @RepliMap/core-team
+
+# CLI
+/apps/cli/ @RepliMap/cli-team @RepliMap/core-team
+
+# Shared configuration - requires core team review
+/packages/config/ @RepliMap/core-team
+
+# CI/CD and security-sensitive files
+/.github/ @RepliMap/devops-team @RepliMap/core-team
+/SECURITY.md @RepliMap/security-team
+
+# Documentation
+*.md @RepliMap/docs-team @RepliMap/core-team

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+github: [RepliMap]
+custom:
+  - "https://replimap.com/pricing"
+  - "https://replimap.com/enterprise"

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,107 @@
+name: Bug Report
+description: Report a bug or unexpected behavior
+title: "[Bug]: "
+labels: ["bug", "triage"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Thank you for reporting a bug!
+
+        Please fill out the form below to help us investigate.
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      description: Which part of RepliMap is affected?
+      options:
+        - CLI (`replimap` command)
+        - Web Dashboard
+        - API
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of the bug
+      placeholder: |
+        When I run `replimap scan`, the process hangs after scanning 50 resources...
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: How can we reproduce this issue?
+      placeholder: |
+        1. Configure AWS credentials with profile 'production'
+        2. Run `replimap scan --profile production`
+        3. Wait for ~2 minutes
+        4. Observe the hang
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: The scan should complete and show a summary of resources found.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / Error Output
+      description: Any relevant log output (use `replimap --debug` for verbose output)
+      render: shell
+      placeholder: |
+        $ replimap scan --debug
+        [DEBUG] Starting scan...
+        [ERROR] ConnectionTimeout: ...
+
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: Output of `replimap --version` or package version
+      placeholder: "0.5.0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating System
+      options:
+        - macOS (Apple Silicon)
+        - macOS (Intel)
+        - Linux (Ubuntu/Debian)
+        - Linux (RHEL/CentOS)
+        - Linux (Other)
+        - Windows (WSL2)
+        - Windows (Native)
+        - Other
+    validations:
+      required: true
+
+  - type: input
+    id: python_version
+    attributes:
+      label: Python Version (for CLI issues)
+      description: Output of `python --version`
+      placeholder: "3.11.5"
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Any other relevant information (screenshots, related issues, etc.)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions & Discussions
+    url: https://github.com/RepliMap/replimap-mono/discussions
+    about: Ask questions and discuss ideas
+  - name: Documentation
+    url: https://replimap.com/docs
+    about: Check our documentation for answers

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,79 @@
+name: Feature Request
+description: Suggest a new feature or improvement
+title: "[Feature]: "
+labels: ["enhancement", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Feature Request
+
+        We love hearing your ideas! Please describe your feature request.
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Component
+      description: Which part of RepliMap would this affect?
+      options:
+        - CLI (`replimap` command)
+        - Web Dashboard
+        - API
+        - New Component
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: What problem does this feature solve? What's your use case?
+      placeholder: |
+        As a DevOps engineer, I often need to compare two AWS environments...
+        Currently, I have to manually export and diff the resources...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: How would you like this to work?
+      placeholder: |
+        A new command like `replimap diff --source prod --target staging` that:
+        1. Scans both environments
+        2. Shows a side-by-side comparison
+        3. Highlights differences
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Any alternative solutions or workarounds you've tried?
+      placeholder: |
+        I tried using terraform plan to compare, but it requires the state files...
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: How important is this feature to you?
+      options:
+        - Nice to have
+        - Important for my workflow
+        - Critical / Blocking
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      description: Would you be willing to help implement this?
+      options:
+        - label: I'd be interested in implementing this feature
+        - label: I can help test this feature
+        - label: I can help write documentation

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,58 @@
+## Description
+
+<!-- Describe your changes. What does this PR do? Why is it needed? -->
+
+## Type of Change
+
+<!-- Mark the relevant option with an "x" -->
+
+- [ ] Bug fix - Non-breaking change fixing an issue
+- [ ] New feature - Non-breaking change adding functionality
+- [ ] Breaking change - Fix or feature causing existing functionality to change
+- [ ] Documentation - Documentation updates only
+- [ ] Chore - Refactoring, dependencies, CI/CD, etc.
+- [ ] Performance - Performance improvement
+
+## Component(s) Affected
+
+<!-- Mark all that apply -->
+
+- [ ] `apps/web` - Web Dashboard
+- [ ] `apps/api` - API Backend
+- [ ] `apps/cli` - Python CLI
+- [ ] `packages/config` - Shared Configuration
+- [ ] `.github/` - CI/CD & Workflows
+- [ ] Documentation
+
+## Testing
+
+<!-- How did you test these changes? -->
+
+- [ ] Unit tests added/updated
+- [ ] Integration tests added/updated
+- [ ] Manual testing performed
+- [ ] N/A (documentation only)
+
+## Checklist
+
+<!-- Ensure all items are checked before requesting review -->
+
+- [ ] My code follows the project's coding standards
+- [ ] I have performed a self-review of my changes
+- [ ] I have added tests that prove my fix/feature works
+- [ ] New and existing unit tests pass locally (`make test`)
+- [ ] I have run `make pre-commit` and all checks pass
+- [ ] I have updated documentation as needed
+- [ ] I have updated CHANGELOG.md (if user-facing change)
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your changes -->
+
+## Related Issues
+
+<!-- Link any related issues using keywords: Fixes #123, Closes #456, Related to #789 -->
+
+## Additional Notes
+
+<!-- Any additional context for reviewers -->