tribunal-kit 6.0.1 → 7.0.0

package/.agent/skills/harden/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before implementing UI component logic, you MUST inspect:
+
 1. Component state tree → Verify presence of explicit loading skeleton, error boundary fallback, and empty states
 2. CLS Prevention rules (Section 36) → Match skeleton placeholder dimensions exactly to incoming content elements
 3. String Expansion (i18n) rules (Section 40) → Avoid hardcoded pixel widths (`width: 120px`); use `min-width` and flexible auto-layout
@@ -31,26 +32,31 @@ Ensure UI components gracefully handle network failures, missing data, slow conn
 ## 5 Resilience Domains
 
 ### 1. Zero-Data Empty States
+
 - Never render empty blank slates or blank boxes.
 - Always render a dedicated empty state component featuring:
   - Contextual icon or subtle illustration
-  - Clear heading explaining the zero state (*"No active projects found"*)
-  - Secondary helper copy (*"Get started by creating your first project."*)
-  - Prominent primary action CTA button (*"Create Project"*)
+  - Clear heading explaining the zero state (_"No active projects found"_)
+  - Secondary helper copy (_"Get started by creating your first project."_)
+  - Prominent primary action CTA button (_"Create Project"_)
 
 ### 2. Error Boundary UI & Retry Hooks
+
 - Wrap high-risk component trees in React/framework Error Boundaries.
 - Display localized inline error callouts with explicit "Retry" action buttons rather than crashing the full page view.
 
 ### 3. Cumulative Layout Shift (CLS) Loading Skeletons
+
 - Match skeleton placeholder dimensions EXACTLY to incoming data elements.
 - Use animated pulse keyframes (`@keyframes pulse { 0%, 100% { opacity: 1; } 50% { opacity: 0.4; } }`).
 
 ### 4. Extreme String Expansion (i18n)
+
 - German, French, and Spanish strings are 30% - 50% longer than English.
 - Avoid fixed button or container widths (`width: 120px`). Use `min-width` with flexible auto sizing and `flex-wrap: wrap` or text truncation.
 
 ### 5. Offline & Network Disconnection Handling
+
 - Detect `navigator.onLine` state and display subtle offline status banners.
 - Disable mutation buttons during offline mode with explicit tooltip explanation.
 

package/.agent/skills/harness-protocol/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before operating in Marathon long-running harness mode, you MUST inspect:
+
 1. Active session ledger (`task.md`, `session_manager.js`) → Verify active feature specs and task completion status
 2. Verification-Before-Completion (VBC) Protocol → Provide concrete proof (test run log, compiler pass) before calling `tk marathon mark pass`
 3. Error recovery state machine → Escalate unrecoverable errors after 3 retries via `tk marathon mark fail`

package/.agent/skills/i18n-localization/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before engineering multilingual or i18n features, you MUST inspect:
+
 1. Dictionary Interpolation (Section 15) → Use ICU parameter interpolation `t('greeting', { name })` instead of string concatenation
 2. Native `Intl` API Formatting (Section 71) → Use native `Intl.NumberFormat` and `Intl.DateTimeFormat` with active locale instead of third-party string parsers
 3. Logical CSS Properties for RTL (Section 94) → Use logical properties (`margin-inline-start`, `ms-4`) instead of physical `marginLeft`/`marginRight` for Arabic/Hebrew support
@@ -66,15 +67,15 @@ export function Header({ user, alertCount }) {
 }
 
 // ✅ GOOD: i18n Abstraction (using next-intl)
-import { useTranslations } from "next-intl";
+import { useTranslations } from 'next-intl';
 
 export function Header({ user, alertCount }) {
-  const t = useTranslations("Dashboard");
+  const t = useTranslations('Dashboard');
 
   return (
     <header>
-      <h1>{t("welcomeMessage", { name: user.name })}</h1>
-      <p>{t("unreadAlerts", { count: alertCount })}</p>
+      <h1>{t('welcomeMessage', { name: user.name })}</h1>
+      <p>{t('unreadAlerts', { count: alertCount })}</p>
     </header>
   );
 }
