tribunal-kit 6.0.0 → 7.0.0

package/.agent/skills/knowledge-graph/SKILL.md

@@ -21,6 +21,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before inspecting codebase architecture, you MUST inspect:
+
 1. Context Snapshots (`.agent/history/snapshots/`) → Read pre-computed JSON snapshots to reduce token overhead by 27x
 2. `graph_builder.js` output → Check downstream dependencies, risk scores, and blast radius before modifying any file
 3. Module boundaries → Identify top imported symbols and high-risk core modules

package/.agent/skills/landing-page/SKILL.md

@@ -21,6 +21,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering full landing pages, you MUST inspect:
+
 1. Hero Layout Model (Section 50) → Choose appropriate layout variance model (Model A Centered Stacked, Model B Asymmetric Split, Model C Full-Bleed Canvas)
 2. CTA Hierarchy (Section 32) → Ensure exactly ONE primary solid accent button above the fold; pair only with a secondary ghost button
 3. Blueprint Rhythm (Section 22) → Follow the 6-section blueprint (Nav, Hero, Social Proof, Features, Testimonials, Final CTA)

package/.agent/skills/lint-and-validate/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before running linting tools or modifying linter rules, you MUST inspect:
+
 1. Zero-Warning CI Blocking (Section 34) → Enforce zero-warning policy in CI pipelines; ban treating lint warnings as non-blocking
 2. Mandatory Strict Type Checks (Section 121) → Run static type checking (`tsc --noEmit` or `mypy`) alongside linters to catch non-linter type bugs
 3. Diff Review Before Auto-Fixing (Section 15) → Review diffs explicitly after auto-fixing (`eslint --fix`) to prevent accidental removal of side-effect code
@@ -69,7 +70,11 @@ npx prettier --write .
 ```json
 // .eslintrc.json
 {
-  "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended", "plugin:@typescript-eslint/recommended-requiring-type-checking"],
+  "extends": [
+    "eslint:recommended",
+    "plugin:@typescript-eslint/recommended",
+    "plugin:@typescript-eslint/recommended-requiring-type-checking"
+  ],
   "rules": {
     "@typescript-eslint/no-explicit-any": "error",
     "@typescript-eslint/no-floating-promises": "error",
@@ -197,9 +202,9 @@ repos:
 
 ## Scripts
 
-| Script                     | Purpose                                   | Run With                                         |
-| -------------------------- | ----------------------------------------- | ------------------------------------------------ |
-| `.agent/scripts/lint_runner.js`   | Runs project linting and reports findings | `node .agent/scripts/lint_runner.js <project_path>`   |
+| Script                          | Purpose                                   | Run With                                            |
+| ------------------------------- | ----------------------------------------- | --------------------------------------------------- |
+| `.agent/scripts/lint_runner.js` | Runs project linting and reports findings | `node .agent/scripts/lint_runner.js <project_path>` |
 
 ---
 

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

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering LLM integrations or tool calling loops, you MUST inspect:
+
 1. Zod Schema Validation on JSON Outputs (Section 115) → Always run Zod validation (`Schema.parse(...)`) on LLM JSON responses, even in strict mode
 2. Hybrid Vector + Keyword Search (Section 290) → Use hybrid vector + BM25 keyword search in RAG applications to prevent missing exact identifiers
 3. System Prompt Secret Isolation (Section 69) → Never put private API keys, database credentials, or secret internal URLs into system prompts
@@ -76,7 +77,7 @@ const SYSTEM_PROMPT = `You are a customer support agent for Acme Corp.
 - End with a follow-up question
 
 ## Context
-Current date: ${new Date().toISOString().split("T")[0]}
+Current date: ${new Date().toISOString().split('T')[0]}
 User plan: {{user_plan}}
 `;
 
@@ -88,11 +89,11 @@ User plan: {{user_plan}}
 ### Structured Output (JSON Mode)
 
 ```typescript
