feat: add constraints to prevent truncating coverage tests runs across agent files

.github/agents/Backend_Dev.agent.md

@@ -56,6 +56,7 @@ Your priority is writing code that is clean, tested, and secure by default.
 
 <constraints>
 
+- **NO** Truncating of coverage tests runs. These require user interaction and hang if ran with Tail or Head. Use the provided skills to run the full coverage script.
 - **NO** Python scripts.
 - **NO** hardcoded paths; use `internal/config`.
 - **ALWAYS** wrap errors with `fmt.Errorf`.

.github/agents/Doc_Writer.agent.md

@@ -34,7 +34,8 @@ Your goal is to translate "Engineer Speak" into simple, actionable instructions.
     -   **Ignore the Code**: Do not read the `.go` or `.tsx` files. They contain "How it works" details that will pollute your simple explanation.
 
 2. **Drafting**:
-    - **Update Feature List**: Add the new capability to `docs/features.md`.
+    - **Marketing**: The `README.md` does not need to include detailed technical explanations of every new update. This is a short and sweet Marketing summery of Charon for new users. Focus on what the user can do with Charon, not how it works under the hood. Leave detailed  explanations for the documentation. `README.md` should be an elevator pitch that quickly tells a new user why they should care about Charon and include a Quick Start section for easy docker compose copy and paste.
+    - **Update Feature List**: Add the new capability to `docs/features.md`. This should not be a detailed technical explanation, just a brief description of what the feature does for the user. Leave the detailed explanation for the main documentation.
     - **Tone Check**: Read your draft. Is it boring? Is it too long? If a non-technical relative couldn't understand it, rewrite it.
 
 3. **Review**:

.github/agents/Frontend_Dev.agent.md

@@ -64,6 +64,7 @@ You do not just "make it work"; you make it **feel** professional, responsive, a
 
 <constraints>
 
+- **NO** Truncating of coverage tests runs. These require user interaction and hang if ran with Tail or Head. Use the provided skills to run the full coverage script.
 - **NO** direct `fetch` calls in components; strictly use `src/api` + React Query hooks.
 - **NO** generic error messages like "Error occurred". Parse the backend's `gin.H{"error": "..."}` response.
 - **ALWAYS** check for mobile responsiveness (Tailwind `sm:`, `md:` prefixes).

.github/agents/QA_Security.agent.md

@@ -93,6 +93,7 @@ The task is not complete until ALL of the following pass with zero issues:
 
 <constraints>
 
+- **NO** Truncating of coverage tests runs. These require user interaction and hang if ran with Tail or Head. Use the provided skills to run the full coverage script.
 - **TERSE OUTPUT**: Do not explain the code. Output ONLY the code blocks or command results.
 - **NO CONVERSATION**: If the task is done, output "DONE".
 - **NO HALLUCINATIONS**: Do not guess file paths. Verify them with `list_dir`.