tribunal-kit 9.2.4 → 9.2.6

package/.agents/skills/progressive-blur/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: progressive-blur
-description: "Use when Smooth progressive backdrop blurs, depth overlays, and modern glassmorphism using CSS mask-image and multi-layered backdrop filters without GPU performance drops."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when implementing, optimizing, and timing 60fps/120fps progressive blur animations, transitions, gesture physics, and reduced-motion fallbacks."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - 60fps-animation
   - better-colors
@@ -15,66 +15,136 @@ scripts-binding:
 
 # Progressive Blur — Multi-Layered Glassmorphism & Depth
 
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `progressive-blur` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-## 🛠️ Technical Architecture & Reference Recipes
 
----
+## Activation Boundaries
+- **Activate when:** Use when implementing, optimizing, and timing 60fps/120fps progressive blur animations, transitions, gesture physics, and reduced-motion fallbacks.
+- **DO NOT activate when:** The task falls outside the `progressive-blur` domain or is managed by a different dedicated specialist agent.
 
----
 
-## 3 Progressive Blur Techniques
+## 🔁 Multi-Pass Execution Protocol
 
-### 1. Multi-Step Masked Progressive Blur
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
-To prevent harsh edge cutoffs in blurred headers or footers, blend 4 progressive blur layers using linear gradient masks:
 
-```css
-.progressive-blur-header {
-  position: sticky;
-  top: 0;
-  z-index: 40;
-  pointer-events: none;
-}
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
-.blur-layer-1 {
-  backdrop-filter: blur(2px);
-  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 0%, rgba(0, 0, 0, 0) 25%);
-}
+---
+
+## 3 Progressive Blur Techniques
+
+### 1. Multi-Step Masked Progressive Blur
+
+To prevent harsh edge cutoffs in blurred headers or footers, blend 4 progressive blur layers using linear gradient masks:
+
+```css
+.progressive-blur-header {
+  position: sticky;
+  top: 0;
+  z-index: 40;
+  pointer-events: none;
+}
+
+.blur-layer-1 {
+  backdrop-filter: blur(2px);
+  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 0%, rgba(0, 0, 0, 0) 25%);
+}
+
+.blur-layer-2 {
+  backdrop-filter: blur(8px);
+  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 25%, rgba(0, 0, 0, 0) 65%);
+}
+
+.blur-layer-3 {
+  backdrop-filter: blur(16px);
+  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 65%, rgba(0, 0, 0, 1) 100%);
+}
+```
+
+### 2. Glass Card Depth Recipe
+
+```css
+.glass-card {
+  background: rgba(255, 255, 255, 0.65);
+  backdrop-filter: blur(16px) saturate(180%);
+  -webkit-backdrop-filter: blur(16px) saturate(180%);
+  border: 1px solid rgba(255, 255, 255, 0.3);
+  box-shadow: 0 8px 32px 0 rgba(0, 0, 0, 0.08);
+}
+
+@media (prefers-color-scheme: dark) {
+  .glass-card {
+    background: rgba(18, 18, 20, 0.7);
+    border: 1px solid rgba(255, 255, 255, 0.08);
+    box-shadow: 0 8px 32px 0 rgba(0, 0, 0, 0.37);
+  }
+}
+```
+
+### 3. GPU Hardware Acceleration Protection
+
+Backdrop blurs can cause frame drops if animated directly.
+
+- **Rule**: Never animate `backdrop-filter: blur()` properties during scroll or transitions. Animate `opacity` of a static blurred pseudo-element instead!
 
-.blur-layer-2 {
-  backdrop-filter: blur(8px);
-  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 25%, rgba(0, 0, 0, 0) 65%);
-}
+## 🚨 Edge-Case & Failure Mode Matrix
 
-.blur-layer-3 {
-  backdrop-filter: blur(16px);
-  mask: linear-gradient(to bottom, rgba(0, 0, 0, 1) 65%, rgba(0, 0, 0, 1) 100%);
-}
-```
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-### 2. Glass Card Depth Recipe
-
-```css
-.glass-card {
-  background: rgba(255, 255, 255, 0.65);
-  backdrop-filter: blur(16px) saturate(180%);
-  -webkit-backdrop-filter: blur(16px) saturate(180%);
-  border: 1px solid rgba(255, 255, 255, 0.3);
-  box-shadow: 0 8px 32px 0 rgba(0, 0, 0, 0.08);
-}
-
-@media (prefers-color-scheme: dark) {
-  .glass-card {
-    background: rgba(18, 18, 20, 0.7);
-    border: 1px solid rgba(255, 255, 255, 0.08);
-    box-shadow: 0 8px 32px 0 rgba(0, 0, 0, 0.37);
-  }
-}
-```
 
