docs: prepare mcp-stacks for public release

Add comprehensive documentation and community files:
- Add MIT License
- Enhance README with executive-level positioning and "Why This Matters" section
- Add comprehensive SECURITY.md with best practices and vulnerability reporting
- Create GitHub issue templates (bug report, feature request, question)
- Significantly expand CONTRIBUTING.md for external contributors

Changes include:
- Executive positioning highlighting GitOps, security-first architecture, and production resilience
- Clear note about example hostnames (jabba.lan) for user customization
- Security policy with responsible disclosure guidelines
- Contribution workflow, coding standards, and testing guidelines
- Community engagement and recognition policies

These changes prepare the repository for open-source collaboration while maintaining security best practices.

Part of public showcase preparation initiative.

Author: unplugged12

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug Report
+about: Report a bug or unexpected behavior
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Bug Description
+A clear and concise description of what the bug is.
+
+## To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Run command '....'
+3. See error
+
+## Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+What actually happened instead.
+
+## Environment
+**Deployment Type:** (Agent / Edge / Both)
+**Operating System:** (e.g., Ubuntu 24.04, Windows 11, macOS)
+**Docker Version:** (output of `docker --version`)
+**Portainer Version:** (e.g., CE 2.19.4)
+**Stack/Compose File:** (e.g., stacks/desktop/docker-compose.yml)
+
+## Logs
+```
+# Paste relevant logs here (docker logs, Portainer logs, etc.)
+# Remove any sensitive information
+```
+
+## Screenshots
+If applicable, add screenshots to help explain your problem.
+
+## Additional Context
+Add any other context about the problem here (network configuration, firewall rules, previous working state, etc.).
+
+## Attempted Solutions
+Have you tried any workarounds or fixes? Please describe them here.
+
+## Checklist
+- [ ] I have searched existing issues to ensure this hasn't been reported
+- [ ] I have included relevant logs (with sensitive info removed)
+- [ ] I have provided clear reproduction steps
+- [ ] I am using the latest version from the main branch

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,51 @@
+---
+name: Feature Request
+about: Suggest an enhancement or new feature
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Feature Description
+A clear and concise description of the feature you'd like to see.
+
+## Problem Statement
+Is your feature request related to a problem? Please describe.
+Example: "I'm always frustrated when..."
+
+## Proposed Solution
+Describe the solution you'd like. Be as detailed as possible.
+
+## Alternatives Considered
+Have you considered any alternative solutions or features? Please describe them.
+
+## Use Case
+Explain how this feature would be used in a real-world scenario.
+
+## Benefits
+What benefits would this feature provide?
+- **Performance:** Does it improve speed/efficiency?
+- **Security:** Does it enhance security posture?
+- **Usability:** Does it make things easier to use?
+- **Scalability:** Does it enable larger deployments?
+
+## Implementation Suggestions
+If you have ideas about how this could be implemented, share them here.
+(Code snippets, architecture diagrams, links to similar implementations, etc.)
+
+## Scope
+**Deployment Type:** (Agent / Edge / Both / Not Applicable)
+**Component:** (Scripts / Compose Files / Documentation / CI/CD / Other)
+**Complexity:** (Low / Medium / High - your best guess)
+
+## Additional Context
+Add any other context, screenshots, or examples about the feature request here.
+
+## Community Interest
+Would others in the community benefit from this feature? Please describe the potential audience.
+
+## Checklist
+- [ ] I have searched existing issues/PRs to ensure this hasn't been proposed
+- [ ] I have provided a clear use case
+- [ ] I have considered alternatives
+- [ ] I am willing to help implement this (optional)

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,39 @@
+---
+name: Question
+about: Ask a question about usage, configuration, or best practices
+title: '[QUESTION] '
+labels: question
+assignees: ''
+---
+
+## Question
+What would you like to know?
+
+## Context
+What are you trying to accomplish? Providing context helps us give better answers.
+
+## What I've Tried
+Have you searched the documentation or tried any solutions? Please describe what you've done so far.
+
+### Documentation Reviewed
+- [ ] README.md
+- [ ] [SECURITY.md](../../SECURITY.md)
+- [ ] [CONTRIBUTING.md](../../CONTRIBUTING.md)
+- [ ] [docs/PIPELINE.md](../../docs/PIPELINE.md)
+- [ ] [docs/ROADMAP.md](../../docs/ROADMAP.md)
+- [ ] Existing GitHub Issues
+
+## Environment (if applicable)
+**Deployment Type:** (Agent / Edge / Both / Planning Phase)
+**Operating System:** (e.g., Ubuntu 24.04, Windows 11, macOS)
+**Portainer Version:** (e.g., CE 2.19.4)
+
+## Additional Information
+Any other details that might be relevant to your question.
+
+## Related Issues
+Are there any related issues or discussions? Please link them here.
+
+---
+
+**Note:** For general discussions or open-ended topics, consider starting a [GitHub Discussion](../../discussions) instead of opening an issue.