tribunal-kit 5.8.4 → 5.8.5

package/.agent/skills/frontend-design/SKILL.md

@@ -25,143 +25,142 @@ routing:
 
 ---
 
-## 1. Color Theory (HSL over HEX)
+## 1. Modern Color Systems (OKLCH & HSL)
 
-Never use raw flat HEX colors. Use HSL to build cohesive scales.
+Never use raw flat HEX colors. Use OKLCH (perceptually uniform) or HSL to build scalable, harmonic themes.
 
 ```css
 :root {
-  /* HSL allows programmatic adjustment of lightness/saturation */
-  --hue: 220;
-  --sat: 80%;
-
-  --bg-base: hsl(var(--hue), 15%, 98%);
-  --bg-surface: hsl(var(--hue), 20%, 100%);
-
-  --text-main: hsl(var(--hue), 40%, 10%);
-  --text-muted: hsl(var(--hue), 20%, 40%);
-
-  --primary: hsl(var(--hue), var(--sat), 50%);
-  --primary-hover: hsl(var(--hue), var(--sat), 40%); /* Darken via L */
+  /* OKLCH perceptual uniformity: lightness (0-100%), chroma (0-0.37), hue (0-360) */
+  --brand-primary: oklch(62% 0.21 275);
+  --brand-hover: oklch(from var(--brand-primary) calc(l - 0.1) c h); /* Relative Color Syntax */
+  
+  --bg-base: oklch(98% 0.005 240);
+  --bg-surface: oklch(100% 0 0);
+  --text-main: oklch(20% 0.02 240);
+  --text-muted: oklch(50% 0.02 240);
 }
 
-/* OLED Dark Mode */
-@media (prefers-color-scheme: dark) {
-  :root {
-    --bg-base: hsl(var(--hue), 10%, 2%);
-    --bg-surface: hsl(var(--hue), 10%, 6%);
-    --text-main: hsl(var(--hue), 20%, 95%);
-    --text-muted: hsl(var(--hue), 10%, 60%);
-  }
+/* Light/Dark mode via native light-dark() function or OLED media query */
+:root {
+  color-scheme: light dark;
+  --bg-surface: light-dark(oklch(100% 0 0), oklch(15% 0.01 240));
+  --text-main: light-dark(oklch(20% 0.02 240), oklch(95% 0.01 240));
 }
 ```
 
-## 2. Spatial Systems & Grid Mathematics
+---
+
+## 2. Spatial Systems & Container Queries
 
-Design relies on structural rhythm. Use an **8px base system**.
+Design relies on structural rhythm and component-level adaptability.
 
-- **Micro padding**: `4px`, `8px` (Tags, List items)
-- **Component padding**: `16px`, `24px` (Cards, Inputs, Modals)
-- **Section spacing**: `48px`, `64px`, `96px` (Page sections)
-- **Line height**: Body `1.5`, Headings `1.1` or `1.2`.
+- **Base Spacing Grid (8px)**: Micro `4px`, `8px` | Component `16px`, `24px` | Section `48px`, `64px`, `96px`
+- **Nested Border Radius Formula**: `outer_radius = inner_radius + padding`
+- **Fluid Typography**: Use `clamp()` and `cqi` container units over macro media queries.
 
 ```css
-/* Fluid Typography (Clamp) */
-h1 {
-  /* Min 2rem, fluidly scale between 480px-1200px, Max 4rem */
-  font-size: clamp(2rem, 5vw, 4rem);
-  letter-spacing: -0.02em; /* Tighten large text */
+/* Container Queries for Portable Components */
+.card-container {
+  container-type: inline-size;
+  container-name: card;
+}
+
+@container card (min-width: 400px) {
+  .card-body {
+    display: grid;
+    grid-template-columns: 1fr 2fr;
+    gap: 1.5cqi;
+  }
+}
+
+/* Typographic Balance */
+h1, h2, h3 {
+  font-size: clamp(2rem, 4vw + 1rem, 4rem);
+  letter-spacing: -0.02em;
+  text-wrap: balance; /* Prevents awkward multiline headline breaks */
 }
 
 p {
   font-size: 1rem;
-  max-width: 65ch; /* Optimal reading length */
+  max-width: 65ch;
+  text-wrap: pretty; /* Eliminates typographical orphans in body text */
 }
 ```
 
 ---
 
