tribunal-kit 4.5.0 → 4.6.0

package/.agent/scripts/compile_router.py

@@ -0,0 +1,112 @@
+import os
+import re
+import json
+import logging
+from pathlib import Path
+
+# Configure basic logging
+logging.basicConfig(level=logging.INFO, format="%(levelname)s: %(message)s")
+
+AGENT_DIR = Path(__file__).parent.parent
+SKILLS_DIR = AGENT_DIR / "skills"
+ROUTING_INDEX_PATH = AGENT_DIR / "routing_index.json"
+
+FRONTMATTER_REGEX = re.compile(r"^---\n(.*?)\n---", re.DOTALL | re.MULTILINE)
+
+def parse_yaml_frontmatter(content: str) -> dict:
+    """Very basic YAML parser specifically for the expected frontmatter."""
+    match = FRONTMATTER_REGEX.search(content)
+    if not match:
+        return {}
+    
+    frontmatter_text = match.group(1)
+    data = {}
+    current_key = None
+    
+    lines = frontmatter_text.split("\n")
+    for line in lines:
+        if not line.strip() or line.startswith("#"):
+            continue
+            
+        # Check if this line is part of a nested block (like routing:)
+        if line.startswith("  ") and current_key:
+            if not isinstance(data[current_key], dict):
+                data[current_key] = {}
+            
+            sub_line = line.strip()
+            if ":" in sub_line:
+                k, v = [x.strip() for x in sub_line.split(":", 1)]
+                # Basic array parsing for triggers, co-requires, etc: [a, b, c]
+                if v.startswith("[") and v.endswith("]"):
+                    items = [x.strip().strip("'\"") for x in v[1:-1].split(",") if x.strip()]
+                    data[current_key][k] = items
+                else:
+                    data[current_key][k] = v
+            continue
+            
+        # Top-level keys
+        if ":" in line:
+            k, v = [x.strip() for x in line.split(":", 1)]
+            current_key = k
+            if not v:
+                # Value is on the next indented lines
+                data[k] = {}
+            else:
+                data[k] = v
+
+    return data
+
+def main():
+    if not SKILLS_DIR.exists():
+        logging.error(f"Skills directory not found: {SKILLS_DIR}")
+        return
+
+    index = []
+    skill_dirs = [d for d in SKILLS_DIR.iterdir() if d.is_dir()]
+    
+    logging.info(f"Scanning {len(skill_dirs)} skill directories...")
+    
+    for skill_dir in skill_dirs:
+        skill_file = skill_dir / "SKILL.md"
+        if not skill_file.exists():
+            continue
+            
+        with open(skill_file, "r", encoding="utf-8") as f:
+            content = f.read()
+            
+        frontmatter = parse_yaml_frontmatter(content)
+        if not frontmatter:
+            continue
+            
+        name = frontmatter.get("name", skill_dir.name)
+        desc = frontmatter.get("description", "")
+        routing = frontmatter.get("routing", {})
+        
+        # Build the compressed index entry
+        entry = {
+            "name": name,
+            "description": desc,
+        }
+        
+        # Only include routing metadata if it exists
+        if routing:
+            if isinstance(routing, dict):
+                for k, v in routing.items():
+                    entry[f"routing_{k}"] = v
+            else:
+                entry["routing"] = routing
+                
+        index.append(entry)
+
+    # Sort alphabetically for deterministic output
+    index.sort(key=lambda x: x["name"])
+
+    # Write the index
+    with open(ROUTING_INDEX_PATH, "w", encoding="utf-8") as f:
+        json.dump({"skills": index}, f, indent=2)
+        
+    logging.info(f"Compiled {len(index)} skills into {ROUTING_INDEX_PATH}")
+    logging.info(f"File size: {os.path.getsize(ROUTING_INDEX_PATH)} bytes")
+
+if __name__ == "__main__":
+    main()

package/.agent/scripts/migrate_skills_frontmatter.py

