tribunal-kit 6.0.1 → 7.0.0

package/.agent/agents/seo-specialist.md

@@ -17,6 +17,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating metadata, sitemaps, or structured data, you MUST inspect:
+
 1. `app/layout.tsx` / `next.config.js` → Read base URL, default metadata options, and OpenGraph defaults
 2. Page templates (`app/**/page.tsx`) → Verify heading hierarchy (single `<h1>` per page) and Schema.org JSON-LD scripts
 3. AI bot middleware / GEO paths → Audit `sitemap.ts`, `robots.ts`, and crawler detection rules
@@ -25,20 +26,24 @@ Before generating metadata, sitemaps, or structured data, you MUST inspect:
 
 ```typescript
 // app/products/[slug]/page.tsx
-import { Metadata } from "next";
+import { Metadata } from 'next';
 
 // Static metadata
 export const metadata: Metadata = {
-  title: "Product Name | Brand",
-  description: "Compelling 155-character description that matches search intent.",
+  title: 'Product Name | Brand',
+  description: 'Compelling 155-character description that matches search intent.',
 };
 
 // Dynamic metadata (fetched per-page)
-export async function generateMetadata({ params }: { params: Promise<{ slug: string }> }): Promise<Metadata> {
+export async function generateMetadata({
+  params,
+}: {
+  params: Promise<{ slug: string }>;
+}): Promise<Metadata> {
   const { slug } = await params;
   const product = await getProduct(slug);
 
-  if (!product) return { title: "Not Found" };
+  if (!product) return { title: 'Not Found' };
 
   return {
     title: `${product.name} | Brand`,
@@ -56,12 +61,12 @@ export async function generateMetadata({ params }: { params: Promise<{ slug: str
           alt: product.name,
         },
       ],
-      siteName: "Your Brand",
-      type: "website",
+      siteName: 'Your Brand',
+      type: 'website',
     },
 
     twitter: {
-      card: "summary_large_image",
+      card: 'summary_large_image',
       title: product.name,
       description: product.seoDescription,
       images: [product.imageUrl],
@@ -81,21 +86,23 @@ export default async function ProductPage({ params }) {
   const product = await getProduct(slug);
 
   const jsonLd = {
-    "@context": "https://schema.org",
-    "@type": "Product",
+    '@context': 'https://schema.org',
+    '@type': 'Product',
     name: product.name,
     image: product.imageUrl,
     description: product.description,
     sku: product.sku,
     offers: {
-      "@type": "Offer",
+      '@type': 'Offer',
       price: product.price,
-      priceCurrency: "USD",
-      availability: product.inStock ? "https://schema.org/InStock" : "https://schema.org/OutOfStock",
+      priceCurrency: 'USD',
+      availability: product.inStock
+        ? 'https://schema.org/InStock'
+        : 'https://schema.org/OutOfStock',
       url: `https://yoursite.com/products/${slug}`,
     },
     aggregateRating: {
-      "@type": "AggregateRating",
+      '@type': 'AggregateRating',
       ratingValue: product.averageRating,
       reviewCount: product.reviewCount,
     },
@@ -103,7 +110,10 @@ export default async function ProductPage({ params }) {
 
   return (
     <>
-      <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }} />
+      <script
+        type="application/ld+json"
+        dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
+      />
       {/* page content */}
     </>
   );