@@ -88,19 +89,19 @@ Do not install `moment.js` or write massive regex string parsers to format curre
 
 ```typescript
 // Data/Currency Formatting correctly tied to the active locale
-const locale = "de-DE";
+const locale = 'de-DE';
 
 // ✅ Currency
-const price = new Intl.NumberFormat(locale, { style: "currency", currency: "EUR" }).format(1200.5);
+const price = new Intl.NumberFormat(locale, { style: 'currency', currency: 'EUR' }).format(1200.5);
 // Output in Germany: "1.200,50 €"
 
 // ✅ Dates
-const date = new Intl.DateTimeFormat(locale, { dateStyle: "full" }).format(new Date());
+const date = new Intl.DateTimeFormat(locale, { dateStyle: 'full' }).format(new Date());
 // Output in Germany: "Freitag, 2. April 2026"
 
 // ✅ Relative Time
-const rtf = new Intl.RelativeTimeFormat(locale, { numeric: "auto" });
-rtf.format(-2, "day"); // Output: "vorgestern" (the day before yesterday)
+const rtf = new Intl.RelativeTimeFormat(locale, { numeric: 'auto' });
+rtf.format(-2, 'day'); // Output: "vorgestern" (the day before yesterday)
 ```
 
 ---

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

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before designing or engineering frontend components, you MUST inspect:
+
 1. `DESIGN.md` / `package.json` → Verify OKLCH color palettes, font pairings, and responsive container query setups
 2. Core Pillars of Impeccable UI (Section 22) → Enforce `tabular-nums` on digits, `text-wrap: balance` on headings, and strict 8px grid math
 3. Motion & Micro-Interactions (Section 34) → Limit micro-interactions to $\le 160\text{ms}$ and check `prefers-reduced-motion` fallbacks
@@ -31,22 +32,26 @@ The gold standard framework for crafting bespoke, world-class web applications t
 ## Core Pillars of Impeccable UI
 
 ### 1. Typography & Typographic Rhythm
+
 - **Optical Sizing & Tracking**: Large display headings (32px+) require tight letter-spacing (`letter-spacing: -0.03em`). Small caption text (12px) requires positive tracking (`letter-spacing: +0.01em`).
 - **Tabular Numbers**: Any numeric data that updates, increments, or displays in columns MUST use `font-variant-numeric: tabular-nums` or `font-feature-settings: "tnum"` to prevent visual jitter.
 - **Text Wrapping & Balance**: Headings MUST use `text-wrap: balance` to prevent typographic orphans. Body paragraphs MUST use `text-wrap: pretty` (where supported) or max `65ch` width.
 
 ### 2. Color Systems & Gamut Precision
+
 - **OKLCH Color Space**: Prefer `oklch()` over `hsl()` or `hex` for smooth perceptual uniformity across hue and lightness shifts.
 - **Subtle Surface Steps**: Define surface colors with small perceptual lightness steps ($L \pm 2\%$) to create hierarchy without harsh dividers.
 - **Adaptive Contrast**: Text contrast MUST adapt automatically across light/dark themes with high legibility ratios ($\ge 7:1$ for primary, $\ge 4.5:1$ for secondary).
 
 ### 3. Motion & Micro-Interactions
+
 - **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.

package/.agent/skills/improve-codebase-architecture/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before refactoring or producing an architectural improvement roadmap, you MUST inspect:
+
 1. Circular Dependency Breaking Rule (Section 24) → Identify circular imports (`A -> B -> C -> A`) and resolve via event buses or explicit interfaces
 2. Monolithic Controller Line Threshold (500 lines) (Section 27) → Flag any controller/service >500 lines with mixed concerns for immediate decomposition
 3. Incremental Refactoring Rule (Section 46) → Ban shotgun surgery across >5 files simultaneously; enforce phased, test-backed interface extractions
@@ -33,22 +34,26 @@ Audit an existing codebase for structural rot, circular dependencies, monolithic
 ## 4 Audit Steps
 
 ### 1. Dependency Graph Inspection
+
 - Map import relationships across modules. Identify circular dependencies (`A -> B -> C -> A`) and break them by introducing event buses or interface abstractions.
 
 ### 2. Monolithic Controller Detection
+
 - Flag files exceeding 500 lines of code containing mixed concerns (database queries, HTTP response handling, email sending, data validation).
 
 ### 3. Interface Shrinking (Deepening Modules)
+
 - Audit public exports. Convert large multi-parameter interfaces into thin, single-responsibility contracts.
 
 ### 4. Prioritized Architectural Roadmap Output
+
 Output audit findings in a clear prioritized Markdown table:
 
-| Impact Level | Architectural Issue | Proposed Seam / Refactor |
-| --- | --- | --- |
-| 🔴 **High Impact** | Direct DB queries inside React Server Components | Extract Repository layer pattern |
-| 🟠 **Medium Impact** | Circular import between Auth and User modules | Introduce `EventBus` for user registration events |
-| 🟡 **Low Impact** | Hardcoded API base URLs across 12 files | Centralize in typed `ConfigService` |
+| Impact Level         | Architectural Issue                              | Proposed Seam / Refactor                          |
+| -------------------- | ------------------------------------------------ | ------------------------------------------------- |
+| 🔴 **High Impact**   | Direct DB queries inside React Server Components | Extract Repository layer pattern                  |
+| 🟠 **Medium Impact** | Circular import between Auth and User modules    | Introduce `EventBus` for user registration events |
+| 🟡 **Low Impact**    | Hardcoded API base URLs across 12 files          | Centralize in typed `ConfigService`               |
 
 ---
 