@@ -0,0 +1,64 @@
+import os
+import re
+import logging
+from pathlib import Path
+
+logging.basicConfig(level=logging.INFO, format="%(levelname)s: %(message)s")
+
+AGENT_DIR = Path(__file__).parent.parent
+SKILLS_DIR = AGENT_DIR / "skills"
+
+FRONTMATTER_REGEX = re.compile(r"^---\n(.*?)\n---", re.DOTALL | re.MULTILINE)
+
+def inject_routing_frontmatter(content: str) -> str:
+    """Injects a baseline routing block into the YAML frontmatter if it doesn't exist."""
+    match = FRONTMATTER_REGEX.search(content)
+    if not match:
+        return content
+        
+    frontmatter_text = match.group(1)
+    
+    if "\nrouting:" in frontmatter_text or frontmatter_text.startswith("routing:"):
+        # Already migrated
+        return content
+        
+    # Append the routing block to the end of the frontmatter
+    new_routing_block = "\nrouting:\n  domain: general\n  tier: basic"
+    new_frontmatter = frontmatter_text + new_routing_block
+    
+    # Replace the old frontmatter with the new one
+    new_content = content[:match.start(1)] + new_frontmatter + content[match.end(1):]
+    return new_content
+
+def main():
+    if not SKILLS_DIR.exists():
+        logging.error(f"Skills directory not found: {SKILLS_DIR}")
+        return
+
+    skill_dirs = [d for d in SKILLS_DIR.iterdir() if d.is_dir()]
+    migrated_count = 0
+    skipped_count = 0
+    
+    logging.info(f"Scanning {len(skill_dirs)} skill directories for migration...")
+    
+    for skill_dir in skill_dirs:
+        skill_file = skill_dir / "SKILL.md"
+        if not skill_file.exists():
+            continue
+            
+        with open(skill_file, "r", encoding="utf-8") as f:
+            content = f.read()
+            
+        new_content = inject_routing_frontmatter(content)
+        
+        if new_content != content:
+            with open(skill_file, "w", encoding="utf-8") as f:
+                f.write(new_content)
+            migrated_count += 1
+        else:
+            skipped_count += 1
+
+    logging.info(f"Migration complete: {migrated_count} files updated, {skipped_count} skipped.")
+
+if __name__ == "__main__":
+    main()

package/.agent/scripts/strengthen_skills.js

@@ -14,7 +14,7 @@
 const fs = require('fs');
 const path = require('path');
 
-const { RED, GREEN, YELLOW, BLUE, BOLD, RESET } = require('./colors.js');
+const { RED, GREEN, YELLOW, BLUE, BOLD, RESET } = require('./_colors.js');
 
 const GUARDRAILS_BLOCK = `
 

package/.agent/skills/advanced-rag-pipelines/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: advanced-rag-pipelines
 description: Production-grade Retrieval-Augmented Generation (RAG) mastery. Semantic chunking, Hybrid Search (Dense + Sparse/BM25), Cross-Encoder Reranking, and architecture-agnostic vector database management.
+routing:
+  domain: general
+  tier: basic
 ---
 
 # Advanced RAG Pipelines (Production AI Data)
@@ -8,6 +11,7 @@ description: Production-grade Retrieval-Augmented Generation (RAG) mastery. Sema
 You are an expert in building production-grade Retrieval-Augmented Generation (RAG) data pipelines. You understand that naive RAG (fixed chunking + Cosine similarity) fails in production. You architect systems that retrieve context with high precision using hybrid search, reranking, and semantic strategies.
 
 ## 1. Core Principles
+
 - **Garbage In, Garbage Out:** Vector embeddings are only as good as the chunking strategy. Never use arbitrary character counts for chunking code or complex documents.
 - **Hybrid Search is Mandatory:** Dense vectors (embeddings) are terrible at exact keyword matches (e.g., finding "ID-4912" or "v4.4.4"). Always combine Dense Search with Sparse Search (BM25) to catch both semantic intent and exact matches.
 - **Retrieve Many, Rerank to Few:** It is cheaper and more accurate to retrieve 50 candidate chunks from a Vector DB and use a Cross-Encoder to rerank them down to the top 5 for the LLM.
@@ -15,12 +19,15 @@ You are an expert in building production-grade Retrieval-Augmented Generation (R
 ## 2. Advanced Architectural Patterns
 
 ### A. Semantic Chunking
+
 Instead of splitting text every 1000 characters, split by structural bounds:
+
 - **Code:** Split by Abstract Syntax Tree (AST) nodes (functions, classes).
 - **Markdown:** Split by Header levels (`##`).
 - **Prose:** Use LLM-assisted proposition extraction (extracting atomic facts from sentences).
 
 ### B. Two-Stage Retrieval (Reranking)
