[CHORE]: Updated Issue Template

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,74 @@
+name: '🐛 Bug Report'
+description: 'File a structured bug report to help optimize the wrapper loop'
+title: '[BUG]: <Short description of the bug>'
+labels: ['bug']
+body:
+    - type: markdown
+      attributes:
+          value: |
+              ### Thanks for helping optimize labeled!
+              Please fill out this form accurately. Our automated pipeline uses these fields to spin up validation containers.
+
+    - type: input
+      id: os_version
+      attributes:
+          label: 'Linux Distribution & Version'
+          description: 'Provide your specific OS details.'
+          placeholder: 'e.g., Fedora 40, Ubuntu 24.04 LTS, Arch Linux'
+      validations:
+          required: true
+
+    - type: dropdown
+      id: manager_backend
+      attributes:
+          label: 'Active Package Manager'
+          description: 'Which system backend triggered the fault?'
+          options:
+              - 'apt'
+              - 'dnf'
+              - 'pacman'
+              - 'other / multiple'
+      validations:
+          required: true
+
+    - type: input
+      id: cli_version
+      attributes:
+          label: 'Labeled Tool Version'
+          description: "Run 'labeled --version' in your terminal."
+          placeholder: 'e.g., 1.0.0'
+      validations:
+          required: true
+
+    - type: textarea
+      id: reproduction
+      attributes:
+          label: 'Reproduction Commands'
+          description: 'What exact sequence of commands triggers the error?'
+          placeholder: |
+              1. labeled install dev-env curl
+              2. [Disconnect network]
+              3. labeled remove dev-env
+      validations:
+          required: true
+
+    - type: textarea
+      id: logs
+      attributes:
+          label: 'Terminal Error Output'
+          description: 'Paste raw error messages or state stack traces here.'
+          render: bash
+
+    - type: checkboxes
+      id: guardrails
+      attributes:
+          label: 'Repository Guardrails'
+          options:
+              - label: 'I verify this is not an open security exploit report.'
+                required: true
+              - label: 'I have searched the issue tracker and verified this issue does not already exist. (Exception: Automated system logs generated directly by Labeled-CLI running).'
+                required: true
+              - label: 'My issue title strictly follows the format: `[BUG]: <short-description>`.'
+                required: true
+              - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.'
+                required: true

.github/ISSUE_TEMPLATE/chore.yml

@@ -0,0 +1,69 @@
+name: '🧹 Maintenance & Chore'
+description: 'File a repository maintenance task, dependency bump, or CI/CD workflow update'
+title: '[CHORE]: <Short description of the task>'
+labels: ['chore']
+body:
+    - type: markdown
+      attributes:
+          value: |
+              ### Repository Maintenance Entry
+              Use this form to map out structural refactors, build script adjustments, or automation pipeline updates.
+
+    - type: dropdown
+      id: chore_category
+      attributes:
+          label: 'Chore Category'
+          description: 'Select the primary scope of this maintenance task.'
+          options:
+              - 'CI/CD Pipeline (.github/workflows)'
+              - 'Dependencies (package.json / lockfiles)'
+              - 'Build & Compilation System (build.js / tsconfig)'
+              - 'Repository Automation & Governance Templates'
+              - 'Other Maintenance'
+      validations:
+          required: true
+
+    - type: input
+      id: target_files
+      attributes:
+          label: 'Target Files / Paths'
+          description: 'Which configuration or system files will this change affect?'
+          placeholder: 'e.g., package.json, eslint.config.js, .github/workflows/pr-pipeline.yml'
+      validations:
+          required: true
+
+    - type: textarea
+      id: description
+      attributes:
+          label: 'Task Description'
+          description: 'Clearly state what needs to be updated and why this maintenance is necessary.'
+          placeholder: 'e.g., Upgrade Node.js environment to LTS version 22 across all action runner contexts to capture performance optimizations...'
+      validations:
+          required: true
+
+    - type: textarea
+      id: outcome
+      attributes:
+          label: 'Technical Expected Outcomes'
+          description: 'What are the criteria for this chore to be considered complete?'
+          placeholder: |
+              - Pipeline executes successfully without environment errors.
+              - Dependency locks are deterministically updated.
+      validations:
+          required: true
+
+    - type: checkboxes
+      id: verification
+      attributes:
+          label: 'Maintenance Guardrails'
+          options:
+              - label: 'I verify this is not an open security exploit report.'
+                required: true
+              - label: 'I have verified no other open issue is currently tracking this exact update.'
+                required: true
+              - label: 'My issue title strictly follows the format: `[CHORE]: <Short description of the task>`.'
+                required: true
+              - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.'
+                required: true
+              - label: 'I confirm this work is strictly structural maintenance (no features, no core bug fixes).'
+                required: true

