feat: update release infrastructure and documentation

- Update GitHub issue templates with standardized YAML format
- Add automated release workflows and smoke testing
- Enhance documentation with installation guides for Docker and Linux
- Add comprehensive quickstart guide and release checklist
- Update license and third-party attributions
- Add MkDocs configuration for documentation site
- Implement packaging infrastructure for multi-platform releases
- Clean up staging artifacts and checksums
- Update security documentation and troubleshooting guides
- Add automated documentation deployment workflow

Author: thegdsks

.github/ISSUE_TEMPLATE/bug.yml

@@ -63,57 +63,113 @@ body:
       required: true
 
   - type: input
-    id: version
+    id: controller_version
     attributes:
-      label: GlinrDock Version
-      description: What version of GlinrDock are you running?
+      label: Controller Version
+      description: What version of GlinrDock Controller are you running?
       placeholder: v1.0.0
     validations:
       required: true
 
+  - type: textarea
+    id: version_output
+    attributes:
+      label: Version Command Output
+      description: |
+        Please run `glinrdockd --version` and paste the complete output below.
+        If using Docker Compose, run: `docker compose exec glinrdock glinrdockd --version`
+      placeholder: |
+        glinrdockd version v1.0.0
+        Build: abc123def
+        Built: 2025-01-01T12:00:00Z
+        Go: go1.21.0
+      render: shell
+    validations:
+      required: true
+
   - type: dropdown
     id: installation
     attributes:
       label: Installation Method
       description: How did you install GlinrDock?
       options:
-        - Install script (recommended)
+        - systemd service (install script)
         - Docker Compose
-        - Manual installation
+        - Manual binary installation
+        - Container (docker run)
         - Other (specify in additional context)
     validations:
       required: true
 
   - type: input
     id: os
     attributes:
-      label: Operating System
-      description: What operating system are you using?
-      placeholder: Ubuntu 22.04, CentOS 8, etc.
+      label: Operating System and Version
+      description: What operating system and version are you using?
+      placeholder: "Ubuntu 22.04.3 LTS, CentOS Stream 8, macOS 13.6, etc."
     validations:
       required: true
 
   - type: input
     id: docker
     attributes:
       label: Docker Version
-      description: What version of Docker are you using?
-      placeholder: Docker version 20.10.21
+      description: What version of Docker are you using? (Run `docker --version`)
+      placeholder: "Docker version 24.0.7, build afdd53b"
     validations:
       required: true
 
   - type: textarea
     id: logs
     attributes:
-      label: Log Output
+      label: Log Output (Required)
       description: |
-        Please provide relevant log output. For systemd installations use:
-        `sudo journalctl -u glinrdock.service --no-pager -l`
+        Please provide relevant log output from the time the issue occurred:
+        
+        **For systemd installations:**
+        ```bash
+        sudo journalctl -u glinrdockd.service --no-pager -l --since="10 minutes ago"
+        ```
+        
+        **For Docker Compose:**
+        ```bash
+        docker compose logs --tail=50 glinrdock
+        ```
         
-        For Docker Compose use:
-        `docker-compose logs glinrdock`
-      placeholder: Paste log output here...
+        **For docker run:**
+        ```bash
+        docker logs --tail=50 glinrdock
+        ```
+      placeholder: Paste log output here (last 50 lines or relevant error messages)...
       render: shell
+    validations:
+      required: true
+
+  - type: textarea
+    id: health_check
+    attributes:
+      label: Health Endpoint Output
+      description: |
+        Please check the health endpoint status by running:
+        ```bash
+        curl -s http://localhost:8080/v1/health | jq .
+        ```
+        Or without jq:
+        ```bash
+        curl -s http://localhost:8080/v1/health
+        ```
+        If the endpoint is not responding, note that in the output.
+      placeholder: |
+        {
+          "status": "healthy",
+          "timestamp": "2025-01-01T12:00:00Z",
+          "version": "v1.0.0"
+        }
+        
+        OR: "Connection refused" / "Timeout" / other error message
+      render: json
+    validations:
+      required: true
 
   - type: textarea
     id: config

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,11 +1,14 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Security Vulnerability
-    url: https://github.com/GLINCKER/glinrdock-release/blob/main/SECURITY.md
-    about: Report security vulnerabilities privately
-  - name: General Discussion
+  - name: 🔒 Security Vulnerability Report
+    url: https://github.com/GLINCKER/glinrdock-release/blob/main/docs/SECURITY.md
+    about: Report security vulnerabilities privately through our coordinated disclosure process
+  - name: 📖 Documentation & Installation Help
+    url: https://glincker.github.io/glinrdock-release/
+    about: Visit our documentation site for installation guides and troubleshooting
+  - name: 💬 General Discussion
     url: https://github.com/GLINCKER/glinrdock-release/discussions
     about: Ask questions and discuss features with the community