+
 ```text
 1. User Query -> Embed -> Vector DB (Pinecone/Milvus/Pgvector)
 2. Retrieve Top K = 50 (Fast, low precision)
@@ -30,18 +37,23 @@ Instead of splitting text every 1000 characters, split by structural bounds:
 ```
 
 ### C. Query Transformation
+
 Never embed the user's raw query directly. Users write poor queries.
+
 - **HyDE (Hypothetical Document Embeddings):** Have the LLM write a fake answer to the query, then embed that fake answer to search the Vector DB.
 - **Query Routing:** Route "summarize" queries to a Graph database, and "how do I" queries to the Vector DB.
 
 ## 3. LLM Traps & Pre-Flight Checks
+
 - **TRAP:** Sending 20 chunks to the LLM. This dilutes the context (Lost in the Middle phenomenon) and increases cost.
 - **FIX:** Always rerank and aggressively filter down to 3-5 highly relevant chunks before the generation step.
 - **TRAP:** Not attaching metadata to chunks.
 - **FIX:** Always attach `{ source_file, line_numbers, date, author }` to the vector payload. This allows the Vector DB to pre-filter before calculating cosine similarity.
 
 ## Verification Protocol
+
 Before submitting code, ensure:
+
 1. Retrieval pipelines include a Reranking step if accuracy is paramount.
 2. BM25 / Sparse search is considered alongside standard dense embeddings.
 3. Chunks are injected into the final LLM prompt with explicit `<context>` XML boundaries to prevent prompt injection.
@@ -49,5 +61,49 @@ Before submitting code, ensure:
 ### 🛑 Verification-Before-Completion (VBC) Protocol
 
 **CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
+- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
+- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.
+
+---
+
+## 🤖 LLM-Specific Traps
+
+AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
+
+1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
+2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
+3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
+4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
+
+---
+
+## 🏛️ Tribunal Integration (Anti-Hallucination)
+
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
+
+### ❌ Forbidden AI Tropes
+
+1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
+2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
+3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+
+### ✅ Pre-Flight Self-Audit
+
+Review these questions before confirming output:
+
+```
+✅ Did I rely ONLY on real, verified tools and methods?
+✅ Is this solution appropriately scoped to the user's constraints?
+✅ Did I handle potential failure modes and edge cases?
+✅ Have I avoided generic boilerplate that doesn't add value?
+```
+
+### 🛑 Verification-Before-Completion (VBC) Protocol
+
+**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
 - ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
 - ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.

package/.agent/skills/agent-organizer/SKILL.md