-### 3. GPU Hardware Acceleration Protection
+## 🤖 LLM-Specific Traps Table
 
-Backdrop blurs can cause frame drops if animated directly.
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **The Instant Pop Trap** | Conditionally unmounting elements without animated interpolation | Use AnimatePresence or coordinate morphs with continuous geometry |
+| **Layout Thrashing** | Animating width, height, top, or left inside animation loops | Animate composite-only transform (translate3d, scale) and opacity |
+| **Sluggish Duration** | Setting micro-interaction transitions to 600ms+ causing interface lag | Cap interactive feedback at 160ms–240ms with snappy ease-out curves |
 
-- **Rule**: Never animate `backdrop-filter: blur()` properties during scroll or transitions. Animate `opacity` of a static blurred pseudo-element instead!
+
+## 🏛️ Tribunal Verification & Guardrails
+
+**Active Reviewers:** `frontend-reviewer` · `motion-reviewer` · `ui-ux-auditor`
+**Slash Command:** `/review` or `/tribunal-full`
+
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
+
+### ✅ Pre-Flight Self-Audit Checklist
+```
+✅ Does animation maintain 60fps/120fps using transform (translate3d, scale) and opacity?
+✅ Is optical mass conserved across state interpolations without volume collapse?
+✅ Is duration capped within micro-interaction budgets (150ms–280ms)?
+✅ Is prefers-reduced-motion respected with graceful instant fallbacks?
+✅ Did I prevent layout thrashing and continuous geometry mutations?
+```
+
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/project-idioms/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: project-idioms
-description: "Use when >"
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when executing, coordinating, planning, or reviewing project idioms agent workflows, cognitive loops, and architecture standards."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - clean-code
   - codebase-design
@@ -16,76 +16,146 @@ scripts-binding:
 
 # Project Idioms — Auto-Evolved Skill
 
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `project-idioms` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
 
-## 🛠️ Technical Architecture & Reference Recipes
 
----
+## Activation Boundaries
+- **Activate when:** Use when executing, coordinating, planning, or reviewing project idioms agent workflows, cognitive loops, and architecture standards.
+- **DO NOT activate when:** The task falls outside the `project-idioms` domain or is managed by a different dedicated specialist agent.
 
----
 
-> **Authority Level: ABSOLUTE**
-> These idioms were extracted from this project's actual code decisions.
-> They override all generic agent defaults and best practices.
-> Every agent reads this file on activation and adapts its proposals accordingly.
+## 🔁 Multi-Pass Execution Protocol
 
----
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
 
-## How Idioms Are Born
 