-  - name: Documentation
-    url: https://github.com/GLINCKER/glinrdock-release/blob/main/README.md
-    about: Read the documentation and guides
+  - name: 📞 Commercial Support
+    url: mailto:support@glincker.com
+    about: Contact GLINCKER LLC for enterprise support and licensing

.github/ISSUE_TEMPLATE/config.yml

@@ -32,27 +32,58 @@ body:
     validations:
       required: true
 
+  - type: textarea
+    id: business_outcome
+    attributes:
+      label: Business Outcome & Impact
+      description: |
+        What business problem does this solve? What value would it provide?
+        Focus on the "why" and business impact, not the "how".
+      placeholder: |
+        Example business outcomes:
+        - "Reduce deployment time from 30 minutes to 5 minutes"
+        - "Enable team to manage 50+ containers without manual oversight"
+        - "Eliminate security compliance violations during container deployment"
+        - "Save 10 hours per week on container monitoring tasks"
+      
+        Describe the impact:
+        - Who benefits from this feature?
+        - How does it improve their workflow?
+        - What are the measurable benefits?
+    validations:
+      required: true
+
   - type: textarea
     id: problem
     attributes:
-      label: Problem Statement
-      description: What problem does this feature solve? What's the motivation?
+      label: Current Problem/Gap
+      description: |
+        What specific problem or limitation currently prevents achieving the business outcome?
+        Be specific about what doesn't work today.
       placeholder: |
-        Is your feature request related to a problem? Please describe.
-        Example: "I'm always frustrated when..."
+        Current state description:
+        - "Currently we have to manually..." 
+        - "There's no way to..."
+        - "Users get frustrated because..."
+        - "We lose time/money because..."
     validations:
       required: true
 
   - type: textarea
-    id: solution
+    id: minimal_solution
     attributes:
-      label: Proposed Solution
-      description: Describe the solution you'd like to see implemented
+      label: Minimal Viable Change
+      description: |
+        What is the smallest possible change that would deliver meaningful value?
+        Think MVP - what's the 80/20 solution that provides the most impact with least complexity?
       placeholder: |
-        Describe your proposed solution:
-        - How should it work?
-        - What should the user experience be?
-        - Any specific implementation details?
+        Minimal solution that would help:
+        - "Just need a simple button to..."
+        - "A basic API endpoint that returns..."
+        - "A config option to enable/disable..."
+        - "Show status in the UI so users can..."
+        
+        This doesn't need to be the full solution, just the minimum that provides value.
     validations:
       required: true
 
@@ -89,29 +120,40 @@ body:
       required: true
 
   - type: dropdown
-    id: priority
+    id: business_priority
     attributes:
-      label: Priority
-      description: How important is this feature to you?
+      label: Business Priority
+      description: What's the business impact if this feature is not implemented?
       options:
-        - Nice to have (would be useful)
-        - Important (would significantly improve workflow)
-        - Critical (blocking current work)
+        - Low (nice to have, minor convenience improvement)
+        - Medium (noticeable productivity/efficiency gain)
+        - High (significant workflow blocker or competitive advantage)
+        - Critical (major business process blocked or security/compliance issue)
     validations:
       required: true
 
+  - type: input
+    id: timeline
+    attributes:
+      label: Business Timeline
+      description: Is there a business deadline or timeline driving this request?
+      placeholder: "Q2 2025 product launch, upcoming audit, team scaling to 50+ developers, etc."
+    validations:
+      required: false
+
   - type: dropdown
-    id: complexity
+    id: user_impact
     attributes:
-      label: Estimated Complexity
-      description: How complex do you think this feature would be to implement?
+      label: User Impact Scope
+      description: How many users or teams would benefit from this feature?
       options:
-        - Simple (minor change, quick to implement)
-        - Medium (moderate effort, some design needed)
-        - Complex (significant effort, major changes)
-        - Unknown (not sure about implementation complexity)
+        - Individual (just me or my specific use case)
+        - Team (5-15 people on my team)
+        - Department (multiple teams, 15-50 people)  
+        - Organization (company-wide, 50+ people)
+        - Community (many external users would benefit)
     validations:
-      required: false
+      required: true
 
   - type: textarea
     id: use_cases