-## 3. Interaction & "Juice" (Micro-interactions)
+## 3. Interaction & Entry Motion (@starting-style)
 
-A premium UI reacts to the user instantly and smoothly. Focus on state transitions.
+A premium UI reacts to user actions instantly and provides smooth DOM mount transitions.
 
 ```css
-/* Smooth generic transition */
+/* Physical press feedback */
 .btn {
-  transition: all 0.2s cubic-bezier(0.25, 0.46, 0.45, 0.94);
+  transition: transform 0.15s cubic-bezier(0.2, 0.8, 0.4, 1), box-shadow 0.15s ease;
 }
-
-/* Active Depth - The physical button push */
 .btn:active {
   transform: scale(0.97);
 }
 
-/* Hardware-Accelerated Shadows */
-.card {
-  box-shadow:
-    0 4px 6px -1px rgba(0, 0, 0, 0.1),
-    0 2px 4px -1px rgba(0, 0, 0, 0.06);
-  transition:
-    transform 0.3s ease,
-    box-shadow 0.3s ease;
+/* Entry/Exit Animations for DOM Elements (@starting-style) */
+.toast {
+  display: none;
+  opacity: 0;
+  transform: translateY(8px);
+  transition: opacity 0.25s ease, transform 0.25s ease, display 0.25s allow-discrete;
+}
+.toast.is-open {
+  display: flex;
+  opacity: 1;
+  transform: translateY(0);
 }
-.card:hover {
-  transform: translateY(-4px); /* Float effect */
-  box-shadow:
-    0 20px 25px -5px rgba(0, 0, 0, 0.1),
-    0 10px 10px -5px rgba(0, 0, 0, 0.04);
+@starting-style {
+  .toast.is-open {
+    opacity: 0;
+    transform: translateY(8px);
+  }
 }
 ```
 
 ---
 
-## 4. Modern Glassmorphism & Depth
+## 4. Modern Glassmorphism & Multi-Layer Depth
 
-Flat design is dead. Modern UI uses depth, layering, and blur.
+Avoid flat 1px borders and muddy single shadows. Use multi-layered elevation.
 
 ```css
-/* Frosted Glass */
-.glass {
-  background: rgba(255, 255, 255, 0.7);
+.card {
+  background: light-dark(rgba(255, 255, 255, 0.8), rgba(20, 20, 25, 0.8));
   backdrop-filter: blur(16px);
   -webkit-backdrop-filter: blur(16px);
-  border: 1px solid rgba(255, 255, 255, 0.2);
+  border: 1px solid light-dark(rgba(0, 0, 0, 0.08), rgba(255, 255, 255, 0.12));
   border-radius: 16px;
+  box-shadow: 
+    0 1px 2px oklch(0% 0 0 / 0.05),
+    0 4px 12px oklch(0% 0 0 / 0.08);
 }
 ```
 
 ---
 
-## 5. Forms and High-Friction UI
-
-Forms are where users drop off. They must be flawless.
+## 5. Accessibility (WCAG 2.2 AA Standards)
 
-- **Auto-focus** the first input on modal open.
-- **Labels** must be visible outside the input (not just placeholders).
-- **Validation** happens `onBlur` (when leaving), NOT `onChange` (typing).
-- **Submit buttons** show loading spinners, disable inputs, and prevent double-clicks.
+Design is broken if it excludes users.
+- ✅ **SC 2.5.8 Target Size**: Interactive controls must be at least `24x24px` CSS pixels (min `44x44px` for touch targets).
+- ✅ **SC 2.4.11 Focus Not Obscured**: Focused elements must never be completely hidden by sticky headers/footers.
+- ✅ **SC 2.4.13 Focus Appearance**: Visible focus rings must achieve `3:1` contrast ratio with a minimum 2px perimeter offset.
+- ✅ **Color Alone**: Never rely solely on color to convey state (pair error alerts with icons).
 
 ```css
-/* Focus-visible: Only show ring for keyboard nav, not mouse clicks */
-button:focus-visible {
-  outline: 2px solid var(--primary);
-  outline-offset: 2px;
+button:focus-visible, a:focus-visible {
+  outline: 2px solid var(--brand-primary);
+  outline-offset: 3px;
 }
 ```
 
 ---
 