-1. Developer commits code that **differs** from what the AI proposed.
-2. `skill_evolution.js digest` extracts the architectural delta (semantic filter).
-3. A minimal LLM prompt (< 500 tokens) identifies the **WHY** behind the change.
-4. The idiom is recorded here with a stable pattern + reason pair.
-5. All future code generations must align with these idioms.
-
----
-
-## Recorded Idioms
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
-| ID  | Pattern | Why This Project Uses It                               | Domain | Since |
-| :-- | :------ | :----------------------------------------------------- | :----- | :---- |
-| —   | —       | _No idioms recorded yet. Run your first digest cycle._ | —      | —     |
+---
+
+> **Authority Level: ABSOLUTE**
+> These idioms were extracted from this project's actual code decisions.
+> They override all generic agent defaults and best practices.
+> Every agent reads this file on activation and adapts its proposals accordingly.
+
+---
+
+## How Idioms Are Born
+
+1. Developer commits code that **differs** from what the AI proposed.
+2. `skill_evolution.js digest` extracts the architectural delta (semantic filter).
+3. A minimal LLM prompt (< 500 tokens) identifies the **WHY** behind the change.
+4. The idiom is recorded here with a stable pattern + reason pair.
+5. All future code generations must align with these idioms.
+
+---
+
+## Recorded Idioms
+
+| ID  | Pattern | Why This Project Uses It                               | Domain | Since |
+| :-- | :------ | :----------------------------------------------------- | :----- | :---- |
+| —   | —       | _No idioms recorded yet. Run your first digest cycle._ | —      | —     |
+
+---
+
+## How to Add New Idioms
+
+Run after committing or staging a meaningful architectural change:
+
+```bash
+# Analyze staged changes (default)
+node .agent/scripts/skill_evolution.js digest
+
+# Preview without writing
+node .agent/scripts/skill_evolution.js digest --dry-run
+
+# Analyze last commit instead of staged
+node .agent/scripts/skill_evolution.js digest --head
+
+# Check current idiom count and token savings
+node .agent/scripts/skill_evolution.js status
+```
+
+---
+
+## Enforcement Rules for All Agents
+
+```
+□ Before proposing any code: scan the idiom table above
+□ If your proposal contradicts an idiom → flag it explicitly with:
+     "⚠️ Note: My proposal differs from Project Idiom #N. Reason: [explain]"
+□ Never override an idiom silently
+□ When citing an idiom in a review:
+     "Per Project Idiom #N: [pattern] — [reason]"
+□ If no idioms yet → proceed with domain-standard approaches
+```
+
+---
+
+## Digest History
+
+Last digest: `never`
+Total cycles: `0`
+
+Run `node .agent/scripts/skill_evolution.js status` to see full statistics.
 
----
+## 🚨 Edge-Case & Failure Mode Matrix
 
-## How to Add New Idioms
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
 
-Run after committing or staging a meaningful architectural change:
 
-```bash
-# Analyze staged changes (default)
-node .agent/scripts/skill_evolution.js digest
+## 🤖 LLM-Specific Traps Table
 
-# Preview without writing
-node .agent/scripts/skill_evolution.js digest --dry-run
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **Hallucinated Tool Capabilities** | Assuming an external library or CLI command exists without verification | Run a verification check or verify package.json before referencing tools |
+| **Premature Completion Claim** | Declaring a task finished because code was generated without verification | Execute tests, linters, or terminal commands to provide concrete proof |
+| **Context Bloat Dumping** | Pasting entire multi-thousand-line files into prompt context | Extract targeted excerpts, symbols, and signatures to preserve tokens |
 
-# Analyze last commit instead of staged
-node .agent/scripts/skill_evolution.js digest --head
 
-# Check current idiom count and token savings
-node .agent/scripts/skill_evolution.js status
-```
+## 🏛️ Tribunal Verification & Guardrails
 
----
+**Active Reviewers:** `orchestrator` · `agent-organizer` · `logic-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-## Enforcement Rules for All Agents
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
 
+### ✅ Pre-Flight Self-Audit Checklist
 ```