-import { z } from "zod";
-import OpenAI from "openai";
+import { z } from 'zod';
+import OpenAI from 'openai';
 
 const SentimentSchema = z.object({
-  sentiment: z.enum(["positive", "negative", "neutral"]),
+  sentiment: z.enum(['positive', 'negative', 'neutral']),
   confidence: z.number().min(0).max(1),
   reasoning: z.string(),
   topics: z.array(z.string()),
@@ -101,49 +102,49 @@ const SentimentSchema = z.object({
 // OpenAI — json_schema mode (strict = true enforces schema exactly)
 async function analyzeSentiment(text: string) {
   const response = await openai.chat.completions.create({
-    model: "gpt-4o-mini",
+    model: 'gpt-4o-mini',
     response_format: {
-      type: "json_schema",
+      type: 'json_schema',
       json_schema: {
-        name: "sentiment_analysis",
+        name: 'sentiment_analysis',
         strict: true,
         schema: {
-          type: "object",
+          type: 'object',
           properties: {
-            sentiment: { type: "string", enum: ["positive", "negative", "neutral"] },
-            confidence: { type: "number" },
-            reasoning: { type: "string" },
-            topics: { type: "array", items: { type: "string" } },
+            sentiment: { type: 'string', enum: ['positive', 'negative', 'neutral'] },
+            confidence: { type: 'number' },
+            reasoning: { type: 'string' },
+            topics: { type: 'array', items: { type: 'string' } },
           },
-          required: ["sentiment", "confidence", "reasoning", "topics"],
+          required: ['sentiment', 'confidence', 'reasoning', 'topics'],
           additionalProperties: false, // required for strict mode
         },
       },
     },
     messages: [
-      { role: "system", content: "Analyze sentiment." },
-      { role: "user", content: text },
+      { role: 'system', content: 'Analyze sentiment.' },
+      { role: 'user', content: text },
     ],
   });
-  const raw = JSON.parse(response.choices[0].message.content ?? "{}");
+  const raw = JSON.parse(response.choices[0].message.content ?? '{}');
   return SentimentSchema.parse(raw); // always validate with Zod even in strict mode
 }
 
 // Gemini — response_mime_type + response_schema
-import { GoogleGenerativeAI, SchemaType } from "@google/generative-ai";
+import { GoogleGenerativeAI, SchemaType } from '@google/generative-ai';
 const genAI = new GoogleGenerativeAI(process.env.GEMINI_API_KEY!);
 const model = genAI.getGenerativeModel({
-  model: "gemini-2.0-flash",
+  model: 'gemini-2.0-flash',
   generationConfig: {
-    responseMimeType: "application/json",
+    responseMimeType: 'application/json',
     responseSchema: {
       type: SchemaType.OBJECT,
       properties: {
-        sentiment: { type: SchemaType.STRING, enum: ["positive", "negative", "neutral"] },
+        sentiment: { type: SchemaType.STRING, enum: ['positive', 'negative', 'neutral'] },
         confidence: { type: SchemaType.NUMBER },
         topics: { type: SchemaType.ARRAY, items: { type: SchemaType.STRING } },
       },
-      required: ["sentiment", "confidence", "topics"],
+      required: ['sentiment', 'confidence', 'topics'],
     },
   },
 });
@@ -159,32 +160,32 @@ const model = genAI.getGenerativeModel({
 ```typescript
 const tools: OpenAI.ChatCompletionTool[] = [
   {
-    type: "function",
+    type: 'function',
     function: {
-      name: "search_products",
-      description: "Search products by name, category, or price range",
+      name: 'search_products',
+      description: 'Search products by name, category, or price range',
       parameters: {
-        type: "object",
+        type: 'object',
         properties: {
-          query: { type: "string", description: "Search query" },
-          category: { type: "string", enum: ["electronics", "clothing", "home"] },
-          max_price: { type: "number", description: "Maximum price in USD" },
+          query: { type: 'string', description: 'Search query' },
+          category: { type: 'string', enum: ['electronics', 'clothing', 'home'] },
+          max_price: { type: 'number', description: 'Maximum price in USD' },
         },
-        required: ["query"],
+        required: ['query'],
       },
     },
   },
   {
-    type: "function",
+    type: 'function',
     function: {
-      name: "get_order_status",
-      description: "Get the status of an order by order ID",
+      name: 'get_order_status',
+      description: 'Get the status of an order by order ID',
       parameters: {
-        type: "object",
+        type: 'object',
         properties: {
-          order_id: { type: "string", description: "The order ID (e.g., ORD-12345)" },
+          order_id: { type: 'string', description: 'The order ID (e.g., ORD-12345)' },
         },
-        required: ["order_id"],
+        required: ['order_id'],
       },
     },
   },
@@ -193,18 +194,18 @@ const tools: OpenAI.ChatCompletionTool[] = [
 // Tool execution loop
 async function chatWithTools(userMessage: string) {
   const messages: OpenAI.ChatCompletionMessageParam[] = [
-    { role: "system", content: SYSTEM_PROMPT },
-    { role: "user", content: userMessage },
+    { role: 'system', content: SYSTEM_PROMPT },
+    { role: 'user', content: userMessage },
   ];
 
   let response = await openai.chat.completions.create({
-    model: "gpt-4o-mini",
+    model: 'gpt-4o-mini',
     messages,
     tools,
   });
 
   // Process tool calls
-  while (response.choices[0].finish_reason === "tool_calls") {
+  while (response.choices[0].finish_reason === 'tool_calls') {
     const toolCalls = response.choices[0].message.tool_calls ?? [];
     messages.push(response.choices[0].message);
 
@@ -212,14 +213,14 @@ async function chatWithTools(userMessage: string) {
       const args = JSON.parse(call.function.arguments);
       const result = await executeFunction(call.function.name, args);
       messages.push({
-        role: "tool",
+        role: 'tool',
         tool_call_id: call.id,
         content: JSON.stringify(result),
       });
     }
 
     response = await openai.chat.completions.create({
-      model: "gpt-4o-mini",
+      model: 'gpt-4o-mini',
       messages,
       tools,
     });
@@ -262,19 +263,19 @@ function chunkDocument(text: string, options: ChunkOptions = {}): Chunk[] {
   const {
     maxTokens = 512, // chunk size
     overlapTokens = 50, // overlap between chunks
-    separator = "\n\n", // split on paragraph boundaries first
+    separator = '\n\n', // split on paragraph boundaries first
   } = options;
 
   const paragraphs = text.split(separator);
   const chunks: Chunk[] = [];
-  let current = "";
+  let current = '';
 
   for (const para of paragraphs) {
     if (tokenCount(current + para) > maxTokens && current) {
       chunks.push({ text: current.trim(), tokens: tokenCount(current) });
       // Keep overlap from previous chunk
-      const words = current.split(" ");
-      current = words.slice(-overlapTokens).join(" ") + separator + para;
+      const words = current.split(' ');
+      current = words.slice(-overlapTokens).join(' ') + separator + para;
     } else {
       current += separator + para;
     }
@@ -311,14 +312,14 @@ Milvus                 → Enterprise scale, GPU acceleration
 
 ```typescript
 // Server-Sent Events for AI token streaming
-app.get("/api/chat", async (req, res) => {
-  res.setHeader("Content-Type", "text/event-stream");
-  res.setHeader("Cache-Control", "no-cache");
-  res.setHeader("Connection", "keep-alive");
+app.get('/api/chat', async (req, res) => {
+  res.setHeader('Content-Type', 'text/event-stream');
+  res.setHeader('Cache-Control', 'no-cache');
+  res.setHeader('Connection', 'keep-alive');
 
   const stream = await openai.chat.completions.create({
-    model: "gpt-4o-mini",
-    messages: [{ role: "user", content: req.query.message as string }],
+    model: 'gpt-4o-mini',
+    messages: [{ role: 'user', content: req.query.message as string }],
     stream: true,
   });
 
@@ -329,14 +330,14 @@ app.get("/api/chat", async (req, res) => {
     }
   }
 
-  res.write("data: [DONE]\n\n");
+  res.write('data: [DONE]\n\n');
   res.end();
 });
 
 // Client-side consumption
 const eventSource = new EventSource(`/api/chat?message=${encodeURIComponent(msg)}`);
-eventSource.onmessage = (event) => {
-  if (event.data === "[DONE]") {
+eventSource.onmessage = event => {
+  if (event.data === '[DONE]') {
     eventSource.close();
     return;
   }

package/.agent/skills/local-first/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing local-first storage or CRDT synchronization, you MUST inspect:
+
 1. Conflict Resolution Strategy (Section 15) → Define explicit conflict resolution (LWW timestamps or Yjs CRDTs) before writing local sync logic
 2. Persistent Storage (Section 16) → Use IndexedDB (via Dexie/idb) or SQLite WASM for local persistence; ban localStorage for >5MB data
 3. Incremental Watermark Sync (Section 17) → Perform delta syncs using timestamps/watermarks rather than re-fetching full datasets
@@ -55,20 +56,20 @@ Do not use React Query / SWR to build local-first. They are HTTP caching mechani
 // ❌ CLOUD-FIRST (React Query / Fetch)
 // Fails when offline. Subject to UI latency.
 const { data, isLoading } = useQuery({
-  queryKey: ["todos"],
-  queryFn: () => fetch("/api/todos").then((res) => res.json()),
+  queryKey: ['todos'],
+  queryFn: () => fetch('/api/todos').then(res => res.json()),
 });
 
 // ✅ LOCAL-FIRST (e.g. PowerSync / ElectricSQL / WatermelonDB)
 // Resolves instantly. Data lives locally. Syncs silently in background.
-import { useQuery } from "@powersync/react";
+import { useQuery } from '@powersync/react';
 
-const { data, isLoading } = useQuery("SELECT * FROM todos ORDER BY created_at DESC");
+const { data, isLoading } = useQuery('SELECT * FROM todos ORDER BY created_at DESC');
 
 // Writes are also local First
 const addTodo = async (text: string) => {
   // Written to the local SQLite WASM database instantly.
-  await localDb.execute("INSERT INTO todos (id, text) VALUES (uuid(), ?)", [text]);
+  await localDb.execute('INSERT INTO todos (id, text) VALUES (uuid(), ?)', [text]);
   // Background worker syncs to Postgres later.
 };
 ```
@@ -83,22 +84,22 @@ When two users edit the exact same document offline and then reconnect, how is i
 
 ```typescript
 // Yjs - The leading CRDT library for collaborative text/state
-import * as Y from "yjs";
-import { WebsocketProvider } from "y-websocket";
+import * as Y from 'yjs';
+import { WebsocketProvider } from 'y-websocket';
 
 const ydoc = new Y.Doc();
-const provider = new WebsocketProvider("wss://sync.example.com", "room-1", ydoc);
+const provider = new WebsocketProvider('wss://sync.example.com', 'room-1', ydoc);
 
 // Shared state array
-const yarray = ydoc.getArray("todos");
+const yarray = ydoc.getArray('todos');
 
 // Observe changes (Fires locally and when peers sync)
-yarray.observe((event) => {
-  console.log("State updated natively without conflict:", yarray.toArray());
+yarray.observe(event => {
+  console.log('State updated natively without conflict:', yarray.toArray());
 });
 
 // Insert data (Instantly merges cleanly with remote peers)
-yarray.insert(0, ["Buy milk"]);
+yarray.insert(0, ['Buy milk']);
 ```
 
 ---
@@ -117,7 +118,7 @@ Storing megabytes of relational data in `localStorage` will crash the browser.
 
 ```typescript
 // Clean IndexedDB Wrapper Example (Dexie)
-import Dexie, { type EntityTable } from "dexie";
+import Dexie, { type EntityTable } from 'dexie';
 
 interface Friend {
   id: number;
@@ -125,21 +126,21 @@ interface Friend {
   age: number;
 }
 
-const db = new Dexie("FriendsDatabase") as Dexie & {
-  friends: EntityTable<Friend, "id">;
+const db = new Dexie('FriendsDatabase') as Dexie & {
+  friends: EntityTable<Friend, 'id'>;
 };
 
 // Schema configuration
 db.version(1).stores({
-  friends: "++id, name, age", // Primary key and indexed props
+  friends: '++id, name, age', // Primary key and indexed props
 });
 
 // Write to DB instantly
-await db.friends.add({ name: "Alice", age: 25 });
+await db.friends.add({ name: 'Alice', age: 25 });
 
 // Live query natively drives React state without network calls
-import { useLiveQuery } from "dexie-react-hooks";
-const friends = useLiveQuery(() => db.friends.where("age").above(21).toArray());
+import { useLiveQuery } from 'dexie-react-hooks';
+const friends = useLiveQuery(() => db.friends.where('age').above(21).toArray());
 ```
 
 ---

package/.agent/skills/local-first-architecture/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing local-first architecture or offline sync engines, you MUST inspect:
+
 1. Zero Network Latency Rule (Section 24) → Execute reads and writes against local storage (IndexedDB/SQLite) first before queueing outbound sync
 2. Outbound Mutation Queue (Section 28) → Persist mutation logs in IndexedDB with client-generated UUID `idempotencyKey` fields
 3. Conflict Resolution Strategy (Section 33) → Use Last-Write-Wins (LWW) for simple fields or CRDTs (Yjs/Automerge) for collaborative state
@@ -31,19 +32,23 @@ Architect software that reads and writes to local storage (SQLite/IndexedDB) fir
 ## 4 Pillars of Local-First Architecture
 
 ### 1. Read & Write Local First
+
 - **Zero Network Latency**: UI queries (`select * from tasks`) run synchronously or near-instantaneously against in-memory or IndexedDB caches.
-- Mutations update the local cache immediately (*optimistic write*), appending a mutation log item to an outbound sync queue.
+- Mutations update the local cache immediately (_optimistic write_), appending a mutation log item to an outbound sync queue.
 
 ### 2. Outbound Mutation Queue & Idempotency
+
 - Store mutation logs in a persistent local queue (`IndexedDB` / `SQLite`).
 - Assign every client mutation a unique UUID (`idempotencyKey`).
 - When network connection is restored, flush queue items sequentially with automatic retry on 5xx failures.
 
 ### 3. Conflict Resolution (CRDTs & LWW)
+
 - **Last-Write-Wins (LWW)**: Timestamp + Client ID ordering for simple fields.
 - **CRDTs (Yjs / Automerge)**: Conflict-free Replicated Data Types for collaborative text editing and array state.
 
 ### 4. Background Delta Streaming
+
 - Receive database updates via WebSockets or Server-Sent Events (SSE) as thin binary deltas (`sync_version > client_version`), applying changes to local storage without re-fetching full datasets.
 
 ---

package/.agent/skills/lottie-animation/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before integrating Lottie animations, you MUST inspect:
+
 1. Asset Format (.lottie vs .json) → Prefer compressed `.lottie` (dotLottie) assets for 80% smaller bundle file sizes
 2. Playback Triggers (Section 34) → Bind playback to user hover/click or viewport intersection instead of aggressive continuous looping
 3. Package Manifest (`package.json`) → Verify `@dotlottie/react-player` or `lottie-web` library dependencies
@@ -31,10 +32,11 @@ Integrate lightweight, vector-based Lottie animations with interactive trigger c
 ## 3 Lottie Integration Recipes
 
 ### 1. React dotLottie Interactive Player (`@dotlottie/react-player`)
+
 ```tsx
-import React, { useRef } from "react";
-import { DotLottiePlayer, Controls } from "@dotlottie/react-player";
-import "@dotlottie/react-player/dist/index.css";
+import React, { useRef } from 'react';
+import { DotLottiePlayer, Controls } from '@dotlottie/react-player';
+import '@dotlottie/react-player/dist/index.css';
 
 export function InteractiveLottieIcon() {
   const lottieRef = useRef<any>(null);
@@ -57,9 +59,11 @@ export function InteractiveLottieIcon() {
 ```
 
 ### 2. Runtime Color Injection / Theming
+
 Pass custom CSS variable overrides to dotLottie players to dynamically recolor vector paths at runtime without re-downloading JSON assets.
 
 ### 3. Performance & Lazy Loading
+
 - Use `.lottie` (dotLottie format) instead of uncompressed `.json` Lottie files to achieve **80% smaller bundle file sizes**.
 - Lazy-load offscreen Lottie animations using `IntersectionObserver`.
 

package/.agent/skills/marquee-loop/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing marquee loop tracks, you MUST inspect:
+
 1. DOM Structure (Section 24) → Duplicate item tracks MUST be rendered with `aria-hidden="true"` to prevent screen reader redundancy
 2. Hover Accessibility (Section 50) → Enforce `animation-play-state: paused` on `:hover` and `:focus-within`
 3. Reduced Motion Fallback (Section 61) → Collapse marquee into static wrapped flex grid when `prefers-reduced-motion: reduce` is active

package/.agent/skills/masked-reveal/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing clip-path or SVG mask reveals, you MUST inspect:
+
 1. Target DOM elements → Enforce `overflow: hidden` on text line wrappers to prevent unmasked overflow artifacts
 2. `clip-path: inset()` syntax (Section 26) → Prefer CSS `clip-path` over heavy SVG masks for linear curtain wipes
 3. Transition Easing → Use custom ease-out curves (`cubic-bezier(0.16, 1, 0.3, 1)`) for smooth deceleration
@@ -31,10 +32,15 @@ Create editorial, high-end visual reveals using CSS `clip-path` and SVG masks.
 ## 3 Masked Reveal Patterns
 
 ### 1. CSS `clip-path` Curtain Reveal
+
 ```css
 @keyframes curtain-reveal {
-  from { clip-path: inset(0 100% 0 0); }
-  to { clip-path: inset(0 0 0 0); }
+  from {
+    clip-path: inset(0 100% 0 0);
+  }
+  to {
+    clip-path: inset(0 0 0 0);
+  }
 }
 
 .reveal-image-curtain {
@@ -43,10 +49,15 @@ Create editorial, high-end visual reveals using CSS `clip-path` and SVG masks.
 ```
 
 ### 2. Radial Spotlight Clip Reveal
+
 ```css
 @keyframes circle-expand {
-  from { clip-path: circle(0% at 50% 50%); }
-  to { clip-path: circle(150% at 50% 50%); }
+  from {
+    clip-path: circle(0% at 50% 50%);
+  }
+  to {
+    clip-path: circle(150% at 50% 50%);
+  }
 }
 
 .spotlight-reveal {
@@ -55,7 +66,9 @@ Create editorial, high-end visual reveals using CSS `clip-path` and SVG masks.
 ```
 
 ### 3. Masked Text Line Wipe (Editorial Typography)
+
 Wrap text lines inside overflow-hidden wrappers and animate inner text lines upward:
+
 ```css
 .text-line-wrapper {
   overflow: hidden;

package/.agent/skills/mcp-builder/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before architecting MCP tools or resource handlers, you MUST inspect:
+
 1. Strict Zod Input Validation (Section 45) → Enforce explicit JSON Schema parameter validation (Zod) for every tool exposed to the LLM
 2. Resource vs Tool Distinction (Section 68) → Use Resources for static read-only data (`file:///`, `db://schema`), Tools strictly for dynamic parameterized actions
 3. Output Payload Truncation Safeguard (Section 94) → Forcibly truncate large tool response outputs before returning payload to protect LLM context windows
@@ -47,27 +48,29 @@ A robust MCP server exposes exactly 3 primary concepts:
 
 ```typescript
 // Standardize exposing a Tool securely via an MCP Server Wrapper
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { z } from "zod";
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { z } from 'zod';
 
 const server = new McpServer({
-  name: "internal-database-auditor",
-  version: "1.0.0",
+  name: 'internal-database-auditor',
+  version: '1.0.0',
 });
 
 // Defining a rigorous tool parameter boundary
 server.tool(
-  "query_production_database",
-  "Executes a read-only sanitized query against the production analytical replica.",
+  'query_production_database',
+  'Executes a read-only sanitized query against the production analytical replica.',
   {
-    table: z.enum(["users", "transactions", "audit_logs"]).describe("The specific table to analyze"),
-    limit: z.number().max(100).default(10).describe("Maximum row returns to prevent context bloat"),
+    table: z
+      .enum(['users', 'transactions', 'audit_logs'])
+      .describe('The specific table to analyze'),
+    limit: z.number().max(100).default(10).describe('Maximum row returns to prevent context bloat'),
   },
   async ({ table, limit }) => {
     // Execution logic
     const data = await secureDatabaseClient.query(`SELECT * FROM ${table} LIMIT ${limit}`);
     return {
-      content: [{ type: "text", text: JSON.stringify(data) }],
+      content: [{ type: 'text', text: JSON.stringify(data) }],
     };
   },
 );
@@ -91,7 +94,7 @@ If your description is vague, the LLM will hallucinate executions unpredictably.
 
 ```typescript
 // ❌ VAGUE (The LLM will guess when to use this, often incorrectly)
-description: "Changes the system status.";
+description: 'Changes the system status.';
 
 // ✅ DETERMINISTIC (The LLM knows the exact boundaries and consequences)
 description: "Transitions the payment processing gateway between 'ACTIVE' and 'MAINTENANCE' modes. Use this ONLY after verifying traffic logs to halt impending queue flooding. Requires Admin clearance.";