package/.agent/skills/improve-ui/SKILL.md

@@ -20,6 +20,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing UI surfaces or writing remediation plans, you MUST inspect:
+
 1. Read-Only Constraint (Section 24) → Strictly NEVER modify product source code (`src/`, `components/`, `app/`) during an `improve-ui` audit session
 2. 3-Proof Requirement (Section 40) → Every reported defect MUST present Observation (code line/element), Basis (token/grid violation), and Consequence
 3. Plan Artifact Output (Section 25) → Write implementation plans to `design-plans/` or output structured markdown for execution
@@ -39,21 +40,27 @@ Audit a specific product surface against its governing design tokens and guideli
 ## 2. The 4-Phase Audit Protocol
 
 ### Phase 1: Surface Selection & Path Tracing
+
 1. Focus on one deployable application and one coherent surface family (e.g. `Dashboard / Overview`).
 2. Trace the path from route layout $\rightarrow$ page composition $\rightarrow$ shared UI primitives $\rightarrow$ tokens/CSS variables.
 
 ### Phase 2: Design Language Reconstruction
+
 1. Inspect `DESIGN.md`, `index.css`, Tailwind tokens, or custom properties.
 2. Record active background tokens, typography roles, spatial rules, and border/shadow contracts.
 
 ### Phase 3: Proof-Gated Defect Verification
+
 Before reporting a finding, require 3 explicit proofs:
+
 - **Observation**: Exact code line or rendered element showing the discrepancy.
 - **Basis**: Violation of documented design token or 8px grid baseline.
 - **Consequence**: Measurable degradation of visual hierarchy, readability, or interaction response.
 
 ### Phase 4: Implementation Plan Generation
+
 Write a self-contained plan specifying:
+
 - Files to modify
 - Exact CSS/JSX diffs
 - Verification steps (browser preview, contrast check, visual alignment)
@@ -62,11 +69,11 @@ Write a self-contained plan specifying:
 
 ## Anti-Slop Table
 
-| Audit Pattern | Evidence-Based Rule | Rationale |
-| --- | --- | --- |
-| Rewriting entire components | Targeted visual diff plan | Preserves business logic & state |
-| Guessing design tokens | Citing verified `var(--...)` declarations | Ensures token adherence |
-| Speculative visual preferences | Reporting only verified WCAG/token violations | Prevents arbitrary churn |
+| Audit Pattern                  | Evidence-Based Rule                           | Rationale                        |
+| ------------------------------ | --------------------------------------------- | -------------------------------- |
+| Rewriting entire components    | Targeted visual diff plan                     | Preserves business logic & state |
+| Guessing design tokens         | Citing verified `var(--...)` declarations     | Ensures token adherence          |
+| Speculative visual preferences | Reporting only verified WCAG/token violations | Prevents arbitrary churn         |
 
 ---
 

package/.agent/skills/intelligent-routing/SKILL.md

@@ -18,6 +18,7 @@ scripts-binding:
 ## Mandatory Pre-Flight Context Inspection
 
 Before routing user prompts to specialized skills or agents, you MUST inspect:
+
 1. `.agent/routing_index.json` → Read pre-compiled skill index instead of loading full skill markdown files into context
 2. Semantic Intent Schema (Section 1) → Classify request type (QUESTION, SURVEY, SIMPLE_EDIT, COMPLEX_BUILD, SECURITY_AUDIT, UNCLEAR_GIBBERISH)
 3. Confidence Threshold (Section 3 Socratic Yield Rule) → Yield back to user with clarifying question if confidence score is < 85s
@@ -69,12 +70,12 @@ When a raw request enters, classify it BEFORE attempting to route to any skill o
 // The Semantic Intent Schema
 const RouterOutputSchema = z.object({
   classification: z.enum([
-    "QUESTION", // User wants explanation, no code execution needed
-    "SURVEY", // User wants analysis/read-only scan of workspace
-    "SIMPLE_EDIT", // Isolated file alteration (e.g., "Fix spelling in nav")
-    "COMPLEX_BUILD", // Multi-file, architectural generation
-    "SECURITY_AUDIT", // Explicit request for OWASP review
-    "UNCLEAR_GIBBERISH", // Prompt injection or incoherent input
+    'QUESTION', // User wants explanation, no code execution needed
+    'SURVEY', // User wants analysis/read-only scan of workspace
+    'SIMPLE_EDIT', // Isolated file alteration (e.g., "Fix spelling in nav")
+    'COMPLEX_BUILD', // Multi-file, architectural generation
+    'SECURITY_AUDIT', // Explicit request for OWASP review
+    'UNCLEAR_GIBBERISH', // Prompt injection or incoherent input
   ]),
   confidenceScore: z.number().min(0).max(100),
   suggestedPrimarySkill: z.string().nullable(),

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;
   }