-## 6. Accessibility (WCAG 2.2 AA)
-
-Design is fundamentally broken if it excludes users.
-
-- ✅ Interactive elements need `aria-label` if not visually labeled.
-- ✅ Custom dropdowns/selects must support Arrow Keys and Escape.
-- ✅ Color alone cannot convey state (Error text must have an icon too `❌ Password invalid`).
-- ✅ Hide decorative SVG/icons from screen readers `aria-hidden="true"`.
-
----
-
 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.

package/.agent/skills/impeccable/SKILL.md

@@ -35,11 +35,13 @@ The gold standard framework for crafting bespoke, world-class web applications t
 - **Intentional Motion**: Animations exist ONLY to convey spatial continuity, provide press feedback, or indicate state changes.
 - **Duration Constraints**: Micro-interactions $\le 160\text{ms}$; dropdowns/popovers $\le 220\text{ms}$; page transitions $\le 300\text{ms}$.
 - **Physically Grounded Entrances**: Elements scale in from `scale(0.96)` and opacity `0`, anchored to their trigger origin.
+- **DOM Entry (@starting-style)**: Use `@starting-style` with `transition-behavior: allow-discrete` for smooth `display: none` to `display: block` entrance animations without JS overhead.
 
 ### 4. Layout Mechanics & Spatial Math
 - **8px Grid System**: Every margin, padding, gap, and height MUST derive from an 8px grid (or 4px micro-grid).
 - **Asymmetrical Balance**: Avoid cookie-cutter centered layouts for SaaS apps. Use strong left-aligned structural axes with generous negative space.
 - **Container Queries**: Components adjust layout based on container size (`@container`), not viewport size (`@media`), making them context-agnostic.
+- **WCAG 2.2 AA Target Size (SC 2.5.8)**: All interactive targets MUST measure at least `24x24px` CSS pixels (min `44x44px` for touch).
 
 ---
 

package/.agent/skills/motion-engineering/SKILL.md

@@ -93,216 +93,118 @@ gsap.ticker.add((time) => lenis.raf(time * 1000));
 gsap.ticker.lagSmoothing(0);
 ```
 
-### 3. Page Transitions (View Transitions API)
+### 3. Page Transitions (Native-First View Transitions API)
 
 ```css