-□ Before proposing any code: scan the idiom table above
-□ If your proposal contradicts an idiom → flag it explicitly with:
-     "⚠️ Note: My proposal differs from Project Idiom #N. Reason: [explain]"
-□ Never override an idiom silently
-□ When citing an idiom in a review:
-     "Per Project Idiom #N: [pattern] — [reason]"
-□ If no idioms yet → proceed with domain-standard approaches
+✅ Did I deconstruct the root objective before proposing architecture?
+✅ Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
+✅ Did I avoid over-engineering and select the simplest effective pattern?
+✅ Did I verify assumptions with concrete file reads instead of speculation?
+✅ Did I establish measurable verification criteria before completion?
 ```
 
----
-
-## Digest History
-
-Last digest: `never`
-Total cycles: `0`
-
-Run `node .agent/scripts/skill_evolution.js status` to see full statistics.
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/property-based-testing/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: property-based-testing
-description: "Use when Generative input invariant testing using fast-check (TS/JS) and hypothesis (Python) to uncover hidden edge cases and boundary failures."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when writing, maintaining, executing, and auditing property based testing test suites, assertions, mocks, and verification gates."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - testing-patterns
   - tdd-workflow
@@ -17,34 +17,106 @@ scripts-binding:
 
 # Property-Based Testing — Invariant Verification
 
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `property-based-testing` domain, inspect these 5 critical parameters:
+1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
+2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
+3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
+4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
+5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
+
+
+## Activation Boundaries
+- **Activate when:** Use when writing, maintaining, executing, and auditing property based testing test suites, assertions, mocks, and verification gates.
+- **DO NOT activate when:** The task falls outside the `property-based-testing` domain or is managed by a different dedicated specialist agent.
+
+
+## 🔁 Multi-Pass Execution Protocol
+
+| Pass | Phase | Core Action | Adaptive Depth |
+|:---|:---|:---|:---|
+| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep |
+| **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep |
+| **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes |
+| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes |
+| **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep |
+| **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep |
+| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes |
+
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+## Fast-Check Arbitrary Generator & Vitest Invariant Test
+
+```typescript
+import fc from 'fast-check';
+import { test, expect } from 'vitest';
+
+function parseAmount(currencyStr: string): number | null {
+  const cleaned = currencyStr.replace(/[^0-9.]/g, '');
+  const num = parseFloat(cleaned);
+  return isNaN(num) ? null : num;
+}
+
+test('currency parser invariant: non-negative parsed numbers', () => {
+  fc.assert(
+    fc.property(fc.tuple(fc.string(), fc.double({ min: 0, max: 1000000 })), ([prefix, val]) => {
+      const input = `${prefix}$${val.toFixed(2)}`;
+      const parsed = parseAmount(input);
+
+      if (parsed !== null) {
+        expect(parsed).toBeGreaterThanOrEqual(0);
+        expect(Number.isFinite(parsed)).toBe(true);
+      }
+    }),
+    { numRuns: 500 }, // Execute 500 generative iterations
+  );
+});
+```
+
+## 🚨 Edge-Case & Failure Mode Matrix
 
-## 🛠️ Technical Architecture & Reference Recipes
-
-## Fast-Check Arbitrary Generator & Vitest Invariant Test
-
-```typescript
-import fc from 'fast-check';
-import { test, expect } from 'vitest';
-
-function parseAmount(currencyStr: string): number | null {
-  const cleaned = currencyStr.replace(/[^0-9.]/g, '');
-  const num = parseFloat(cleaned);
-  return isNaN(num) ? null : num;
-}
-
-test('currency parser invariant: non-negative parsed numbers', () => {
-  fc.assert(
-    fc.property(fc.tuple(fc.string(), fc.double({ min: 0, max: 1000000 })), ([prefix, val]) => {
-      const input = `${prefix}$${val.toFixed(2)}`;
-      const parsed = parseAmount(input);
-
-      if (parsed !== null) {
-        expect(parsed).toBeGreaterThanOrEqual(0);
-        expect(Number.isFinite(parsed)).toBe(true);
-      }
-    }),
-    { numRuns: 500 }, // Execute 500 generative iterations
-  );
-});
+| Scenario | Risk | Production Mitigation |
+|:---|:---|:---|
+| **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+| **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+| **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+| **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+| **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
+
+
+## 🤖 LLM-Specific Traps Table
+
+| Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+|:---|:---|:---|
+| **Testing Implementation Details** | Asserting on private component state or internal helper functions | Assert on observable user behaviors, DOM roles, and network outcomes |
+| **Flaky Async Assertion** | Using arbitrary setTimeout delays before asserting on asynchronous state | Use waitFor or condition-based queries that poll with timeout bounds |
+| **Shared Mutable State** | Reusing database records across concurrent test runners | Isolate test databases per worker or execute in rolled-back transactions |
+
+
+## 🏛️ Tribunal Verification & Guardrails
+
+**Active Reviewers:** `test-engineer` · `qa-automation-engineer` · `logic-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
+
+### 🔬 Evidence Standard (Tri-State Verification)
+Every finding, audit statement, or completion claim must classify its factual certainty:
+- **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command.
+- **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations.
+- **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement.
+
+### ✅ Pre-Flight Self-Audit Checklist
 ```
+✅ Do tests follow behavioral GIVEN/WHEN/THEN specifications?
+✅ Are happy path, failure paths, and boundary conditions (0, null, max, unicode) covered?
+✅ Are test mocks isolated and reset between successive test cases?
+✅ Do E2E locators rely on stable ARIA attributes instead of brittle CSS selectors?
+✅ Did I verify test suite passes deterministically without flaky race conditions?
+```
+
+### 🛑 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 test suites, compiler success, or equivalent operational proof) that your output works as intended.