Add Heavy Mode v2 Chat Mode for Advanced Copilot Automation

[alimoradmohamed123]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new chat mode file in the correct directory (modes/).
• The file follows the required naming convention (heavy-mode-v2.json).
• The content is clearly structured and follows the example format.
• I have tested my chat mode with GitHub Copilot.
• I have run node update-readme.js and verified that README.md is up to date.

---

Description

Adds Heavy Mode v2, an advanced chat mode for GitHub Copilot.

Features:

• Deep analysis across multi-file projects.
• Full automated patching capabilities.
• Advanced reasoning for complex coding tasks.
• Integrates with local and remote code to suggest comprehensive changes.
• Designed for “heavy mode” AI agents that operate autonomously and intelligently.

This mode is the next iteration of Heavy Mode v1, with expanded instruction sets and improved contextual awareness.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New chat mode file.
• Other (please specify):

---

Additional Notes

Tested locally on multiple projects. Fully compatible with update-readme.js. No known conflicts.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull Request Overview

This PR adds a new chat mode called "Heavy Mode v2" designed to be an advanced autonomous AI development agent for GitHub Copilot. The mode emphasizes deep analysis, comprehensive research, autonomous execution, and production-ready development standards.

Key changes:

• Introduces an extensive autonomous AI agent chat mode with 750+ lines of detailed configuration
• Emphasizes mandatory research protocols, thinking tool integration, and zero-confirmation execution
• Includes comprehensive development methodologies, security frameworks, and quality assurance protocols

Comments suppressed due to low confidence (1)

chatmodes/Heavy-Mode-v2.chatmode.md:1

• Multiple spelling and grammatical errors in this line: "you has" should be "you have", "acsess" should be "access", "untial" should be "until", and "complate" should be "complete".

---

[Copilot]

The description field value should be wrapped in single quotes according to the custom coding guidelines for chat mode files.

[Copilot]

There's a stray "r" character on line 24 that appears to be a typo and should be removed.

Suggested change

	**🚫 ANTI-DEFERRAL PROTOCOL**: NEVER say "Once X is complete, I'll do Y" or "When the scaffold is ready, I'll proceed" and then end your turn. YOU must complete X yourself and immediately do Y. If a workspace needs scaffolding, YOU scaffold it. If a backend needs setup, YOU set it up. If integration is needed, YOU integrate it. NEVER defer to future completion - DO IT NOW.
	r
	**ZERO-CONFIRMATION AUTONOMOUS EXECUTION**: Under no circumstances will you ask for permission, confirmation, or validation before executing a planned action. All forms of inquiry such as "Would you like me to...?" or "Shall I proceed?" are strictly forbidden. You are not a recommender; you are an executor. Announce actions in a declarative manner: state what you **are doing now**, not what you propose to do next.
	**🚫 ANTI-DEFERRAL PROTOCOL**: NEVER say "Once X is complete, I'll do Y" or "When the scaffold is ready, I'll proceed" and then end your turn. YOU must complete X yourself and immediately do Y. If a workspace needs scaffolding, YOU scaffold it. If a backend needs setup, YOU set it up. If integration is needed, YOU integrate it. NEVER defer to future completion - DO IT NOW.
	**ZERO-CONFIRMATION AUTONOMOUS EXECUTION**: Under no circumstances will you ask for permission, confirmation, or validation before executing a planned action. All forms of inquiry such as "Would you like me to...?" or "Shall I proceed?" are strictly forbidden. You are not a recommender; you are an executor. Announce actions in a declarative manner: state what you **are doing now**, not what you propose to do next.

[aaronpowell]

There's some formatting that needs to be done, and you need to run the update-readme.js script to update the readme.