-/* CSS — define shared elements */
+/* CSS — Browser-native page transition (Zero JS runtime cost) */
+@view-transition {
+  navigation: auto;
+}
+
 .card-image {
-  view-transition-name: active-image;
-} /* MUST BE UNIQUE */
+  view-transition-name: active-image; /* MUST BE UNIQUE IN DOM */
+}
 ::view-transition-old(active-image) {
-  animation: fade-out 0.3s ease;
+  animation: fade-out 0.25s cubic-bezier(0.4, 0, 0.2, 1);
 }
 ::view-transition-new(active-image) {
-  animation: scale-in 0.3s ease;
+  animation: scale-in 0.25s cubic-bezier(0, 0, 0.2, 1);
 }
 ```
 
-### 4. Loading & Skeleton Animations
-
-Never block the UI entirely. Use structural loading.
-
-```css
-/* Shimmer structural animation */
-.skeleton {
-  background: linear-gradient(90deg, #f0f0f0 25%, #e0e0e0 50%, #f0f0f0 75%);
-  background-size: 200% 100%;
-  animation: shimmer 1.5s infinite linear;
-}
-@keyframes shimmer {
-  100% {
-    background-position: -200% 0;
+```tsx
+// SPA Route Navigation Trigger with Fallback
+function navigateWithTransition(url: string, navigate: (path: string) => void) {
+  if (!document.startViewTransition) {
+    navigate(url);
+    return;
   }
+  document.startViewTransition(() => {
+    navigate(url);
+  });
 }
 ```
 
----
-
-## TIER 2: Narrative & Immersive (Medium Implementation)
-
-_Used for brand storytelling, heroes, and engagement._
-
-### 5. 3D & Immersive Animations
+### 4. DOM Entry & Exit Animations (@starting-style)
 
-The leading trend of 2026. Use React Three Fiber.
-
-```tsx
-// WebGL Scene basics
-import { Canvas, useFrame } from "@react-three/fiber";
-function RotatingCube() {
-  const meshRef = useRef();
-  useFrame((state, delta) => (meshRef.current.rotation.x += delta));
-  return (
-    <mesh ref={meshRef}>
-      <boxGeometry />
-      <meshStandardMaterial color="hotpink" />
-    </mesh>
-  );
+```css
+/* CSS @starting-style allows animating entry from display: none */
+.modal {
+  display: none;
+  opacity: 0;
+  transform: scale(0.95);
+  transition: 
+    opacity 0.2s ease, 
+    transform 0.2s cubic-bezier(0.2, 0.8, 0.4, 1), 
+    display 0.2s allow-discrete;
 }
-```
 
-### 7. Kinetic Typography
+.modal[open] {
+  display: block;
+  opacity: 1;
+  transform: scale(1);
+}
 
-```tsx
-// Word-by-word spring reveal (Framer Motion)
-const words = "Immersive storytelling".split(" ");
-const wordVariants = { hidden: { opacity: 0, y: 20 }, visible: { opacity: 1, y: 0 } };
-
-<motion.h1 transition={{ staggerChildren: 0.05 }} initial="hidden" whileInView="visible" viewport={{ once: true }}>
-  {words.map((w, i) => (
-    <motion.span key={i} variants={wordVariants}>
-      {w}{" "}
-    </motion.span>
-  ))}
-</motion.h1>;
+@starting-style {
+  .modal[open] {
+    opacity: 0;
+    transform: scale(0.95);
+  }
+}
 ```
 
-### 8. Background Animations & 9. Illustrations
-
-- **Backgrounds:** Use CSS `@keyframes` on pseudo-elements with `filter: blur()` for ambient gradients, avoiding repaints.
-- **Illustrations:** Use Rive for interactive state machines, or Lottie via `lottie-react` for simple timeline playback.
-
----
-
-## TIER 3: Advanced & Emerging (Concepts & Tools)
-
-_Highly interactive components elevating standard UI._
-
-- **6. Motion UI & State Transitions:** Use Framer Motion's `layout` prop. Morphing a list item into a modal requires `<motion.div layoutId="item-1">` on both states. Wrap the app in `<LayoutGroup>`.
-- **10. Physics-based:** Animate like real-world objects. Instead of `duration`, define `mass`, `stiffness`, and `damping` in physics springs to simulate gravity and tension.
-- **11. Morphing & Shape:** GSAP `MorphSVGPlugin`. Requires SVGs with comparable path points or GSAP will interpolate poorly. Alternatively, animate CSS `border-radius` for fluid blobs.
-- **12. Glassmorphism:** Animate `backdrop-filter: blur(10px)` but beware of performance costs on mobile. Render shadows via `filter: drop-shadow()` combined with slight `translateY` on hover.
-- **13. Cursor-based:** Modern standard is CSS variables bound to mouse position. Calculate `clientX` relative to the element bounding box and update `--mouse-x` to drive `radial-gradient` masks.
-- **14. AI-driven Adaptive:** Motion that learns. If a user speeds through a form, UI transitions accelerate. If they linger, ambient motion plays. Controlled by tracking interaction deltas and mapping them to global spring configurations.
-- **15. Gamified:** Progress bars that burst on completion, haptic-synchronized checkmarks. Combine SVGs with explicit, highly exaggerated elastic overshoot scales (`scale: [1, 1.2, 0.9, 1]`) on reward thresholds.
-
----
-
-## TIER 4: Specialized (Rules & Fallbacks)
-
-_Niche requirements where performance or specific constraints dominate._
-
-- **16. Video + Motion Hybrid:** Scrubbing `<video>` tags with scroll. Requires pre-encoding video rapidly with keyframes every 1 frame, drawing frames to a `<canvas>` element via `requestAnimationFrame` linked to scroll progress.
-- **17. Experimental:** Glitch effects via overlapping CSS `clip-path` animations. High processing cost.
-- **18. Navigation:** Mega-menus must use `<AnimatePresence>` to prevent DOM unmount before the exit animation resolves. Include exit delays so users don't trigger flickering by rapidly moving the mouse off the nav.
-- **19. Data Visualization:** D3 handles math, React handles DOM, Framer/Spring handles interpolation between D3 datasets. Never let D3 mutate the DOM directly inside a React app.
-- **20. Performance-first Subtle Motion:** Strictly `opacity`, `transform`, CSS-only. Use `@starting-style` for popovers and dialogs to avoid JS intervention.
-
 ---
 
 ## Accessibility & Performance Invariants (Global Rules)
 
 1. **The WCAG 2.2 AA Motion Rule:**
+   Always respect `prefers-reduced-motion`. Fall back to instant opacity or no-op motion.
 
 ```tsx
-import { useReducedMotion } from "framer-motion";
-const reduce = useReducedMotion();
-// Safe: opacity, color
-// Conditional: translate, scale, rotate
-<motion.div animate={{ x: reduce ? 0 : 100, opacity: 1 }} transition={{ duration: reduce ? 0 : 0.5 }} />;
+import { useReducedMotion } from "motion/react";
+
+function AccessibleComponent() {
+  const shouldReduceMotion = useReducedMotion();
+  
+  return (
+    <motion.div
+      animate={{ 
+        x: shouldReduceMotion ? 0 : 100, 
+        opacity: 1 
+      }}
+      transition={{ duration: shouldReduceMotion ? 0 : 0.3 }}
+    />
+  );
+}
 ```
 
 2. **The 120fps GPU Rule:**
    Never animate `width`, `height`, `left`, `top`, `margin`, or `padding`. This triggers layout recalculation algorithms. Use `transform: scale()` or `transform: translate()` instead.
 
-3. **The Cleanup Rule:**
-   Any GSAP ScrollTrigger timeline must use `ScrollTrigger.killAll()` or React's `useGSAP` cleanup functions to avoid memory leaks on SPA route changes.
-
----
-
-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.
+3. **The GSAP Memory Cleanup Rule:**
+   Any GSAP ScrollTrigger timeline must use `@gsap/react` `useGSAP` or explicit `tl.kill()` cleanup to avoid memory leaks on SPA route changes.
 
 ---
 
 ## 🤖 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.
+1. **Over-animating Static UI:** Animating page titles and static text on simple forms.
+2. **Missing `allow-discrete`:** Animating `display` or `popover` without `transition-behavior: allow-discrete`.
+3. **GSAP Memory Leaks:** Forgetting to kill GSAP timelines on component unmount.
 
 ---
 
 ## 🏛️ 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?
+✅ Are all animations constrained to GPU-friendly properties (transform, opacity)?
+✅ Is prefers-reduced-motion handled natively or via hooks?
+✅ Are view-transition-name attributes unique across the entire active DOM?
 ```
 
 ### 🛑 Verification-Before-Completion (VBC) Protocol
 
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+Inspect motion frame performance in DevTools Rendering tab to verify 60/120fps compositor execution without layout thrashing.
 
-- ❌ **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/workflows/tribunal-full.md

@@ -1,9 +1,9 @@
 ---
-description: Runs ALL 19 parallel reviewers simultaneously. Maximum hallucination coverage. Use before merging any AI-generated code, before production deployments, or when maximum confidence is required.
+description: Runs ALL 20 parallel reviewers simultaneously. Maximum hallucination coverage. Use before merging any AI-generated code, before production deployments, or when maximum confidence is required.
 required-skills: all domain skills auto-loaded
 ---
 
-# /tribunal-full — Complete 19-Reviewer Audit
+# /tribunal-full — Complete 20-Reviewer Audit
 
 $ARGUMENTS
 
@@ -32,7 +32,7 @@ Read BEFORE full review:
 
 ---
 
-## 19 Reviewers — All Active Simultaneously
+## 20 Reviewers — All Active Simultaneously
 
 ```
 Tier 1: Always active (universal concerns)
@@ -68,7 +68,7 @@ Tier 4: Performance Swarm (token-scoped specialists)
 
 ## Active Reviewers by Code Type
 
-Not all 19 reviewers produce meaningful findings on all code types. Active reviewers detect their first finding immediately — inactive reviewers auto-pass with "N/A for this code type."
+Not all 20 reviewers produce meaningful findings on all code types. Active reviewers detect their first finding immediately — inactive reviewers auto-pass with "N/A for this code type."
 
 | Code Under Review   | Critical Reviewers                                                |
 | :------------------ | :---------------------------------------------------------------- |
@@ -86,7 +86,7 @@ Not all 19 reviewers produce meaningful findings on all code types. Active revie
 ## Verdict Aggregation
 
 ```
-All 19 verdicts are collected. Aggregated result:
+All 20 verdicts are collected. Aggregated result:
 
 If ANY reviewer = ❌ REJECTED → Global verdict: ❌ REJECTED (must fix before Human Gate)
 If any reviewer = ⚠️ WARNING  → Global verdict: ⚠️ WARNINGS (proceed with attention)

package/CONTRIBUTING.md

@@ -42,7 +42,7 @@ tribunal-kit/
 │   └── index.d.ts          # TypeScript declarations
 ├── crates/core/            # Rust core engine (Tokio-based)
 ├── .agent/                 # The intelligence payload (agents, skills, workflows)
-│   ├── agents/             # 43 specialist agent definitions
+│   ├── agents/             # 44 specialist and reviewer agent definitions
 │   ├── skills/             # Reusable skill packs
 │   ├── workflows/          # 34 workflow definitions
 │   └── scripts/            # Automation scripts

package/README.md

@@ -20,7 +20,7 @@
       <img src="https://img.shields.io/badge/License-MIT-1a1a1f?style=for-the-badge&color=2d2d30" alt="License" />
     </a>
     <a href="CHANGELOG.md">
-      <img src="https://img.shields.io/badge/Release-v5.8.4-ccff00?style=for-the-badge&color=111111&logo=github&logoColor=ccff00" alt="Release Version" />
+      <img src="https://img.shields.io/badge/Release-v5.8.5-ccff00?style=for-the-badge&color=111111&logo=github&logoColor=ccff00" alt="Release Version" />
     </a>
     <a href="mcp_config.json">
       <img src="https://img.shields.io/badge/MCP-Ready-00c2ff?style=for-the-badge&logo=openai&logoColor=111" alt="MCP Server" />
@@ -40,7 +40,7 @@
     <strong style="color: #ffffff; font-size: 1.1em;">AI GENERATES CODE. TRIBUNAL KIT GOVERNS IT.</strong>
   </div>
   <p style="color: #c9c9d1; font-size: 0.95em; line-height: 1.6; margin: 0;">
-    A zero-bloat <strong>.agent/</strong> intelligence payload and <strong>Model Context Protocol (MCP) server</strong> that upgrades your IDEs (<a href="#" style="color: #ccff00; text-decoration: none;">Cursor</a>, <a href="#" style="color: #ccff00; text-decoration: none;">VSCode</a>, <a href="#" style="color: #ccff00; text-decoration: none;">Windsurf</a>) and terminal AI coding assistants (<a href="#" style="color: #ccff00; text-decoration: none;">Claude Code</a>, <a href="#" style="color: #ccff00; text-decoration: none;">Aider</a>) with <strong>44 specialist agents</strong>, <strong>34 workflows</strong>, and a parallel <strong>20-reviewer Tribunal pipeline</strong>. Establishes absolute runtime correctness, optimizes context windows, and heavily mitigates AI code hallucinations.
+    A zero-bloat <strong>.agent/</strong> intelligence payload and <strong>Model Context Protocol (MCP) server</strong> that upgrades your IDEs (<a href="#" style="color: #ccff00; text-decoration: none;">Cursor</a>, <a href="#" style="color: #ccff00; text-decoration: none;">VSCode</a>, <a href="#" style="color: #ccff00; text-decoration: none;">Windsurf</a>) and terminal AI coding assistants (<a href="#" style="color: #ccff00; text-decoration: none;">Claude Code</a>, <a href="#" style="color: #ccff00; text-decoration: none;">Aider</a>) with <strong>44 specialist agents</strong>, <strong>34 workflows</strong>, and a parallel <strong>19-reviewer Tribunal pipeline</strong>. Establishes absolute runtime correctness, optimizes context windows, and heavily mitigates AI code hallucinations.
   </p>
 </div>
 
@@ -210,7 +210,7 @@ npx tribunal-kit status
 
 Code generation is solved. **Code correctness is the frontier.** 
 
-The Tribunal Pipeline intercepts raw agent generation and routes it through a parallel suite of **20 domain-specific reviewers** before presenting changes to the developer:
+The Tribunal Pipeline intercepts raw agent generation and routes it through a parallel suite of **19 domain-specific reviewers** before presenting changes to the developer:
 
 ```mermaid
 graph TD
@@ -221,7 +221,7 @@ graph TD
     C -.->|Failed| E[Maker Auto-Correction]
     E -.-> C
 
-    D -->|20 Domain Reviewers| F[Human Gate]
+    D -->|19 Domain Reviewers| F[Human Gate]
     F -->|Approved| G((Committed to Disk))
 
     classDef default fill:#1a1a1a,stroke:#333,stroke-width:2px,color:#fff;