Add comprehensive documentation and guidelines for markdown, performance optimization, Playwright testing, secure coding, TypeScript development, and Copilot management

- Introduced markdown content rules and validation requirements in markdown.instructions.md
- Added React controls and platform libraries guidelines in pcf-react-platform-libraries.instructions.md
- Created extensive performance optimization instructions covering frontend, backend, and database best practices in performance-optimization.instructions.md
- Established Playwright test writing guidelines and structure in playwright-typescript.instructions.md
- Developed secure coding practices based on OWASP Top 10 in security-and-owasp.instructions.md
- Defined directives for managing Copilot interactions and code generation in taming-copilot.instructions.md
- Provided TypeScript 5.x and ES2022 development guidelines in typescript-5-es2022.instructions.md

.github/agents/Manegment.agent.md

@@ -21,6 +21,7 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
 </global_context>
 
 <workflow>
+
 1.  **Phase 1: Assessment and Delegation**:
     -   **Read Instructions**: Read `.github/copilot-instructions.md`.
     -   **Identify Goal**: Understand the user's request.
@@ -29,6 +30,13 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
         -   *Prompt*: "Research the necessary files for '{user_request}' and write a comprehensive plan detailing as many specifics as possible to `docs/plans/current_spec.md`. Be an artist with directions and discriptions. Include file names, function names, and component names wherever possible. Break the plan into phases based on the least amount of requests. Review and suggest updaetes to `.gitignore`, `codecove.yml`, `.dockerignore`, and `Dockerfile` if necessary. Return only when the plan is complete."
     - **Task Specifics**:
         - If the task is to just run tests or audits, there is no need for a plan. Directly call `QA_Security` to perform the tests and write the report. If issues are found, return to `Planning` for a remediation plan and delegate the fixes to the corresponding subagents.
+
+1.5 :  **Phase 1.5: Supervisor Review**:
+    -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
+    -   **Delegate Review**: Call `Supervisor` subagent.
+        -   *Prompt*: "Review the plan in `docs/plans/current_spec.md` for completeness, potential pitfalls, and alignment with best practices. Provide feedback or approval."
+    -   **Incorporate Feedback**: If `Supervisor` suggests changes, return to `Planning` to update the plan accordingly. Repeat this step until the plan is approved by `Supervisor`.
+
 2.  **Phase 2: Approval Gate**:
     -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
     -   **Present**: Summarize the plan to the user.