@@ -1,154 +1,158 @@
----
-name: agent-organizer
-description: Master Agent orchestration framework. Coordination of sub-agents, workflow definitions, delegation patterns, state management across conversations, memory distillation, and execution loops. Use when assembling multi-agent systems or managing complex agent-to-agent architectures.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-02
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
----
-
-## Hallucination Traps (Read First)
-- ❌ Dispatching sub-agents without a context_summary -> ✅ Always send a trimmed context, never the full conversation
-- ❌ Assuming sub-agents share memory -> ✅ Each agent invocation is stateless unless explicitly passed context
-- ❌ Running agents sequentially when they are independent -> ✅ Use fan-out/fan-in for parallelizable work
-
----
-
-
-# Agent Organizer — Multi-Agent Orchestration Mastery
-
----
-
-## 1. The Delegation Sub-Agent Pattern
-
-Agents should defer specific domain problems to specialized sub-agents.
-
-```json
-// Define the payload contract the Worker Agent expects
-{
-  "taskId": "task-auth-migration-01",
-  "workerRole": "api-security-auditor",
-  "isolatedContext": {
-    "filesToScan": ["src/login.ts", "src/middleware.ts"],
-    "objective": "Identify unprotected mass assignments"
-  },
-  "requiredOutputFormat": "json_list"
-}
-```
-
-### Delegation Rules:
-1. **Never pass full histories:** Do not pass the entire conversation history to a worker sub-agent. Extract only the exact files and goal context required. (Context Window Budgeting).
-2. **Clear Boundaries:** If the worker is fixing CSS, it must not invent logic for the database.
-3. **Structured Handoff:** The parent agent requests JSON from the worker, parses it, and then acts. Let machines talk to machines through syntax, not prose.
-
----
-
-## 2. Execution Loops (Supervisor Pattern)
-
-A Supervisor decides *who* works and *when*, but does not execute the work.
-
-```
-[User Request: "Add OAuth and secure it"]
-       |
-[Supervisor Agent analyzing required skills...]
-       |
-       ├─> [Dispatches: authentication-best-practices]
-       |         (Worker builds OAuth implementation)
-       |
-       ├─> [Dispatches: api-security-auditor]
-       |         (Worker reviews implementation against OWASP)
-       |
-[Supervisor Agent synthesizes findings]
-       |
-[Action Executed / Git Commit]
-```
-
-### Handoff Signals
-A worker must return definitive state signals when yielding control:
-- `COMPLETE`: Goal achieved. Final diff generated.
-- `BLOCKED`: Missing context (e.g., "I need the `.env` schema").
-- `ERROR`: Script failed, requires manual Supervisor intervention.
-
----
-
-## 3. Session State Management (Memory)
-
-Agents lose memory across boundaries. The Organizer must explicitly persist context.
-
-1. **Short-Term Context:** Maintained natively in the active LLM context window.
-2. **Task State:** Maintained locally in `task.md`. Workers check-in and check-out checkboxes.
-3. **Long-Term Memory:** "Knowledge Items" (KIs). Distilling massive conversations down into a single `learnings.json` file injected on subsequent startups.
-
-```markdown
-<!-- task.md (The Global Execution State) -->
-# Current Objective: Build Chat Feature
-- [x] Initialize websocket connection
-- [/] (Worker: frontend-specialist) Build Chat UI component
-- [ ] (Worker: realtime-patterns) Implement presence sync
-```
-
----
-
-## 4. The Human-in-the-Loop (Socratic Gate)
-
-Automation without oversight is reckless. The Organizer manages when to pause and query the human.
-
-**Mandatory Gates:**
-1. **Approval Gate (Before Execution):** "I have drafted the architecture plan. Do you approve execution?"
-2. **Recovery Gate (After 3 Failures):** "The database migration script has failed 3 times. I am halting. How would you like to proceed?"
-
----
-
-
----
-
-
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.
-
-
-## Pre-Flight Checklist
-- [ ] Have I reviewed the user's specific constraints and requests?
-- [ ] Have I checked the environment for relevant existing implementations?
-
-## VBC Protocol (Verification-Before-Completion)
-You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
+---
+name: agent-organizer
+description: Master Agent orchestration framework. Coordination of sub-agents, workflow definitions, delegation patterns, state management across conversations, memory distillation, and execution loops. Use when assembling multi-agent systems or managing complex agent-to-agent architectures.
+allowed-tools: Read, Write, Edit, Glob, Grep
+version: 2.0.0
+last-updated: 2026-04-02
+applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
+routing:
+  domain: general
+  tier: basic
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Dispatching sub-agents without a context_summary -> ✅ Always send a trimmed context, never the full conversation
+- ❌ Assuming sub-agents share memory -> ✅ Each agent invocation is stateless unless explicitly passed context
+- ❌ Running agents sequentially when they are independent -> ✅ Use fan-out/fan-in for parallelizable work
+
+---
+
+# Agent Organizer — Multi-Agent Orchestration Mastery
+
+---
+
+## 1. The Delegation Sub-Agent Pattern
+
+Agents should defer specific domain problems to specialized sub-agents.
+
+```json
+// Define the payload contract the Worker Agent expects
+{
+  "taskId": "task-auth-migration-01",
+  "workerRole": "api-security-auditor",
+  "isolatedContext": {
+    "filesToScan": ["src/login.ts", "src/middleware.ts"],
+    "objective": "Identify unprotected mass assignments"
+  },
+  "requiredOutputFormat": "json_list"
+}
+```
+
+### Delegation Rules:
+
+1. **Never pass full histories:** Do not pass the entire conversation history to a worker sub-agent. Extract only the exact files and goal context required. (Context Window Budgeting).
+2. **Clear Boundaries:** If the worker is fixing CSS, it must not invent logic for the database.
+3. **Structured Handoff:** The parent agent requests JSON from the worker, parses it, and then acts. Let machines talk to machines through syntax, not prose.
+
+---
+
+## 2. Execution Loops (Supervisor Pattern)
+
+A Supervisor decides _who_ works and _when_, but does not execute the work.
+
+```
+[User Request: "Add OAuth and secure it"]
+       |
+[Supervisor Agent analyzing required skills...]
+       |
+       ├─> [Dispatches: authentication-best-practices]
+       |         (Worker builds OAuth implementation)
+       |
+       ├─> [Dispatches: api-security-auditor]
+       |         (Worker reviews implementation against OWASP)
+       |
+[Supervisor Agent synthesizes findings]
+       |
+[Action Executed / Git Commit]
+```
+
+### Handoff Signals
+
+A worker must return definitive state signals when yielding control:
+
+- `COMPLETE`: Goal achieved. Final diff generated.
+- `BLOCKED`: Missing context (e.g., "I need the `.env` schema").
+- `ERROR`: Script failed, requires manual Supervisor intervention.
+
+---
+
+## 3. Session State Management (Memory)
+
+Agents lose memory across boundaries. The Organizer must explicitly persist context.
+
+1. **Short-Term Context:** Maintained natively in the active LLM context window.
+2. **Task State:** Maintained locally in `task.md`. Workers check-in and check-out checkboxes.
+3. **Long-Term Memory:** "Knowledge Items" (KIs). Distilling massive conversations down into a single `learnings.json` file injected on subsequent startups.
+
+```markdown
+<!-- task.md (The Global Execution State) -->
+
+# Current Objective: Build Chat Feature
+
+- [x] Initialize websocket connection
+- [/] (Worker: frontend-specialist) Build Chat UI component
+- [ ] (Worker: realtime-patterns) Implement presence sync
+```
+
+---
+
+## 4. The Human-in-the-Loop (Socratic Gate)
+
+Automation without oversight is reckless. The Organizer manages when to pause and query the human.
+
+**Mandatory Gates:**
+
+1. **Approval Gate (Before Execution):** "I have drafted the architecture plan. Do you approve execution?"
+2. **Recovery Gate (After 3 Failures):** "The database migration script has failed 3 times. I am halting. How would you like to proceed?"
+
+---
 
