docs: update .github/PULL_REQUEST_TEMPLATE.md via Apex Optimizer

Author: chirag127

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,75 +1,73 @@
-# Pull Request Checklist & Review Directive
+# Pull Request Template
 
-<!--
+## 🚀 High-Velocity Contribution Checklist
 
-Thank you for contributing to JSErrorFlow! 
+**Please ensure all the following points are addressed before submitting your Pull Request:**
 
-Before submitting, please ensure this PR adheres to the Apex Technical Authority standards.
+### 1. ✨ Code Quality & Standards
 
-1. **Branch Naming:** Is your branch descriptive (e.g., `feature/new-dom-highlight` or `fix/error-parsing-bug`)?
-2. **Self-Review:** Have you reviewed your own changes against the architectural guidelines in AGENTS.md?
-3. **Testing:** Have you added/updated necessary unit/E2E tests?
-4. **Description:** Is the description clear, concise, and does it reference any related issues (e.g., `Closes #123`)?
+*   [ ] My code adheres to the **Apex Technical Authority** standards (Zero-Defect, High-Velocity, Future-Proof).
+*   [ ] Code is clean, well-commented, and follows established architectural patterns (e.g., SOLID, DRY).
+*   [ ] New code is covered by comprehensive unit and/or integration tests.
+*   [ ] All linting and formatting checks pass using the configured tools (e.g., Ruff for Python, Biome for TS/JS).
+*   [ ] README.md, AGENTS.md, and other relevant documentation have been updated to reflect changes.
 
--->
+### 2. 🧪 Testing & Verification
 
-## 🚀 Feature / Fix Summary
+*   [ ] I have run all tests locally (`pytest` for Python, `vitest` for TS/JS) and they are passing.
+*   [ ] If applicable, I have tested the changes manually in a development environment.
+*   [ ] End-to-end tests (e.g., Playwright) have been considered and updated if necessary.
 
-**Briefly describe the change this PR introduces.** (Why was this change necessary?)
+### 3. 📚 Documentation & Metadata
 
-<!-- Example: Implements real-time error visualization for unhandled promise rejections by hooking into the global `unhandledrejection` event. -->
+*   [ ] The **README.md** is updated with accurate descriptions, setup instructions, and usage examples.
+*   [ ] **AGENTS.md** is updated with the latest directives, including any new technology stack or architectural decisions.
+*   [ ] **Badges** in README.md and `badges.yml` are accurate and reflect the current build/coverage status.
+*   [ ] Topics for the repository have been reviewed and updated if necessary.
 
+### 4. 🚀 Deployment & CI/CD
 
-[Describe the core change here]
+*   [ ] CI/CD pipeline (`ci.yml`) is configured correctly and will execute the necessary build and test steps.
+*   [ ] The changes do not introduce any regressions that would break the CI pipeline.
 
+### 5. 📄 Licensing & Compliance
 
-## Related Issues
+*   [ ] All new code is compliant with the **CC BY-NC 4.0** license.
 
-Closes/Fixes/Relates to: (e.g., `Closes #42`, `Fixes #10`)
+### 6. 🚨 Security Considerations
 
----
+*   [ ] I have reviewed my changes for potential security vulnerabilities.
+*   [ ] Sensitive information is not hardcoded or exposed.
+*   [ ] Dependencies have been updated responsibly, and potential vulnerabilities have been addressed.
 
-## ✅ Checklist
+---
 
-**Developer Confirmation (Check all that apply):**
+## 📝 Description
 
-- [ ] **Code Quality:** Linting passes without warnings (`npm run lint`).
-- [ ] **Formatting:** Code formatting is consistent (`npm run format`).
-- [ ] **Testing:** Unit tests (`npm run test:unit`) pass successfully for the added scope.
-- [ ] **Documentation:** Any new public APIs or significant behavioral changes are documented in the relevant source files or README.
-- [ ] **Architecture Alignment:** Changes adhere to the established FSD/WXT patterns outlined in `AGENTS.md`.
-- [ ] **Security:** No secrets exposed, and input sanitization has been applied where necessary (especially DOM manipulation).
+Please provide a concise description of your changes. What problem does this PR solve?
 
----
+## 💡 Motivation
 
-## 🧠 Architecture & Technical Deep Dive
+Why are these changes necessary? What is the context?
 
-**For non-trivial changes, detail the architectural impact or implementation decisions.**
+## 🗺️ Proposed Changes
 
-1. **Component Impact:** Which main FSD layers were affected (e.g., `entities/error-model`, `features/visualizer-display`)?
-2. **DOM/Runtime Strategy:** How does this interact with the browser's event loop or MutationObserver (if applicable)?
-3. **Performance Considerations:** Are there any new DOM thrashing or excessive re-renders introduced? (Targeting sub-10ms updates).
+*   [Link to related issue, if any]
+*   Briefly list the key changes included in this PR.
 
-markdown
-[Technical notes here]
+## 🎯 What was changed?
 
+*   [Provide a summary of the changes. Be specific.]
 
----
+## 🎯 How was this tested?
 
-## 🖼️ Screenshots / Artifacts (If Applicable)
+*   [Describe the testing procedures performed.]
 
-<!-- If this PR affects the UI or observable behavior, include visual proof. -->
+## 📸 Screenshots (if applicable)
 
-| Before | After |
-| :---: | :---: | 
-| (Optional Screenshot/GIF) | (Optional Screenshot/GIF) |
+*   [Add screenshots or recordings of the UI changes.]
 
 ---
 
-## 🤖 Reviewer Guidance
-
-**Please focus review efforts on the following areas:**
-
-1.  Performance implications of the new visualizer logic.
-2.  Correctness of TypeScript type definitions introduced.
-3.  Adherence to WXT extension lifecycle management.
+**Repository:** `https://github.com/chirag127/JSErrorFlow-Realtime-DOM-Error-Visualizer-Browser-Extension`
+**Username:** `chirag127`