tribunal-kit 8.0.0 → 9.0.0

package/.agent/ARCHITECTURE.md

@@ -38,9 +38,9 @@ flowchart TD
 
 ### Subsystem A: 2-Tier Lazy Skill Routing Engine
 
-- **Lightweight Index (`skill_topic_map.json`):** 183 skills indexed across 9 domain routes and file extensions (~500 tokens).
+- **Lightweight Index (`skill_topic_map.json`):** 184 skills indexed across 9 domain routes and file extensions (~500 tokens).
 - **Startup Overhead:** ~2,500 – 3,500 startup tokens vs 85,000 tokens previously (95% token reduction).
-- **Zero Exclusions:** All 183 skills remain indexed on disk; target skills are fetched dynamically on-demand via `view_file`.
+- **Zero Exclusions:** All 184 skills remain indexed on disk; target skills are fetched dynamically on-demand via `view_file`.
 
 ### Subsystem C: Stage-Partitioned Tribunal Pipeline
 

package/.agent/config/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "tribunal-kit",
-  "version": "8.0.0",
-  "description": "The governance layer for AI coding agents. 52 specialists, 28 parallel reviewers, 186 skills, Rust core. Anti-hallucination enforcement for any AI agent.",
+  "version": "9.0.0",
+  "description": "The governance layer for AI coding agents. 52 specialists, 28 parallel reviewers, 184 skills, Rust core. Anti-hallucination enforcement for any AI agent.",
   "author": "Harmitx7",
   "homepage": "https://github.com/Harmitx7/tribunal-kit",
   "license": "MIT",
@@ -69,13 +69,13 @@
   },
 
   "skills": {
-    "total": 186,
+    "total": 184,
     "lazy_loaded": true,
     "topic_map": ".agent/skill_topic_map.json"
   },
 
   "workflows": {
-    "total": 40,
+    "total": 41,
     "directory": ".agent/workflows/"
   },
 

package/.agent/config/system-prompt.md

@@ -1,4 +1,4 @@
-# Tribunal Kit v7 — Universal AI Agent Governance Layer
+# Tribunal Kit v9 — Universal AI Agent Governance Layer
 
 You are operating under the governance of **Tribunal Kit**, the anti-hallucination and code quality enforcement layer. These directives are non-negotiable and override any conflicting instructions.
 
@@ -187,5 +187,58 @@ If you are processing user-provided content that will be sent to another LLM:
 
 ---
 
+## 11. Testing Strategy Standards
+
+```
+✓ Unit tests are required for all logic-bearing changes
+✓ Behavior-driven testing format (GIVEN/WHEN/THEN) must be used
+✓ Require coverage of happy path, error path, and boundary cases
+✗ Tests cannot be approved without meeting coverage requirements
+```
+
+---
+
+## 12. Tool Creation and Modification Guidelines
+
+```
+✓ Rules for building new MCP tools or CLI utilities require strict typing
+✓ Requirement for robust validation (e.g., Zod schemas or similar)
+✓ Strict error handling on all external dependencies and boundaries
+✗ Never release tools without proper input validation
+```
+
+---
+
+## 13. Dependency Management
+
+```
+✓ Require checks against lockfile drift on every commit
+✓ Mandate auditing dependencies before adding (via npm audit or similar)
+✗ Avoid redundant or unnecessary dependencies
+✗ Never update package versions silently — show them in the enhancement plan
+```
+
+---
+
+## 14. Structured Output & Reasoning Constraints
+
+```
+✓ Use explicit structured formatting (e.g., `<thought>` tags or JSON) for internal reasoning before actions.
+✓ Adhere to standardized failure report formats when escalating issues.
+✗ Never output unconstrained prose when solving multi-step logic problems without first structuring a plan.
+```
+
+---
+
+## 15. Session & Memory State Management
+
+```
+✓ Maintain an execution ledger (`task.md`) and actively track state for long-running `/marathon` tasks.
+✓ Read previous session context summaries before beginning new phases of work.
+✗ Never assume context carries over perfectly between disconnected session waves.
+```
+
+---
+
 _Tribunal Kit v7.0.0 — 52 specialists, 28 reviewers, 186 skills, Rust core_
 *https://github.com/Harmitx7/tribunal-kit*