.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,71 @@
+name: '📝 Documentation Update'
+description: 'File a request to improve, correct, or expand the documentation or wiki'
+title: '[DOCS]: <Short description of the documentation task>'
+labels: ['documentation']
+body:
+    - type: markdown
+      attributes:
+          value: |
+              ### Documentation Improvement Request
+              Use this form to flag outdated instructions, broken reference tables, typos, or clear gaps in our architecture guides.
+
+    - type: dropdown
+      id: docs_scope
+      attributes:
+          label: 'Documentation Scope'
+          description: 'Which area of the project documentation needs adjustment?'
+          options:
+              - 'README / Main Landing Page'
+              - 'CONTRIBUTING Guide'
+              - 'SECURITY / License Layout Files'
+              - 'Wiki Architecture Pages'
+              - 'JSDoc / Codebase Inline Annotations'
+              - 'Other Documentation'
+      validations:
+          required: true
+
+    - type: dropdown
+      id: priority_impact
+      attributes:
+          label: 'Impact Assessment'
+          description: 'How severely does this documentation issue affect users or developers?'
+          options:
+              - 'Critical (Broken setup commands, missing core requirements, broken links)'
+              - 'Standard Update (Expanding guides, updating configuration flags)'
+              - 'Typo / Style Fix (Fixing typos, grammar, or markdown spacing)'
+      validations:
+          required: true
+
+    - type: textarea
+      id: problem_description
+      attributes:
+          label: 'Current Deficiency Description'
+          description: 'What is currently missing, misleading, or incorrect in the active documentation?'
+          placeholder: 'e.g., The setup step mentions using Node 18, but the modern ESLint 10 setup depends on flat configuration bindings requiring Node 20+...'
+      validations:
+          required: true
+
+    - type: textarea
+      id: proposed_changes
+      attributes:
+          label: 'Proposed Text / Corrections'
+          description: 'Provide the updated phrasing or a clear layout outline of what should be written instead.'
+          placeholder: "Update Section 2 to state: 'Ensure your host local node execution runtime matches...' "
+      validations:
+          required: true
+
+    - type: checkboxes
+      id: documentation_guardrails
+      attributes:
+          label: 'Documentation Guardrails'
+          options:
+              - label: 'I confirm that I have verified the accuracy of the proposed text changes.'
+                required: true
+              - label: 'I verify this is not an open security exploit report.'
+                required: true
+              - label: 'I have searched the issue tracker and verified this issue does not already exist. (Exception: Automated system logs generated directly by Labeled-CLI running).'
+                required: true
+              - label: 'My issue title strictly follows the format: `[DOCS]: <Short description of the documentation task>`.'
+                required: true
+              - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.'
+                required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,68 @@
+name: '🚀 Feature Request'
+description: 'Propose a new utility capability, terminal flag, or engine behavior for labeled'
+title: '[FEATURE]: <Short description of the feature>'
+labels: ['enhancement']
+body:
+    - type: markdown
+      attributes:
+          value: |
+              ### Propose a New Extension
+              Thank you for suggesting an improvement! Please outline your idea clearly so we can evaluate its architectural alignment and hardware performance impact.
+
+    - type: dropdown
+      id: feature_scope
+      attributes:
+          label: 'Feature Target Scope'
+          description: 'Which architectural layer does this feature target?'
+          options:
+              - 'Core Engine Logic (src/engine.ts)'
+              - 'CLI Argument / Flag Interface (src/index.ts)'
+              - 'Package Manager Integration (src/managers/*)'
+              - 'State & Storage Optimization (src/utils/saveData.ts)'
+              - 'Other System Extension'
+      validations:
+          required: true
+
+    - type: textarea
+      id: user_problem
+      attributes:
+          label: 'Problem Statement / Use Case'
+          description: 'What limitation or friction in your current workflow does this feature solve? Describe clearly.'
+          placeholder: "e.g., Currently, when installing a tool chain that takes a long time, there's no way to pass an interactive timeout flag, causing background manager updates to hang silently on slower connections..."
+      validations:
+          required: true
+
+    - type: textarea
+      id: proposed_implementation
+      attributes:
+          label: 'Proposed Solution & Terminal Behavior'
+          description: 'How should this feature work? Provide examples of the exact CLI commands, syntax variations, or expected tracking data structures.'
+          placeholder: |
+              Introduce a `--timeout <seconds>` flag that maps to execution spawn loops.
+              Example syntax: 
+              labeled install dev-env curl --timeout 30
+      validations:
+          required: true
+
+    - type: textarea
+      id: technical_notes
+      attributes:
+          label: 'Architectural Implementation Ideas'
+          description: 'Optional notes on how this could be coded or which internal strategies are impacted.'
+          placeholder: 'This will require modifying the execution options structure in src/managers/index.ts to safely append custom abort signals...'
+
+    - type: checkboxes
+      id: feature_guardrails
+      attributes:
+          label: 'Feature Proposal Alignment'
+          options:
+              - label: 'I confirm this proposal is a feature addition, not a bug report or structural maintenance task.'
+                required: true
+              - label: 'I verify this is not an open security exploit report.'
+                required: true
+              - label: 'I have verified that no other active issue or open discussion thread is tracking this exact proposal.'
+                required: true
+              - label: 'My issue title strictly follows the format: `[FEATURE]: <Short description of the feature>`.'
+                required: true
+              - label: 'I understand that I must not start working on this until a maintainer assigns it to me via a comment request.'
+                required: true