docs: update .github/ISSUE_TEMPLATE/bug_report.md via Apex Optimizer

Author: chirag127

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,92 +1,63 @@
 ---
-name: 🐛 Bug Report
-about: Report unexpected behavior or defects in JSErrorFlow.
-title: "[BUG]: Brief Summary of the Issue"
-labels: bug, triage
-assignees: ""
----
-
-## 🚨 Summary & Intent Alignment
-
-Please provide a concise, one-sentence summary of the defect. Ensure the reported behavior deviates from the documented specification.
-
-> **Example:** "The extension fails to highlight errors originating from Web Workers on Chromium 119."
-
----
-
-## ⚙️ Environment & Context (Mandatory)
-
-This section ensures rapid triangulation of the failure domain. **Do not omit details.**
-
-### A. Platform Details
-- **Operating System:** [e.g., macOS Sonoma 14.2, Windows 11 Pro]
-- **Browser:** [e.g., Chrome 119.0.6045.199, Firefox 120.0.1]
-- **Extension Version:** `JSErrorFlow vX.Y.Z` (Check `manifest.json` or extension details)
-
-### B. Target Application Context
-- **URL / Domain:** (Use placeholders for sensitive sites)
-- **Website Framework:** [e.g., React 18, Vue 3, Vanilla JS]
+name: "🐞 Bug Report"
+about: "Report a reproducible bug or unexpected behavior to help us improve."
+title: "[BUG] <A brief, descriptive title>"
+labels: ["bug", "triage"]
+assignees:
+  - "chirag127"
 
 ---
 
-## 👣 Steps to Reproduce (The Critical Path)
+### Preliminary Checks
 
-Provide a numbered, deterministic sequence that reliably triggers the issue. If the error is intermittent, describe the specific load conditions or timing required.
-
-1. Open Browser to `[Target URL]`
-2. Ensure JSErrorFlow is actively injected.
-3. Execute the triggering action (e.g., "Click the Submit button").
-4. Observe the resulting error visualization or lack thereof.
+- [ ] I have searched the existing [issues](https://github.com/chirag127/JSErrorFlow-Real-Time-Visualizer-Browser-Extension/issues) to ensure this is not a duplicate bug report.
+- [ ] I have checked the [project documentation](https://github.com/chirag127/JSErrorFlow-Real-Time-Visualizer-Browser-Extension#readme) for any relevant information.
+- [ ] I am using the latest version of the extension.
 
 ---
 
-## 🎯 Expected Behavior (The Specification)
-
-What result aligns with the project's design goals (i.e., what *should* have happened)?
+### Bug Description
 
-*   [ ] The JavaScript error stack trace should appear in the extension popup within 500ms.
-*   [ ] The affected DOM node should receive a persistent, pulsating visual indicator as defined by the current UI theme.
+A clear and concise description of what the bug is. What happened, and what did you expect to happen?
 
----
+### Steps to Reproduce
 
-## 💥 Actual Behavior (The Defect)
+Provide the exact steps to reproduce the behavior:
 
-What actually occurred that constitutes the bug?
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error
 
-*   [ ] The error was logged in the browser console but **not** visualized by JSErrorFlow.
-*   [ ] The visualization caused an unexpected side effect (e.g., UI component displacement or layout shift).
+### Expected Behavior
 
----
+A clear and concise description of what you expected to happen.
 
-## 🖼️ Evidence & Logs
+### Screenshots or Screen Recordings
 
-High-quality evidence accelerates triage by 75%.
+If applicable, add screenshots, GIFs, or video recordings to help explain your problem. You can drag and drop files directly into this editor.
 
-### A. Visual Proof
-(Attach screenshots or screen recordings demonstrating the discrepancy.)
+### Environment
 
-### B. Console Output
-Paste the full, relevant output from the browser's Developer Tools Console. Filter by JSErrorFlow sources if possible.
+Please complete the following information:
 
-```javascript
-// Paste logs here, including stack traces
-```
+-   **Operating System:** [e.g., macOS Sonoma, Windows 11]
+-   **Browser & Version:** [e.g., Chrome 125.0.6422.112, Firefox 126.0]
+-   **Extension Version:** [e.g., v1.0.1]
 
----
+### Console Logs & Technical Details
 
-## ⚖️ Impact Assessment (Severity)
+Please open the developer console (F12 or Ctrl+Shift+I) and paste any relevant error messages or stack traces below.
 
-How severely does this defect impede core functionality?
+<details>
+<summary>Click to expand console logs</summary>
 
-- [ ] **P0 - Critical:** Core visualization functionality completely blocked. High developer downtime incurred.
-- [ ] **P1 - High:** Major error handling path broken; workaround requires disabling the extension.
-- [ ] **P2 - Medium:** Minor functionality impaired; aesthetic inconsistency or edge-case handling failure.
-- [ ] **P3 - Low:** Typo, documentation error, or non-critical performance degradation.
+text
+(Paste your logs here)
 
----
 
-## 🤖 AI Agent Directives for Resolution
+</details>
 
-**Agent Focus:** Verify against the LATEST TypeScript Strictness settings. Ensure the Content Script's message passing to the Background Service Worker uses the high-reliability `chrome.runtime.sendMessage` pattern (asynchronous). Check Event Listener Cleanup in `cleanupOnDomDetach` to prevent memory leaks.
+### Additional Context
 
-**Target Fix Location:** `src/content-script.ts` and related DOM manipulation handlers.
+Add any other context about the problem here. For example, is this happening on a specific website or framework (React, Vue, etc.)? Is it intermittent or always reproducible?