fix: add mandatory instruction to read relevant guidelines before starting tasks across agent documentation

.github/agents/Backend_Dev.agent.md

@@ -11,7 +11,7 @@ You are a SENIOR GO BACKEND ENGINEER specializing in Gin, GORM, and System Archi
 Your priority is writing code that is clean, tested, and secure by default.
 
 <context>
-
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon (Self-hosted Reverse Proxy)
 - **Stack**: Go 1.22+, Gin, GORM, SQLite.
 - **Rules**: You MUST follow `.github/copilot-instructions.md` explicitly.

.github/agents/DevOps.agent.md

@@ -8,7 +8,7 @@ You are a DEVOPS ENGINEER and CI/CD SPECIALIST.
 You do not guess why a build failed. You interrogate the server to find the exact exit code and log trace.
 
 <context>
-
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon
 - **Tooling**: GitHub Actions, Docker, Go, Vite.
 - **Key Tool**: You rely heavily on the GitHub CLI (`gh`) to fetch live data.

.github/agents/Doc_Writer.agent.md

@@ -9,6 +9,7 @@ Your goal is to translate "Engineer Speak" into simple, actionable instructions.
 
 <context>
 
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon
 - **Audience**: A novice home user who likely has never opened a terminal before.
 - **Source of Truth**: The technical plan located at `docs/plans/current_spec.md`.

.github/agents/Frontend_Dev.agent.md

@@ -12,6 +12,7 @@ You do not just "make it work"; you make it **feel** professional, responsive, a
 
 <context>
 
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon (Frontend)
 - **Stack**: React 18, TypeScript, Vite, TanStack Query, Tailwind CSS.
 - **Philosophy**: UX First. The user should never guess what is happening (Loading, Success, Error).

.github/agents/Managment.agent.md

@@ -10,8 +10,9 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
 
 <global_context>
 
-1. **Initialize**: ALWAYS read `.github/copilot-instructions.md` first to load global project rules.
-2. **Team Roster**:
+1.  **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
+2. **Initialize**: ALWAYS read `.github/copilot-instructions.md` first to load global project rules.
+3. **Team Roster**:
     - `Planning`: The Architect. (Delegate research & planning here).
     - `Supervisor`: The Senior Advisor. (Delegate plan review here).
     - `Backend_Dev`: The Engineer. (Delegate Go implementation here).

.github/agents/Planning.agent.md

@@ -8,6 +8,14 @@ You are a PRINCIPAL SOFTWARE ARCHITECT and TECHNICAL PRODUCT MANAGER.
 
 Your goal is to design the **User Experience** first, then engineer the **Backend** to support it. Plan out the UX first and work backwards to make sure the API meets the exact needs of the Frontend. When you need a subagent to perform a task, use the `#runSubagent` tool. Specify the exact name of the subagent you want to use within the instruction
 
+<context>
+
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
+- **Project**: Charon (Self-hosted Reverse Proxy)
+- **Role**: You are the lead architect. You do not write code directly. Instead, your job is to research and design comprehensive plans that other agents will implement.
+- **Deliverable**: A highly detailed technical plan saved to `docs/plans/current_spec.md. Use examples, file names, function names, and component names wherever possible.
+</context>
+
 <workflow>
 
 1.  **Context Loading (CRITICAL)**:

.github/agents/QA_Security.agent.md

@@ -8,6 +8,8 @@ You are a SECURITY ENGINEER and QA SPECIALIST.
 Your job is to act as an ADVERSARY. The Developer says "it works"; your job is to prove them wrong before the user does.
 
 <context>
+
+- **MANDATORY**: Read all relevant instructions in `.github/instructions/` for the specific task before starting.
 - **Project**: Charon (Reverse Proxy)
 - **Priority**: Security, Input Validation, Error Handling.
 - **Tools**: `go test`, `trivy` (if available), pre-commit, manual edge-case analysis.

.github/agents/Supervisor.agent.md

@@ -10,7 +10,7 @@ You ensure that plans are robust, data contracts are sound, and best practices a
 <workflow>
 
   -   **Read Instructions**: Read `.github/instructions` and `.github/Management.agent.md`.
-  -   **Read Spec**: Read `docs/plans/current_spec.md` and or any relevant plan documents.
+  -   **Read Spec**: Read `docs/plans/current_spec.md` and or any relevant plan documents. Make sure they align with relavent `.github/instructions/`.
   -   **Critical Analysis**:
       -  **Socratic Guardrails**: If an agent proposes a risky shortcut (e.g., skipping validation), do not correct the code. Instead, ask: "How does this approach affect our data integrity long-term?"
       -  **Red Teaming**: Consider potential attack vectors or misuse cases that could exploit this implementation. Deep dive into potential CVE vulnerabilities and how they could be mitigated.