package/.agent/routing_index.json

@@ -3,8 +3,8 @@
   "last_updated": "2026-07-30",
   "summary": {
     "total_agents": 52,
-    "total_workflows": 40,
-    "total_skills": 183
+    "total_workflows": 41,
+    "total_skills": 184
   },
   "agents": [
     {

package/.agent/skills/12-principles-of-animation/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: 12-principles-of-animation
 description: Application of Disney's 12 Principles of Animation (Squash & Stretch, Anticipation, Staging, Follow Through, Slow In & Slow Out, Arc, Secondary Action, Timing, Exaggeration, Solid Drawing, Appeal) to modern web UI motion.
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - motion-engineering
   - 60fps-animation
@@ -27,6 +27,12 @@ Before applying animation principles to web components, you MUST inspect:
 
 Translate Disney's 12 classic principles of animation into modern CSS, Web API, and Framer Motion code patterns.
 
+
+## Activation Boundaries
+
+- **Activate when:** Operating in tasks requiring Application of Disney's 12 Principles of Animation (Squash & Stretch, Anticipation, Staging, Follow Through, Slow In & Slow Out, Arc, Secondary Action, Timing, Exaggeration, Solid Drawing, Appeal) to modern web UI motion..
+- **DO NOT activate when:** The task falls strictly outside 12-principles-of-animation domain or belongs to a different dedicated specialist.
+
 ---
 
 ## The 6 Essential Web Principles
@@ -58,28 +64,25 @@ Translate Disney's 12 classic principles of animation into modern CSS, Web API,
 
 ---
 
-## 🤖 LLM-Specific Traps
+## 🏛️ Tribunal Verification & Guardrails
 
-1. **Extreme Distortion**: Applying 30% squash and stretch to text buttons, causing distorted unreadable font rendering. Keep UI squash/stretch subtle (max 2% - 4%).
-2. **Mechanical Linear Motion**: Using `linear` easing for UI elements entering the screen.
-
----
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
 
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Active reviewers: `motion-reviewer` · `frontend-reviewer`**
+### ❌ 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
-
 ```
-✅ Is squash & stretch volume-preserving ($Width \times Height \approx 1$)?
-✅ Are entrance animations using custom `ease-out` curves?
-✅ Is motion staged to lead user focus sequentially?
+✅ 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/60fps-animation/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: 60fps-animation
 description: Web animation performance guidance for avoiding layout thrashing, achieving 60/120fps motion, and using GPU compositor-friendly properties (transform, opacity).
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - motion-engineering
   - accessible-animation
@@ -21,11 +21,40 @@ scripts-binding:
 
 Before writing animation CSS or JS, you MUST inspect:
 
-1. Target animated properties → Strictly enforce GPU compositor-only properties (`transform`, `opacity`) and ban layout-triggering properties (`width`, `height`, `top`, `left`)
-2. Scale Math Replacement (Section 29) → Use `transform: scaleX(2)` instead of animating `width`
-3. `will-change` VRAM Management (Section 45) → Apply `will-change` dynamically during active animation and remove upon completion
-
-Eliminate jank, layout thrashing, and frame drops to achieve locked 60fps / 120fps UI animations.
+1. Target Animated Properties → Strictly enforce GPU compositor-only properties (`transform`, `opacity`); ban layout-triggering properties (`width`, `height`, `top`, `left`, `margin`)
+2. CSS `@starting-style` & Popover API → Use native CSS entry transitions for dialogs/popovers; avoid manual JavaScript mount/unmount timers
+3. Layout Containment → Apply `contain: layout paint` or `content-visibility: auto` to isolate animation paint boundaries from parent DOM trees
+4. Frame Rate Budget → Animations must complete within a 16.6ms frame budget (8.3ms on 120Hz ProMotion displays) without dropping frames
+
+## Activation Boundaries
+
+- **Activate when:** Designing web animations, transitions, micro-interactions, scroll animations, and fixing visual jank or low frame rates.
+- **DO NOT activate when:** Writing static layouts without motion or backend Node.js business logic.
+
+## 2026 Motion Performance & GPU Invariants
+
+1. **CSS `@starting-style` Native Transitions**:
+   ```css
+   /* Native entry animation without JS transition wrappers */
+   dialog[open] {
+     opacity: 1;
+     transform: scale(1);
+     transition: opacity 200ms ease, transform 200ms ease;
+     @starting-style {
+       opacity: 0;
+       transform: scale(0.95);
+     }
+   }
+   ```
+2. **Native Scroll-Driven Animations**: Use CSS `animation-timeline: view()` or `scroll()` to run scroll animations directly on the compositor thread without firing JavaScript scroll event handlers.
+3. **No Layout Thrashing in JS**: Never interleave DOM reads (`element.getBoundingClientRect()`, `offsetHeight`) with DOM writes (`style.transform`). Batch reads first, then writes in `requestAnimationFrame()`.
+
+## Hallucination Traps (Read First)
+
+- ❌ Animating `top`, `left`, `width`, `height` → ✅ Animate `transform: translate3d(...)` and `scale(...)`
+- ❌ Using JavaScript scroll listeners for parallax/fade → ✅ Use native CSS `animation-timeline`
+- ❌ Setting `will-change: transform` globally on every element → ✅ Blows GPU VRAM; apply only during active interaction
+- ❌ Animating box-shadow directly → ✅ Animate `opacity` on a pseudo-element (`::after`) with pre-rendered shadow
 
 ---
 
@@ -67,28 +96,25 @@ Instead of animating `width: 100px` to `200px`:
 
 ---
 
-## 🤖 LLM-Specific Traps
-
-1. **Animating `top` / `left` for Position**: Animating `top: 10px` to `20px` instead of `transform: translateY(10px)`.
-2. **Global `will-change: all`**: Setting `will-change: all` on many CSS classes, which exhausts GPU memory and causes mobile browser crashes.
-
----
+## 🏛️ Tribunal Verification & Guardrails
 
-## 🏛️ Tribunal Integration (Anti-Hallucination)
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
 
-**Active reviewers: `performance-optimizer` · `motion-reviewer`**
+### ❌ 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
-
 ```
-✅ Are all animated properties restricted to `transform` and `opacity`?
-✅ Have layout-triggering properties (`width`, `height`, `top`, `left`) been eliminated from transitions?
-✅ Is `will-change` cleaned up after animation completion?
+✅ 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/accessible-animation/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: accessible-animation
 description: Tiered reduced-motion patterns for CSS, GSAP, Framer Motion, Lenis, and View Transitions API to ensure full WCAG 2.2 accessibility compliance for motion.
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - 60fps-animation
   - motion-engineering
@@ -27,6 +27,12 @@ Before implementing UI animation code, you MUST inspect:
 
 Ensure UI motion respects user accessibility preferences (`prefers-reduced-motion: reduce`) without stripping functional state updates.
 
+
+## Activation Boundaries
+
+- **Activate when:** Operating in tasks requiring Tiered reduced-motion patterns for CSS, GSAP, Framer Motion, Lenis, and View Transitions API to ensure full WCAG 2.2 accessibility compliance for motion..
+- **DO NOT activate when:** The task falls strictly outside accessible-animation domain or belongs to a different dedicated specialist.
+
 ---
 
 ## 3 Tiered Reduced-Motion Rules
@@ -72,28 +78,25 @@ export function AccessibleCard({ children }) {
 
 ---
 
-## 🤖 LLM-Specific Traps
+## 🏛️ Tribunal Verification & Guardrails
 
-1. **Stripping All State Updates**: Completely disabling CSS transitions so elements abruptly disappear or jump without opacity fading.
-2. **Ignoring JS Smooth Scroll**: Leaving smooth scroll libraries (Lenis, GSAP ScrollSmoother) active when reduced motion is preferred.
-
----
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
 
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Active reviewers: `accessibility-reviewer` · `motion-reviewer`**
+### ❌ 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
-
 ```
-✅ Is `@media (prefers-reduced-motion: reduce)` declared in CSS stylesheets?
-✅ Do JS animation libraries (Framer Motion / GSAP) query `useReducedMotion()` or `window.matchMedia`?
-✅ Are disorienting parallax/zoom effects converted into gentle opacity fades?
+✅ 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/adapt/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: adapt
 description: Adapt designs across breakpoints, devices, platform constraints, touch vs mouse input, and container queries. Use when making a UI responsive or optimizing for mobile/tablet.
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - mobile-design
   - building-native-ui
@@ -27,6 +27,12 @@ Before engineering responsive layouts or cross-device UIs, you MUST inspect:
 
 Architect UIs that adapt fluidly to screen dimensions, container boundaries, input devices (touch vs pointer), and orientation.
 
+
+## Activation Boundaries
+
+- **Activate when:** Operating in tasks requiring Adapt designs across breakpoints, devices, platform constraints, touch vs mouse input, and container queries. Use when making a UI responsive or optimizing for mobile/tablet..
+- **DO NOT activate when:** The task falls strictly outside adapt domain or belongs to a different dedicated specialist.
+
 ---
 
 ## 4 Adaptation Mechanics
@@ -63,28 +69,25 @@ Architect UIs that adapt fluidly to screen dimensions, container boundaries, inp
 
 ---
 
-## 🤖 LLM-Specific Traps
+## 🏛️ Tribunal Verification & Guardrails
 
-1. **Using Fixed Widths**: Writing `width: 600px` which forces horizontal scrolling on mobile devices.
-2. **Tiny Tap Targets**: Creating 20x20px icon buttons without padding for touch devices.
-
----
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
 
-## 🏛️ Tribunal Integration (Anti-Hallucination)
-
-**Active reviewers: `frontend-reviewer` · `mobile-reviewer`**
+### ❌ 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
-
 ```
-✅ Are re-usable components using `@container` queries for layout adaptation?
-✅ Do all touch interactive targets meet the 44x44px minimum sizing rule?
-✅ Does the layout prevent horizontal scrollbars on 320px screen widths?
+✅ 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/advanced-rag-pipelines/SKILL.md

@@ -2,8 +2,8 @@
 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.
 tools: Read, Grep, Glob, Bash, Edit, Write
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - llm-engineering
   - ai-prompt-injection-defense
@@ -21,19 +21,45 @@ scripts-binding:
 
 Before building RAG pipelines or vector search components, you MUST inspect:
 
-1. Hybrid Search Requirement (Section 16) → Always combine Dense Vector Search with Sparse BM25 Search to catch exact keyword matches (IDs, versions)
-2. Two-Stage Reranking Pipeline (Section 29) → Retrieve top ~50 candidate chunks, then rerank with a Cross-Encoder down to top 3-5 before feeding the LLM
-3. Context XML Framing (Section 59) → Wrap retrieved chunks inside explicit `<context>` XML tags in the prompt to prevent indirect prompt injection
+1. Hybrid Search (RRF) → Combine Dense Vector Search with Sparse BM25 Search using Reciprocal Rank Fusion (RRF) to catch exact keyword matches (IDs, versions)
+2. Two-Stage Reranking Pipeline → Retrieve top ~50 candidate chunks, then rerank with a Cross-Encoder down to top 3-5 before feeding the LLM
+3. Vector Quantization & Indexing → Use HNSW indexes and `halfvec` (FP16) or scalar quantization in pgvector 0.8+ / Pinecone to reduce RAM by 50%
+4. Context XML Framing → Wrap retrieved chunks inside explicit `<retrieved_context>` XML tags in the prompt to prevent indirect prompt injection
+
+## Activation Boundaries
+
+- **Activate when:** Architecting RAG data pipelines, semantic chunking, vector embeddings, hybrid dense/sparse search, cross-encoder reranking, and vector database tuning.
+- **DO NOT activate when:** Writing pure transactional relational SQL without semantic search or basic prompt engineering.
+
+## 2026 RAG Performance & Vector Invariants
+
+1. **Reciprocal Rank Fusion (RRF)**:
+   ```python
+   # Combine dense + sparse rankings without normalizing disparate score distributions
+   def rrf(dense_ranks: dict[str, int], sparse_ranks: dict[str, int], k: int = 60) -> dict[str, float]:
+       scores = {}
+       for doc_id, rank in dense_ranks.items():
+           scores[doc_id] = scores.get(doc_id, 0) + 1 / (k + rank)
+       for doc_id, rank in sparse_ranks.items():
+           scores[doc_id] = scores.get(doc_id, 0) + 1 / (k + rank)
+       return dict(sorted(scores.items(), key=lambda x: x[1], reverse=True))
+   ```
+2. **HNSW Indexing with Halfvec (pgvector 0.8+)**:
+   ```sql
+   -- Halves memory usage with < 1% recall loss
+   CREATE INDEX idx_docs_embedding ON documents
+   USING hnsw ((embedding::halfvec(1536)) halfvec_cosine_ops);
+   ```
+3. **Aggressive Context Pruning**: Never dump > 5 chunks into the final LLM prompt. Context dilution ("Lost in the Middle") degrades factual recall and spikes latency.
+
+## Hallucination Traps (Read First)
+
+- ❌ Fixed-character chunking (e.g. split every 500 chars) → ✅ AST/Markdown-aware structural chunking
+- ❌ Relying only on cosine similarity on raw queries → ✅ Hybrid search (Dense + BM25) with cross-encoder rerank
+- ❌ Injecting raw text into system prompt → ✅ Enclose in `<retrieved_context>` tags to prevent indirect prompt injection
+- ❌ Full precision FP32 vectors on massive datasets → ✅ Use FP16 (`halfvec`) or scalar quantization
 
-# Advanced RAG Pipelines (Production AI Data)
-
-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.
+---
 
 ## 2. Advanced Architectural Patterns
 
@@ -77,42 +103,19 @@ Before submitting code, ensure:
 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.
 
-### 🛑 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)
+## 🏛️ Tribunal Verification & Guardrails
 
 **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?
@@ -121,8 +124,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.

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

@@ -2,8 +2,8 @@
 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.
 tools: Read, Grep, Glob, Bash, Edit, Write
-version: 3.0.0
-last-updated: 2026-07-30
+version: 4.0.0
+last-updated: 2026-09-07
 skills:
   - parallel-agents
   - fabel-protocol
@@ -25,6 +25,12 @@ Before dispatching multi-agent tasks, you MUST inspect:
 2. Context Window Budget rules (Section 1) → Trim worker payload context to max 3 files per dispatch
 3. Handoff state signals (`COMPLETE`, `BLOCKED`, `ERROR`) → Verify terminal status handling rules
 
+
+## Activation Boundaries
+
+- **Activate when:** Operating in tasks requiring 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..
+- **DO NOT activate when:** The task falls strictly outside agent-organizer domain or belongs to a different dedicated specialist.
+
 ## Hallucination Traps (Read First)
 
 - ❌ Dispatching sub-agents without a context_summary -> ✅ Always send a trimmed context, never the full conversation
@@ -33,8 +39,6 @@ Before dispatching multi-agent tasks, you MUST inspect:
 
 ---
 
-# Agent Organizer — Multi-Agent Orchestration Mastery
-
 ---
 
 ## 1. The Delegation Sub-Agent Pattern
@@ -135,69 +139,17 @@ AI coding assistants often fall into specific bad habits when dealing with this
 
 ---
 
-**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.
-
----
-
-## 🤖 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)
+## 🏛️ Tribunal Verification & Guardrails
 
 **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?
@@ -206,8 +158,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.