+---
+
+AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
+
+1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
+2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
+3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
+4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
+
+---
+
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
+
+### ❌ Forbidden AI Tropes
+
+1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
+2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
+3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+
+Review these questions before confirming output:
+
+```
+✅ Did I rely ONLY on real, verified tools and methods?
+✅ Is this solution appropriately scoped to the user's constraints?
+✅ Did I handle potential failure modes and edge cases?
+✅ Have I avoided generic boilerplate that doesn't add value?
+```
+
+### 🛑 Verification-Before-Completion (VBC) Protocol
+
+**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
+- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
+- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.
+
+## Pre-Flight Checklist
+
+- [ ] Have I reviewed the user's specific constraints and requests?
+- [ ] Have I checked the environment for relevant existing implementations?
+
+## VBC Protocol (Verification-Before-Completion)
+
+You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
 
 ---
 
@@ -178,6 +182,7 @@ AI coding assistants often fall into specific bad habits when dealing with this
 ### ✅ Pre-Flight Self-Audit
 
 Review these questions before confirming output:
+
 ```
 ✅ Did I rely ONLY on real, verified tools and methods?
 ✅ Is this solution appropriately scoped to the user's constraints?
@@ -188,5 +193,6 @@ Review these questions before confirming output:
 ### 🛑 Verification-Before-Completion (VBC) Protocol
 
 **CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
 - ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
 - ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.