@@ -116,29 +126,29 @@ export default async function ProductPage({ params }) {
 
 ```typescript
 // app/sitemap.ts
-import { MetadataRoute } from "next";
+import { MetadataRoute } from 'next';
 
 export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
   const products = await getAllProducts();
 
-  const productUrls = products.map((product) => ({
+  const productUrls = products.map(product => ({
     url: `https://yoursite.com/products/${product.slug}`,
     lastModified: product.updatedAt,
-    changeFrequency: "weekly" as const,
+    changeFrequency: 'weekly' as const,
     priority: 0.8,
   }));
 
   return [
     {
-      url: "https://yoursite.com",
+      url: 'https://yoursite.com',
       lastModified: new Date(),
-      changeFrequency: "daily",
+      changeFrequency: 'daily',
       priority: 1.0,
     },
     {
-      url: "https://yoursite.com/products",
+      url: 'https://yoursite.com/products',
       lastModified: new Date(),
-      changeFrequency: "daily",
+      changeFrequency: 'daily',
       priority: 0.9,
     },
     ...productUrls,
@@ -177,7 +187,7 @@ When AI engines (Perplexity, ChatGPT Search) index your site, they need:
 // Next.js Edge Middleware: serve bare markdown to AI bots
 // middleware.ts
 export function middleware(req: NextRequest) {
-  const ua = req.headers.get("user-agent") ?? "";
+  const ua = req.headers.get('user-agent') ?? '';
   const isAIBot = /ChatGPT-User|PerplexityBot|ClaudeBot|GPTBot/i.test(ua);
 
   if (isAIBot) {

package/.agent/agents/sql-reviewer.md

@@ -21,6 +21,7 @@ SQL mistakes are quiet, catastrophic, and permanent. Injection vulnerabilities e
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing SQL queries or ORM calls, you MUST inspect:
+
 1. `schema.prisma` / `drizzle.schema.ts` / DB migrations → Inspect table schema, existing indices, and foreign key relations
 2. ORM & DB driver in `package.json` → Confirm parameterization syntax (`$1` in pg vs `?` in mysql vs Prisma objects)
 3. Query invocation sites → Check for raw SQL strings (`SELECT ... ${input}`) or `for` loops making queries inside loop bodies
@@ -40,7 +41,7 @@ await db.execute(query);
 const result = await db.execute(`SELECT * FROM orders WHERE id = ${orderId}`);
 
 // ✅ SAFE: Parameterized query (Postgres/pg driver)
-const result = await client.query("SELECT * FROM users WHERE email = $1", [userInput]);
+const result = await client.query('SELECT * FROM users WHERE email = $1', [userInput]);
 
 // ✅ SAFE: Prisma — never interpolates user input into SQL
 const user = await prisma.user.findUnique({
@@ -73,14 +74,14 @@ const users = await prisma.user.findMany({
 // ❌ N+1: GraphQL resolver without DataLoader
 const resolver = {
   User: {
-    posts: (parent) => db.posts.findAll({ where: { userId: parent.id } }), // Fires per user!
+    posts: parent => db.posts.findAll({ where: { userId: parent.id } }), // Fires per user!
   },
 };
 
 // ✅ FIXED: DataLoader batches all requests into one query
-const postsLoader = new DataLoader(async (userIds) => {
+const postsLoader = new DataLoader(async userIds => {
   const posts = await db.posts.findAll({ where: { userId: userIds } });
-  return userIds.map((id) => posts.filter((p) => p.userId === id));
+  return userIds.map(id => posts.filter(p => p.userId === id));
 });
 ```
 

package/.agent/agents/supervisor-agent.md

@@ -18,6 +18,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before decomposing goals into worker dispatches, you MUST inspect:
+
 1. `swarm-worker-registry.md` → Read the primary routing table and specialist worker capabilities
 2. Active codebase file layout (`task.md`, file structure) → Ensure worker target file paths do not overlap across parallel tasks
 3. System constraints & dependencies (`package.json`, environment variables) → Verify context passed to workers is grounded in current repo state
@@ -78,8 +79,17 @@ Every worker receives a structured JSON dispatch. No unstructured natural langua
   "scope": "Refactor the UserCard component to use Server Components and remove client-side state that belongs on the server.",
   "files_to_read": ["src/components/UserCard.tsx", "src/app/users/[id]/page.tsx"],
   "files_to_write": ["src/components/UserCard.tsx", "src/components/UserCardClient.tsx"],
-  "context_summary": ["The app uses Next.js 15 App Router", "Authentication is handled via next-auth v5 (now 'auth' package)", "Database uses Prisma 6 with PostgreSQL", "No existing tests for this component"],
-  "constraints": ["Do NOT modify any files outside the listed files_to_write", "Store only interactive state in the Client Component", "Maintain identical visual output — no design changes"],
+  "context_summary": [
+    "The app uses Next.js 15 App Router",
+    "Authentication is handled via next-auth v5 (now 'auth' package)",
+    "Database uses Prisma 6 with PostgreSQL",
+    "No existing tests for this component"
+  ],
+  "constraints": [
+    "Do NOT modify any files outside the listed files_to_write",
+    "Store only interactive state in the Client Component",
+    "Maintain identical visual output — no design changes"
+  ],
   "output_format": {
     "status": "COMPLETE | BLOCKED | ERROR",
     "files_modified": ["list of files actually changed"],

package/.agent/agents/swarm-worker-contracts.md

@@ -18,16 +18,16 @@ interface WorkerRequest {
 
   // The category of work being requested.
   type:
-    | "research" // Understand or explain something
-    | "generate_code" // Write new code
-    | "review_code" // Audit existing code
-    | "debug" // Find and fix a bug
-    | "plan" // Produce a structured plan only (no code)
-    | "design_schema" // Design a database or data schema
-    | "write_docs" // Write documentation or comments
-    | "security_audit" // OWASP security review
-    | "optimize" // Refactor for performance
-    | "test"; // Write or run tests
+    | 'research' // Understand or explain something
+    | 'generate_code' // Write new code
+    | 'review_code' // Audit existing code
+    | 'debug' // Find and fix a bug
+    | 'plan' // Produce a structured plan only (no code)
+    | 'design_schema' // Design a database or data schema
+    | 'write_docs' // Write documentation or comments
+    | 'security_audit' // OWASP security review
+    | 'optimize' // Refactor for performance
+    | 'test'; // Write or run tests
 
   // The agent to route this WorkerRequest to.
   // MUST match a filename in .agent/agents/ (without the .md extension).
@@ -77,9 +77,9 @@ interface WorkerResult {
 
   // Outcome of the Worker's execution.
   status:
-    | "success" // Task completed. Output is valid.
-    | "failure" // Task failed but retries remain.
-    | "escalate"; // Task failed after max_retries. Requires human intervention.
+    | 'success' // Task completed. Output is valid.
+    | 'failure' // Task failed but retries remain.
+    | 'escalate'; // Task failed after max_retries. Requires human intervention.
 
   // The agent's output if status is "success".
   // Empty string if status is "failure" or "escalate".

package/.agent/agents/swarm-worker-registry.md

@@ -8,35 +8,35 @@ All agents listed here MUST exist as `.md` files in `.agent/agents/`.
 
 ## Primary Routing Table
 
-| Task Type        | Domain Keywords                                  | Route to Agent          |
-| ---------------- | ------------------------------------------------ | ----------------------- |
-| `research`       | any                                              | `explorer-agent`        |
-| `research`       | security, vulnerability, owasp                   | `security-auditor`      |
-| `research`       | database, schema, sql, orm                       | `database-architect`    |
-| `research`       | performance, profiling, optimization             | `performance-optimizer` |
-| `generate_code`  | api, route, endpoint, server, express, auth, jwt | `backend-specialist`    |
-| `generate_code`  | python, fastapi, django, flask                   | `python-pro`            |
-| `generate_code`  | c#, .net, blazor, aspnet                         | `csharp-developer`      |
-| `generate_code`  | component, hook, react, next, ui, css            | `frontend-specialist`   |
-| `generate_code`  | mobile, react native, flutter, ios, android      | `mobile-developer`      |
-| `generate_code`  | docker, ci, cd, deploy, github actions, cloud    | `devops-engineer`       |
-| `generate_code`  | sql, query, migration, prisma, drizzle           | `sql-pro`               |
-| `generate_code`  | vue, nuxt                                        | `vue-expert`            |
-| `review_code`    | api, backend, auth                               | `backend-specialist`    |
-| `review_code`    | react, component, hook                           | `frontend-specialist`   |
-| `review_code`    | sql, query                                       | `sql-pro`               |
-| `review_code`    | security (any domain)                            | `security-auditor`      |
-| `debug`          | any                                              | `debugger`              |
-| `plan`           | any                                              | `project-planner`       |
-| `design_schema`  | any                                              | `database-architect`    |
-| `write_docs`     | any                                              | `documentation-writer`  |
-| `security_audit` | any                                              | `security-auditor`      |
-| `optimize`       | any                                              | `performance-optimizer` |
-| `test`           | any                                              | `test-engineer`         |
-| `visual_audit`   | ui, component, visual, screenshot, layout, render| `ui-visual-auditor`     |
-| `generate_code`  | aws, terraform, ecs, fargate, lambda, iac, vpc   | `cloud-engineer`        |
-| `plan`           | system design, scale, capacity, architecture     | `system-architect`      |
-| `test`           | e2e, playwright, automation, cypress             | `qa-automation-engineer`|
+| Task Type        | Domain Keywords                                   | Route to Agent           |
+| ---------------- | ------------------------------------------------- | ------------------------ |
+| `research`       | any                                               | `explorer-agent`         |
+| `research`       | security, vulnerability, owasp                    | `security-auditor`       |
+| `research`       | database, schema, sql, orm                        | `database-architect`     |
+| `research`       | performance, profiling, optimization              | `performance-optimizer`  |
+| `generate_code`  | api, route, endpoint, server, express, auth, jwt  | `backend-specialist`     |
+| `generate_code`  | python, fastapi, django, flask                    | `python-pro`             |
+| `generate_code`  | c#, .net, blazor, aspnet                          | `csharp-developer`       |
+| `generate_code`  | component, hook, react, next, ui, css             | `frontend-specialist`    |
+| `generate_code`  | mobile, react native, flutter, ios, android       | `mobile-developer`       |
+| `generate_code`  | docker, ci, cd, deploy, github actions, cloud     | `devops-engineer`        |
+| `generate_code`  | sql, query, migration, prisma, drizzle            | `sql-pro`                |
+| `generate_code`  | vue, nuxt                                         | `vue-expert`             |
+| `review_code`    | api, backend, auth                                | `backend-specialist`     |
+| `review_code`    | react, component, hook                            | `frontend-specialist`    |
+| `review_code`    | sql, query                                        | `sql-pro`                |
+| `review_code`    | security (any domain)                             | `security-auditor`       |
+| `debug`          | any                                               | `debugger`               |
+| `plan`           | any                                               | `project-planner`        |
+| `design_schema`  | any                                               | `database-architect`     |
+| `write_docs`     | any                                               | `documentation-writer`   |
+| `security_audit` | any                                               | `security-auditor`       |
+| `optimize`       | any                                               | `performance-optimizer`  |
+| `test`           | any                                               | `test-engineer`          |
+| `visual_audit`   | ui, component, visual, screenshot, layout, render | `ui-visual-auditor`      |
+| `generate_code`  | aws, terraform, ecs, fargate, lambda, iac, vpc    | `cloud-engineer`         |
+| `plan`           | system design, scale, capacity, architecture      | `system-architect`       |
+| `test`           | e2e, playwright, automation, cypress              | `qa-automation-engineer` |
 
 ---
 
@@ -54,28 +54,28 @@ When multiple domain keywords match, apply the following priority order:
 
 Quick reference for Supervisor triage. Full instructions are in each agent's `.md` file.
 
-| Agent File                 | Best For                                         | Do NOT Use For          |
-| -------------------------- | ------------------------------------------------ | ----------------------- |
-| `backend-specialist.md`    | REST APIs, auth flows, server logic              | React components        |
-| `python-pro.md`            | FastAPI, Django, data scripts                    | Node/TypeScript code    |
-| `csharp-developer`         | .NET 8+, C#, Blazor, AOT                         | Python or Node backends |
-| `frontend-specialist.md`   | Web UI, CSS, components                          | Server code             |
-| `react-specialist.md`      | Advanced React patterns, Next.js architecture    | Vue or mobile           |
-| `vue-expert.md`            | Vue 3, Nuxt 3, Pinia                             | React or Angular        |
-| `mobile-developer.md`      | React Native, Flutter                            | Web browser UI          |
-| `database-architect.md`    | Schema design, ORM selection, migrations         | Raw SQL query tuning    |
-| `sql-pro.md`               | Complex queries, CTEs, window functions, indexes | Schema design           |
-| `devops-engineer.md`       | CI/CD, Docker, Kubernetes, cloud infra           | Application code        |
-| `security-auditor.md`      | OWASP review, pen test findings, auth hardening  | Feature development     |
-| `performance-optimizer.md` | Profiling, bottleneck resolution, caching        | New feature design      |
-| `debugger.md`              | Root cause analysis, systematic issue isolation  | Code generation         |
-| `project-planner.md`       | Planning, task breakdown, estimates              | Implementation          |
-| `documentation-writer.md`  | READMEs, API docs, inline comments               | Code or schemas         |
-| `test-engineer.md`         | Unit/integration test design and strategy        | Production code         |
-| `explorer-agent.md`        | Mapping unknown codebases before acting          | Building new features   |
-| `cloud-engineer.md`        | AWS, Terraform, Docker, ECS, GitHub Actions CI   | Application code        |
-| `system-architect.md`      | System design, capacity planning, scalability    | Implementation details  |
-| `qa-automation-engineer.md`| E2E testing, Playwright, test automation          | Unit test design        |
+| Agent File                  | Best For                                         | Do NOT Use For          |
+| --------------------------- | ------------------------------------------------ | ----------------------- |
+| `backend-specialist.md`     | REST APIs, auth flows, server logic              | React components        |
+| `python-pro.md`             | FastAPI, Django, data scripts                    | Node/TypeScript code    |
+| `csharp-developer`          | .NET 8+, C#, Blazor, AOT                         | Python or Node backends |
+| `frontend-specialist.md`    | Web UI, CSS, components                          | Server code             |
+| `react-specialist.md`       | Advanced React patterns, Next.js architecture    | Vue or mobile           |
+| `vue-expert.md`             | Vue 3, Nuxt 3, Pinia                             | React or Angular        |
+| `mobile-developer.md`       | React Native, Flutter                            | Web browser UI          |
+| `database-architect.md`     | Schema design, ORM selection, migrations         | Raw SQL query tuning    |
+| `sql-pro.md`                | Complex queries, CTEs, window functions, indexes | Schema design           |
+| `devops-engineer.md`        | CI/CD, Docker, Kubernetes, cloud infra           | Application code        |
+| `security-auditor.md`       | OWASP review, pen test findings, auth hardening  | Feature development     |
+| `performance-optimizer.md`  | Profiling, bottleneck resolution, caching        | New feature design      |
+| `debugger.md`               | Root cause analysis, systematic issue isolation  | Code generation         |
+| `project-planner.md`        | Planning, task breakdown, estimates              | Implementation          |
+| `documentation-writer.md`   | READMEs, API docs, inline comments               | Code or schemas         |
+| `test-engineer.md`          | Unit/integration test design and strategy        | Production code         |
+| `explorer-agent.md`         | Mapping unknown codebases before acting          | Building new features   |
+| `cloud-engineer.md`         | AWS, Terraform, Docker, ECS, GitHub Actions CI   | Application code        |
+| `system-architect.md`       | System design, capacity planning, scalability    | Implementation details  |
+| `qa-automation-engineer.md` | E2E testing, Playwright, test automation         | Unit test design        |
 
 ---
 

package/.agent/agents/system-architect.md

@@ -15,6 +15,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before designing high-level system architectures, you MUST inspect:
+
 1. Active codebase scale & dependencies (`package.json`, `ARCHITECTURE.md`, microservices vs monolith setup)
 2. Data storage models (`schema.prisma`, SQL schemas, cache configs) → Assess read/write ratios, partitioning, and replica setups
 3. Scale targets (DAU, peak QPS, storage growth, latency SLOs) → Establish quantitative bounds before making component choices

package/.agent/agents/test-coverage-reviewer.md

@@ -21,6 +21,7 @@ Coverage numbers are vanity metrics. You audit for **behavioral completeness**
 ## Mandatory Pre-Flight Context Inspection
 
 Before auditing test coverage and quality, you MUST inspect:
+
 1. Active test runner config (`vitest.config.ts`, `jest.config.js`, `playwright.config.ts`) → Read coverage thresholds and test match globs
 2. Tested source file exported symbols → Cross-reference exported functions against corresponding test cases in `.test.ts` or `.spec.ts`
 3. Required edge case coverage checklist (Section 2) → Audit numbers (0, negative), strings (empty, whitespace), arrays (empty), and auth boundaries
@@ -33,27 +34,27 @@ This is the most common test failure mode. AI generates tests for the success ca
 
 ```typescript
 // ❌ INCOMPLETE: Only tests the success path
-describe("calculateDiscount()", () => {
-  it("applies 10% to orders over $100", () => {
+describe('calculateDiscount()', () => {
+  it('applies 10% to orders over $100', () => {
     expect(calculateDiscount(150)).toBe(135);
   });
 });
 
 // ✅ COMPLETE: Tests all behavioral boundaries
-describe("calculateDiscount()", () => {
-  it("applies 10% to orders over $100", () => {
+describe('calculateDiscount()', () => {
+  it('applies 10% to orders over $100', () => {
     expect(calculateDiscount(150)).toBe(135);
   });
-  it("applies no discount to orders at exactly $100", () => {
+  it('applies no discount to orders at exactly $100', () => {
     expect(calculateDiscount(100)).toBe(100); // Boundary edge case
   });
-  it("applies no discount to orders under $100", () => {
+  it('applies no discount to orders under $100', () => {
     expect(calculateDiscount(50)).toBe(50);
   });
-  it("throws on negative input", () => {
+  it('throws on negative input', () => {
     expect(() => calculateDiscount(-50)).toThrow(/negative/i);
   });
-  it("handles zero input", () => {
+  it('handles zero input', () => {
     expect(calculateDiscount(0)).toBe(0);
   });
 });
@@ -81,19 +82,19 @@ For any function being tested, flag if these are missing:
 
 ```typescript
 // ❌ BRITTLE: CSS selectors break on UI refactoring
-const button = container.querySelector(".btn-primary > span");
+const button = container.querySelector('.btn-primary > span');
 
 // ❌ BRITTLE: Index-based selection — breaks when order changes
-const firstItem = getAllByRole("listitem")[0];
+const firstItem = getAllByRole('listitem')[0];
 
 // ❌ BRITTLE: Text content in another language context (i18n risk)
-const btn = getByText("Enregistrer"); // French — breaks if locale changes
+const btn = getByText('Enregistrer'); // French — breaks if locale changes
 
 // ✅ RESILIENT: Role-based selector — verifies accessibility simultaneously
-const submitBtn = getByRole("button", { name: /submit/i });
+const submitBtn = getByRole('button', { name: /submit/i });
 
 // ✅ RESILIENT: data-testid for non-semantic elements
-const card = getByTestId("product-card-42");
+const card = getByTestId('product-card-42');
 ```
 
 ---
@@ -102,25 +103,27 @@ const card = getByTestId("product-card-42");
 
 ```typescript
 // ❌ BAD: Mocking internal business logic — tests nothing real
-vi.mock("./calculateTax"); // Now the test just verifies the mock, not the function
+vi.mock('./calculateTax'); // Now the test just verifies the mock, not the function
 
 // ❌ BAD: Overspecified mock — asserting exact call parameters that will change
 expect(mockSendEmail).toHaveBeenCalledWith(
-  "user@example.com",
-  "Welcome!",
+  'user@example.com',
+  'Welcome!',
   expect.any(String),
   { cc: undefined, bcc: undefined, replyTo: null }, // Too brittle
 );
 
 // ✅ GOOD: Mock at architectural boundaries only (network, DB, filesystem)
 // MSW intercepts network — component behaves exactly as in production
-import { setupServer } from "msw/node";
-const server = setupServer(http.get("/api/users", () => HttpResponse.json([{ id: 1, name: "Alice" }])));
+import { setupServer } from 'msw/node';
+const server = setupServer(
+  http.get('/api/users', () => HttpResponse.json([{ id: 1, name: 'Alice' }])),
+);
 
 // ✅ GOOD: Assert meaningful behavior — not exact implementation
 expect(mockSendEmail).toHaveBeenCalledWith(
-  "user@example.com",
-  expect.stringContaining("Welcome"), // Cares about content, not exact format
+  'user@example.com',
+  expect.stringContaining('Welcome'), // Cares about content, not exact format
 );
 ```
 
@@ -130,14 +133,14 @@ expect(mockSendEmail).toHaveBeenCalledWith(
 
 ```typescript
 // ❌ BAD: Tests internal private state (breaks on refactor)
-test("stores user in internal cache", () => {
+test('stores user in internal cache', () => {
   const service = new UserService();
   service.fetchUser(1);
   expect(service._cache.has(1)).toBe(true); // Internal implementation detail
 });
 
 // ✅ GOOD: Tests observable behavior — the public contract
-test("returns cached user on second call without network request", async () => {
+test('returns cached user on second call without network request', async () => {
   const service = new UserService();
   await service.fetchUser(1); // First call — hits network
   await service.fetchUser(1); // Second call — from cache

package/.agent/agents/test-engineer.md

@@ -18,6 +18,7 @@ last-updated: 2026-07-29
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating unit or integration tests, you MUST inspect:
+
 1. `package.json` → Confirm test runner engine (`vitest`, `jest`, `playwright`, `pytest`) and assertions configuration
 2. Target source file (`src/`, `lib/`, `app/`) → Read function signatures, export statements, and exception paths
 3. Existing test utilities (`test/setup.ts`, `vitest.config.ts`) → Check mock providers and shared test context fixtures
@@ -49,7 +50,7 @@ The loop repeats per function. The key is that the test drives the design — no
 
 ```typescript
 // ✅ Tests a specific, observable output
-expect(formatCurrency(1500)).toBe("$1,500.00");
+expect(formatCurrency(1500)).toBe('$1,500.00');
 
 // ❌ Tests that the function ran (not what it produced)
 const result = formatCurrency(1500);
@@ -63,16 +64,16 @@ expect(formatCurrency(1500)).toBe(formatCurrency(1500));
 
 ```typescript
 // ✅ One test → one behavior
-it("adds VAT to the price", () => {
+it('adds VAT to the price', () => {
   expect(addVat(100, 0.2)).toBe(120);
 });
 
-it("throws when rate is negative", () => {
-  expect(() => addVat(100, -0.2)).toThrow("Rate must be positive");
+it('throws when rate is negative', () => {
+  expect(() => addVat(100, -0.2)).toThrow('Rate must be positive');
 });
 
 // ❌ Two behaviors in one test — which one failed?
-it("adds VAT correctly", () => {
+it('adds VAT correctly', () => {
   expect(addVat(100, 0.2)).toBe(120);
   expect(() => addVat(100, -0.2)).toThrow();
 });
@@ -86,15 +87,15 @@ it("adds VAT correctly", () => {
 // ✅ Mock only the direct external dependency
 // Testing: userService.create()
 // Mock: the DB layer (because we don't need a real DB for this unit)
-vi.mock("../db", () => ({
-  insert: vi.fn().mockResolvedValue({ id: "u1", email: "test@example.com" }),
+vi.mock('../db', () => ({
+  insert: vi.fn().mockResolvedValue({ id: 'u1', email: 'test@example.com' }),
 }));
 
 // ❌ Over-mocking — nothing real is being tested
-vi.mock("../db");
-vi.mock("../logger");
-vi.mock("../validator");
-vi.mock("../emailService");
+vi.mock('../db');
+vi.mock('../logger');
+vi.mock('../validator');
+vi.mock('../emailService');
 // At this point you're testing that mocks return mocks
 ```