feat: add comprehensive GitHub issue templates (#42)

Add structured issue templates following OpenUP methodology for improved
issue creation and project management.

Templates added:
- 🚀 Feature Request: Functional requirements with OpenUP phases
- 🐛 Bug Report: Comprehensive debugging with environment info
- ⚡ Quality Enhancement: Non-functional requirements (performance, testing)
- 🔧 Infrastructure & Process: CI/CD, release management, DevOps
- 📦 Distribution & Packaging: Package manager integration templates
- 🧹 Technical Debt & Cleanup: Code cleanup and refactoring
- 📝 General Issue: Discussions, documentation, planning
- config.yml: Template organization and contact links

Features:
- OpenUP phase integration (Elaboration, Construction, Transition)
- Story point estimation (1-2, 3-5, 6-7, 8-10)
- Priority levels (High, Medium, Low)
- Dependency tracking (Depends on, Blocks, Relates to)
- Platform-specific fields for distribution templates
- Security considerations and testing strategies
- Structured acceptance criteria and success metrics

Benefits:
- Consistent issue format across project
- Better requirement gathering and planning
- Improved OpenUP workflow integration
- Enhanced project tracking and organization

Author: behrangsa

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,124 @@
+name: 🐛 Bug Report
+description: Report a bug or defect in Samoid
+title: "[Bug]: "
+labels: ["🐛 bug", "🔥 priority: high"]
+projects: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug! Please provide detailed information to help us reproduce and fix the issue.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Bug Summary
+      description: Provide a clear and concise description of the bug
+      placeholder: Brief description of what went wrong...
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps to Reproduce
+      description: Provide detailed steps to reproduce the behavior
+      placeholder: |
+        1. Run command '...'
+        2. In directory with '...'
+        3. Expected '...' but got '...'
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: What did you expect to happen?
+      placeholder: Describe what should have happened...
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual Behavior
+      description: What actually happened?
+      placeholder: Describe what actually happened...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      description: How severe is this bug?
+      options:
+        - 🔴 Critical - Application crashes or data loss
+        - 🟠 High - Major functionality broken
+        - 🟡 Medium - Minor functionality affected
+        - 🟢 Low - Cosmetic or minor issue
+      default: 1
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: platform
+    attributes:
+      label: Platform
+      description: Which platforms are affected?
+      options:
+        - label: Linux
+        - label: macOS
+        - label: Windows
+        - label: WSL (Windows Subsystem for Linux)
+        - label: Git Bash
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment Information
+      description: Please provide relevant environment details
+      placeholder: |
+        - OS: [e.g., Ubuntu 24.04, macOS 14.0, Windows 11]
+        - Samoid version: [e.g., 0.1.4]
+        - Git version: [e.g., 2.45.0]
+        - Shell: [e.g., bash, zsh, PowerShell]
+        - Other relevant tools: [e.g., node 18.0, cargo 1.75]
+    validations:
+      required: true
+
+  - type: textarea
+    id: error-output
+    attributes:
+      label: Error Output
+      description: Include any error messages, stack traces, or debug output
+      placeholder: |
+        Paste error output here...
+      render: text
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Debug Logs
+      description: If available, include output from running with debug mode (SAMOID=2)
+      placeholder: |
+        Output from SAMOID=2 samoid command...
+      render: text
+
+  - type: checkboxes
+    id: workaround
+    attributes:
+      label: Workaround
+      description: Do you have a workaround for this issue?
+      options:
+        - label: Yes, I have a workaround (please describe below)
+        - label: No workaround available
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context about the problem, including configuration files or repository structure
+      placeholder: Any additional information that might help...

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 💬 Discussions
+    url: https://github.com/nutthead/samoid/discussions
+    about: Ask questions, share ideas, or discuss the project with the community
+  - name: 📚 Documentation
+    url: https://github.com/nutthead/samoid/blob/master/README.md
+    about: Read the project documentation and user guides
+  - name: 🔍 Search Issues
+    url: https://github.com/nutthead/samoid/issues
+    about: Search existing issues before creating a new one

.github/ISSUE_TEMPLATE/distribution-packaging.yml

@@ -0,0 +1,227 @@
+name: 📦 Distribution & Packaging
+description: Package manager integration, distribution channels, and installation methods
+title: "[Distribution]: "
+labels: ["🚀 deployment", "🏁 phase: transition", "🎯 type: nonfunctional"]
+projects: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for improving Samoid's distribution! Package manager integration helps users install and update Samoid easily.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Provide a clear summary of the distribution enhancement
+      placeholder: Brief description of the distribution channel or packaging improvement...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: distribution-type
+    attributes:
+      label: Distribution Channel
+      description: What type of distribution channel is this?
+      options:
+        - 🍺 Homebrew - macOS/Linux package manager (brew install)
+        - 🪣 Scoop - Windows package manager (scoop install)
+        - 🍫 Chocolatey - Windows package manager (choco install)
+        - 📦 APT Repository - Debian/Ubuntu package repository
+        - 📦 YUM/DNF Repository - Red Hat/Fedora package repository
+        - 🐧 Snap Package - Universal Linux package (snap install)
+        - 📥 Installation Script - Automated download/install script (curl | sh)
+        - 🔐 Package Signing - Cryptographic signing of release artifacts
+        - 🌐 Other Distribution - Different distribution method
+      default: 0
+    validations:
+      required: true
+
+  - type: textarea
+    id: target-users
+    attributes:
+      label: Target Users
+      description: Who will benefit from this distribution method?
+      placeholder: |
+        Target audience:
+        - macOS developers using Homebrew
+        - Windows users preferring GUI installers
+        - Linux system administrators...
+    validations:
+      required: true
+
+  - type: textarea
+    id: current-state
+    attributes:
+      label: Current State
+      description: Describe current installation methods and their limitations
+      placeholder: |
+        Current installation options:
+        - Manual binary download from GitHub releases
+        - cargo install samoid (Rust developers only)
+        - Limitations: [specific pain points]
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-implementation
+    attributes:
+      label: Proposed Implementation
+      description: Describe the specific implementation approach
+      placeholder: |
+        Implementation plan:
+        - Create package manifest/formula
+        - Set up automated publishing workflow
+        - Test installation across target platforms
+        - Update documentation...
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance Criteria
+      description: List specific, testable requirements for completion
+      placeholder: |
+        - [ ] Package manifest/formula created and validated
+        - [ ] Automated publishing workflow implemented
+        - [ ] Installation tested on target platforms
+        - [ ] Documentation updated with installation instructions
+        - [ ] Package properly handles updates/uninstallation
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: platform-support
+    attributes:
+      label: Target Platforms
+      description: Which platforms will be supported?
+      options:
+        - label: macOS (Intel x64)
+        - label: macOS (Apple Silicon ARM64)
+        - label: Linux (x86_64)
+        - label: Linux (ARM64)
+        - label: Windows (x64)
+        - label: Windows (x86/32-bit)
+
+  - type: textarea
+    id: package-manifest
+    attributes:
+      label: Package Manifest/Formula Details
+      description: Provide details about the package configuration
+      placeholder: |
+        Package configuration:
+        - Package name: samoid
+        - Version management: [semver, git tags]
+        - Dependencies: [none, system requirements]
+        - Installation location: [/usr/local/bin, ~/.local/bin]
+        - Configuration files: [locations, permissions]
+
+  - type: textarea
+    id: automation-workflow
+    attributes:
+      label: Automation & Publishing
+      description: How will package updates be automated?
+      placeholder: |
+        Automation approach:
+        - Trigger: [on release, manual workflow]
+        - Update mechanism: [PR to tap, API submission]
+        - Validation: [testing, checksums, signatures]
+        - Rollback plan: [if issues discovered]
+
+  - type: textarea
+    id: testing-strategy
+    attributes:
+      label: Testing Strategy
+      description: How will you validate the distribution channel?
+      placeholder: |
+        Testing plan:
+        - Fresh installation on clean systems
+        - Update scenarios (old version → new version)
+        - Uninstallation cleanup verification
+        - Cross-platform compatibility testing
+        - Integration with existing tools/workflows
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How important is this distribution channel?
+      options:
+        - 🔥 High - Critical for user adoption
+        - ⚡ Medium - Important for convenience
+        - 🟢 Low - Nice to have additional option
+      default: 1
+    validations:
+      required: true
+
+  - type: dropdown
+    id: effort
+    attributes:
+      label: Estimated Effort (Story Points)
+      description: Rough estimate of implementation complexity
+      options:
+        - 🟢 1-2 - Simple manifest creation
+        - 🟡 3-5 - Medium complexity with automation
+        - 🟠 6-7 - Complex setup with testing infrastructure
+        - 🔴 8-10 - Major infrastructure requiring hosting/signing
+      default: 1
+    validations:
+      required: true
+
+  - type: textarea
+    id: security-considerations
+    attributes:
+      label: Security Considerations
+      description: What security measures are needed?
+      placeholder: |
+        Security requirements:
+        - Package signing/verification
+        - Checksum validation
+        - Secure distribution channels
+        - Update integrity verification
+        - Vulnerability disclosure process
+
+  - type: textarea
+    id: maintenance-requirements
+    attributes:
+      label: Long-term Maintenance
+      description: What ongoing maintenance will be required?
+      placeholder: |
+        Maintenance considerations:
+        - Regular testing of installation process
+        - Monitoring package manager ecosystem changes
+        - Updating manifests for new releases
+        - Handling deprecated distribution channels
+        - Community support and issue resolution
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies & Prerequisites
+      description: List any dependencies or setup requirements
+      placeholder: |
+        Prerequisites:
+        - **Depends on**: #issue_number (Description)
+        - **Requires**: External accounts/access (Homebrew tap, Windows signing cert)
+        - **Blocks**: #issue_number (Description)
+
+  - type: textarea
+    id: success-metrics
+    attributes:
+      label: Success Metrics
+      description: How will you measure the success of this distribution channel?
+      placeholder: |
+        Success criteria:
+        - Installation success rate: >95%
+        - User feedback: Positive reception
+        - Adoption metrics: Downloads/installs via this channel
+        - Reduced manual installation support requests
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context, examples, or references
+      placeholder: Any additional information...