tribunal-kit 9.2.4 → 9.2.6

package/.agent/skills/anti-slop-enforcement/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: anti-slop-enforcement
+description: "Use when Tribunal extraction of the anti-slop rule sets. Enforces Purpose-Gates, Hard-Gates, and Liveliness Dials for UI engineering."
+version: 6.0.0
+last-updated: 2026-09-29
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
+---
+
+# Anti-Slop Enforcement Guidelines
+
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `anti-slop-enforcement` 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 Tribunal extraction of the anti-slop rule sets. Enforces Purpose-Gates, Hard-Gates, and Liveliness Dials for UI engineering.
+- **DO NOT activate when:** The task falls outside the `anti-slop-enforcement` 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 |
+
+
+This skill provides the definition for what constitutes "slop" and how to enforce intentionality.
+
+## 1. The Liveliness Dials
+Before writing any UI code, the agent MUST articulate the following three dials:
+
+- **ENERGY (1-3):**
+  - `1`: Baseline, calm, muted (Corporate, B2B SaaS).
+  - `2`: Bright, punchy, confident (Modern Developer Tool).
+  - `3`: Maximalist, high-contrast, aggressive (Consumer App, Hype Landing Page).
+
+- **RHYTHM (1-3):**
+  - `1`: Uniform, standard grids, predictable alignment.
+  - `2`: Syncopated, broken-grid elements, overlapping layers, dynamic spacing.
+  - `3`: Chaotic, brutalist, anti-alignment.
+
+- **MOTION (1-3):**
+  - `1`: Static, CSS hover only.
+  - `2`: Micro-interactions, route transitions (Framer Motion / View Transitions).
+  - `3`: Heavy scroll-jacking, GSAP, spring physics orchestration.
+
+## 2. Hard Gates (Absolute Bans)
+Do not allow these under any circumstances:
+1. **The Purple Cliché:** Using `#8B5CF6`, `violet-500`, or purple-to-blue mesh gradients as a default "tech" aesthetic.
+2. **Fake Data:** Generating fake statistics ("10,000+ users", "5-star rating") unless provided in the prompt.
+3. **Card-in-Card Mud:** Cards nested inside cards with the same background color and no border/shadow contrast.
+4. **Hex Hacks:** Using raw hex codes instead of the design system's variables (e.g., `oklch`).
+
+## 3. Purpose-Gates (Allowed only with stated purpose)
+These techniques are permitted ONLY IF the agent writes down a one-line reason (purpose) before generating the code:
+1. **Glassmorphism (`backdrop-filter: blur`)**: Must state *why* the layer beneath needs to be partially visible.
+2. **Gradients**: Must state *why* a solid color wasn't enough (e.g., "Using subtle gradient to indicate depth on the active tab").
+3. **Bento Grids**: Must state *why* the data requires a multi-column irregular grid instead of a standard list or card array.
+4. **Shadows > 20px**: Must state the z-index hierarchy reasoning for the massive shadow.
+
+## 🚨 Edge-Case & Failure Mode Matrix
+
+| 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 |
+|:---|:---|:---|
+| **Uncontrolled Re-render Loop** | Mutating state inside render bodies or omitting hook dependencies | Wrap effects with explicit deps and isolate reactive derivations in useMemo |
+| **Accessibility Neglect** | Interactive <div> without role="button", tabIndex, or onKeyDown | Use semantic <button> or provide ARIA role, keyboard handlers, and focus ring |
+| **Layout Shift Flash** | Images/dynamic content without aspect-ratio or explicit dimensions | Enforce aspect-ratio or skeleton placeholders to guarantee zero CLS |
+
+
+## 🏛️ Tribunal Verification & Guardrails
+
+**Active Reviewers:** `frontend-reviewer` · `type-safety` · `ui-ux-auditor` · `complexity-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
+```
+✅ Are all component props strictly typed with zero implicit "any"?
+✅ Are responsive breakpoints, fluid typography, and optical balance verified?
+✅ Is accessibility (ARIA labels, keyboard navigation, contrast ratio >= 4.5:1) validated?
+✅ Are re-renders minimized and state lifecycles cleanly separated?
+✅ Did I verify all imported UI components and icon sets actually exist?
+```
+
+### 🛑 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/.agent/skills/api-patterns/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: api-patterns
-description: "Use when API design mastery. REST, GraphQL, tRPC, and gRPC selection. Request/response design, pagination (cursor/offset), filtering, versioning, rate limiting, error formats (RFC 9457), authentication (JWT/OAuth2/API keys), idempotency, file uploads, webhooks, and OpenAPI documentation. Use when designing APIs, choosing protocols, or implementing API standards."
-version: 5.0.0
-last-updated: 2026-09-13
+description: "Use when designing, implementing, auditing, and hardening api patterns server logic, APIs, background jobs, and error boundaries."
+version: 6.0.0
+last-updated: 2026-09-29
 skills:
   - api-security-auditor
   - backend-security-expert
@@ -15,204 +15,265 @@ scripts-binding:
 
 # API Patterns — Design & Protocol Mastery
 
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
-## Hallucination Traps (Read First)
-
-- ❌ JWT in URL query params → ✅ `Authorization: Bearer` header only. Query params get logged in server access logs.
-- ❌ Assuming JWT is encrypted → ✅ JWT is base64-encoded (NOT encrypted). Anyone can decode it. Never put secrets/PII in the payload.
-- ❌ Offset pagination on large tables → ✅ `OFFSET 100000` scans and discards 100K rows. Use cursor pagination for tables > 10K rows.
-- ❌ Verbs in REST URLs (`/api/getUsers`) → ✅ Nouns only (`GET /api/users`). HTTP method IS the verb.
-- ❌ `POST` is idempotent → ✅ `POST` is NOT idempotent — requires `Idempotency-Key` header for safe retries.
-- ❌ GraphQL has no security risks → ✅ Deeply nested queries are a DoS vector. Set max depth, query cost limits. Disable introspection in production.
-
----
-
-## Protocol Selection Matrix
-
-| Protocol      | Use When                                                                              |
-| ------------- | ------------------------------------------------------------------------------------- |
-| **REST**      | Public APIs, 3rd-party consumers, standard CRUD, HTTP caching                         |
-| **GraphQL**   | Complex nested data, multiple clients, flexible queries, mobile bandwidth sensitivity |
-| **tRPC**      | Full-stack TypeScript (Next.js monorepo), shared types, no codegen                    |
-| **gRPC**      | Internal microservices, high-throughput, streaming, binary protocol                   |
-| **WebSocket** | Bidirectional real-time (chat, gaming, live collaboration)                            |
-| **SSE**       | Server-to-client streaming only (AI token streaming, live feeds)                      |
-
----
-
-## REST Design
-
-### URL Conventions
-
-```
-✅  GET    /api/v1/users              list users
-✅  GET    /api/v1/users/123          get user by ID
-✅  POST   /api/v1/users              create user
-✅  PATCH  /api/v1/users/123          partial update
-✅  DELETE /api/v1/users/123          delete user
-✅  GET    /api/v1/users/123/posts    nested resource
-
-❌  /api/getUsers   /api/createUser   /api/user (singular)   /api/Users (uppercase)
-```
-
-### HTTP Status Codes
-
-```
-200 OK             → GET / PUT / PATCH success
-201 Created        → POST success (include Location: /api/v1/users/123 header)
-204 No Content     → DELETE success
-400 Bad Request    → Malformed request / missing fields
-401 Unauthorized   → Missing or invalid authentication
-403 Forbidden      → Authenticated but not authorized
-404 Not Found      → Resource does not exist
-409 Conflict       → Duplicate resource (email already exists)
-422 Unprocessable  → Valid JSON, semantically invalid data
-429 Too Many Req   → Rate limit exceeded
-500 Internal       → Unhandled server error — NEVER expose stack traces
-```
-
-### Response Envelope
-
-```typescript
-interface ApiResponse<T> {
-  data: T;
-  meta?: Record<string, unknown>;
-}
-
-interface ApiError {
-  error: {
-    code: string; // machine-readable: "VALIDATION_ERROR"
-    message: string; // human-readable: "Email is already in use"
-    details?: Array<{ field: string; message: string }>; // field-level errors
-    requestId?: string; // for support/tracing
-  };
-}
-```
-
----
-
-## Pagination
-
-```typescript
-// ✅ Cursor-based — required for large/dynamic datasets
-// GET /api/v1/posts?cursor=eyJpZCI6MTAwfQ&limit=20
-const posts = await db.post.findMany({
-  where: { id: { lt: decodeCursor(req.query.cursor).id } },
-  orderBy: { id: 'desc' },
-  take: limit + 1, // fetch one extra to determine hasMore
-});
-const hasMore = posts.length > limit;
-if (hasMore) posts.pop();
-return { data: posts, meta: { hasMore, nextCursor: encodeCursor(posts.at(-1)) } };
-
-// Offset-based — only for small datasets where users need page jumping
-// GET /api/v1/posts?page=3&limit=20
-// ❌ TRAP: OFFSET 100000 scans and discards 100K rows — degrades badly at scale
-```
-
----
+## Mandatory Pre-Flight Context Inspection
+Before reading, generating, or refactoring code in the `api-patterns` 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).
 
-## Idempotency
 
-```typescript
-// POST /api/v1/payments with header: Idempotency-Key: <uuid>
-app.post('/api/v1/payments', async (req, res) => {
-  const key = req.headers['idempotency-key'];
-  if (!key) return res.status(400).json({ error: 'Missing Idempotency-Key' });
+## Activation Boundaries
+- **Activate when:** Use when designing, implementing, auditing, and hardening api patterns server logic, APIs, background jobs, and error boundaries.
+- **DO NOT activate when:** The task falls outside the `api-patterns` domain or is managed by a different dedicated specialist agent.
 
-  const cached = await redis.get(`idempotency:${key}`);
-  if (cached) return res.status(200).json(JSON.parse(cached));
 
-  const result = await processPayment(req.body);
-  await redis.set(`idempotency:${key}`, JSON.stringify(result), 'EX', 86400);
-  return res.status(201).json(result);
-});
-// GET, PUT, DELETE → naturally idempotent (safe to retry without a key)
-// POST, PATCH      → NOT idempotent by default — require Idempotency-Key
-```
+## 🔁 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 |
 
-## Webhooks
-
-```typescript
-// HMAC signature verification (always verify — never trust unsigned webhooks)
-import { createHmac, timingSafeEqual } from 'node:crypto';
-function verify(payload: string, signature: string, secret: string): boolean {
-  const expected = createHmac('sha256', secret).update(payload).digest('hex');
-  return timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
-}
-
-app.post('/webhooks', (req, res) => {
-  if (
-    !verify(JSON.stringify(req.body), req.headers['x-webhook-signature'] as string, WEBHOOK_SECRET)
-  )
-    return res.status(401).send('Invalid signature');
-  res.status(200).send('OK'); // respond immediately
-  processWebhookAsync(req.body); // process asynchronously
-});
-// Retry policy: 3 retries with exponential backoff (1s → 10s → 100s)
-// Include unique event ID in payload for receiver-side deduplication
-```
 
----
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
 
-## Versioning
+## Hallucination Traps (Read First)
+
+- ❌ JWT in URL query params → ✅ `Authorization: Bearer` header only. Query params get logged in server access logs.
+- ❌ Assuming JWT is encrypted → ✅ JWT is base64-encoded (NOT encrypted). Anyone can decode it. Never put secrets/PII in the payload.
+- ❌ Offset pagination on large tables → ✅ `OFFSET 100000` scans and discards 100K rows. Use cursor pagination for tables > 10K rows.
+- ❌ Verbs in REST URLs (`/api/getUsers`) → ✅ Nouns only (`GET /api/users`). HTTP method IS the verb.
+- ❌ `POST` is idempotent → ✅ `POST` is NOT idempotent — requires `Idempotency-Key` header for safe retries.
+- ❌ GraphQL has no security risks → ✅ Deeply nested queries are a DoS vector. Set max depth, query cost limits. Disable introspection in production.
+
+---
+
+## Protocol Selection Matrix
+
+| Protocol      | Use When                                                                              |
+| ------------- | ------------------------------------------------------------------------------------- |
+| **REST**      | Public APIs, 3rd-party consumers, standard CRUD, HTTP caching                         |
+| **GraphQL**   | Complex nested data, multiple clients, flexible queries, mobile bandwidth sensitivity |
+| **tRPC**      | Full-stack TypeScript (Next.js monorepo), shared types, no codegen                    |
+| **gRPC**      | Internal microservices, high-throughput, streaming, binary protocol                   |
+| **WebSocket** | Bidirectional real-time (chat, gaming, live collaboration)                            |
+| **SSE**       | Server-to-client streaming only (AI token streaming, live feeds)                      |
+
+---
+
+## REST Design
+
+### URL Conventions
+
+```
+✅  GET    /api/v1/users              list users
+✅  GET    /api/v1/users/123          get user by ID
+✅  POST   /api/v1/users              create user
+✅  PATCH  /api/v1/users/123          partial update
+✅  DELETE /api/v1/users/123          delete user
+✅  GET    /api/v1/users/123/posts    nested resource
+
+❌  /api/getUsers   /api/createUser   /api/user (singular)   /api/Users (uppercase)
+```
+
+### HTTP Status Codes
+
+```
+200 OK             → GET / PUT / PATCH success
+201 Created        → POST success (include Location: /api/v1/users/123 header)
+204 No Content     → DELETE success
+400 Bad Request    → Malformed request / missing fields
+401 Unauthorized   → Missing or invalid authentication
+403 Forbidden      → Authenticated but not authorized
+404 Not Found      → Resource does not exist
+409 Conflict       → Duplicate resource (email already exists)
+422 Unprocessable  → Valid JSON, semantically invalid data
+429 Too Many Req   → Rate limit exceeded
+500 Internal       → Unhandled server error — NEVER expose stack traces
+```
+
+### Response Envelope
+
+```typescript
+interface ApiResponse<T> {
+  data: T;
+  meta?: Record<string, unknown>;
+}
+
+interface ApiError {
+  error: {
+    code: string; // machine-readable: "VALIDATION_ERROR"
+    message: string; // human-readable: "Email is already in use"
+    details?: Array<{ field: string; message: string }>; // field-level errors
+    requestId?: string; // for support/tracing
+  };
+}
+```
+
+---
+
+## Pagination
+
+```typescript
+// ✅ Cursor-based — required for large/dynamic datasets
+// GET /api/v1/posts?cursor=eyJpZCI6MTAwfQ&limit=20
+const posts = await db.post.findMany({
+  where: { id: { lt: decodeCursor(req.query.cursor).id } },
+  orderBy: { id: 'desc' },
+  take: limit + 1, // fetch one extra to determine hasMore
+});
+const hasMore = posts.length > limit;
+if (hasMore) posts.pop();
+return { data: posts, meta: { hasMore, nextCursor: encodeCursor(posts.at(-1)) } };
+
+// Offset-based — only for small datasets where users need page jumping
+// GET /api/v1/posts?page=3&limit=20
+// ❌ TRAP: OFFSET 100000 scans and discards 100K rows — degrades badly at scale
+```
+
+---
+
+## Idempotency
+
+```typescript
+// POST /api/v1/payments with header: Idempotency-Key: <uuid>
+app.post('/api/v1/payments', async (req, res) => {
+  const key = req.headers['idempotency-key'];
+  if (!key) return res.status(400).json({ error: 'Missing Idempotency-Key' });
+
+  const cached = await redis.get(`idempotency:${key}`);
+  if (cached) return res.status(200).json(JSON.parse(cached));
+
+  const result = await processPayment(req.body);
+  await redis.set(`idempotency:${key}`, JSON.stringify(result), 'EX', 86400);
+  return res.status(201).json(result);
+});
+// GET, PUT, DELETE → naturally idempotent (safe to retry without a key)
+// POST, PATCH      → NOT idempotent by default — require Idempotency-Key
+```
+
+---
+
+## Webhooks
+
+```typescript
+// HMAC signature verification (always verify — never trust unsigned webhooks)
+import { createHmac, timingSafeEqual } from 'node:crypto';
+function verify(payload: string, signature: string, secret: string): boolean {
+  const expected = createHmac('sha256', secret).update(payload).digest('hex');
+  return timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
+}
+
+app.post('/webhooks', (req, res) => {
+  if (
+    !verify(JSON.stringify(req.body), req.headers['x-webhook-signature'] as string, WEBHOOK_SECRET)
+  )
+    return res.status(401).send('Invalid signature');
+  res.status(200).send('OK'); // respond immediately
+  processWebhookAsync(req.body); // process asynchronously
+});
+// Retry policy: 3 retries with exponential backoff (1s → 10s → 100s)
+// Include unique event ID in payload for receiver-side deduplication
+```
+
+---
+
+## Versioning
+
+```
+URL path (recommended):  /api/v1/users      → simplest, most common, cache-friendly
+Header:                  Accept: application/vnd.api.v1+json
+Query param:             /api/users?version=1 → messy, avoid
+
+Rules:
+  - Start at v1, never v0
+  - Breaking changes = new major version (v2)
+  - Non-breaking additions (new optional fields) do NOT need a version bump
+  - Deprecate before removing — give consumers 6+ months notice
+```
+
+---
+
+## Rate Limiting
+
+```
+Strategy         How                          When
+Token bucket   → Burst allowed, refills       Most APIs (recommended)
+Sliding window → Smooth distribution          Strict fairness required
+Fixed window   → Simple counter per period    Basic needs only
+
+Response headers to always include:
+  X-RateLimit-Limit        (max requests in window)
+  X-RateLimit-Remaining    (requests left)
+  X-RateLimit-Reset        (Unix timestamp when limit resets)
+  Retry-After              (seconds to wait on 429)
+```
+
+---
+
+## GraphQL Security
+
+```
+Protect against:
+  Depth attacks    → Set max query depth (typically 7–10)
+  Cost attacks     → Calculate query complexity score, reject > threshold
+  Batch abuse      → Limit batch size / alias count
+  Introspection    → Disable in production (exposes full schema to attackers)
+```
+
+---
+
+## Authentication Selection
+
+| Pattern                                         | Best For                               |
+| ----------------------------------------------- | -------------------------------------- |
+| **JWT** (short-lived access + httpOnly refresh) | Stateless services, microservices      |
+| **Session**                                     | Traditional server-rendered apps       |
+| **OAuth 2.0 / OIDC**                            | Third-party login, delegated access    |
+| **API Key**                                     | Server-to-server, public API consumers |
+| **Passkey (WebAuthn)**                          | Modern passwordless (2026+)            |
 
-```
-URL path (recommended):  /api/v1/users      → simplest, most common, cache-friendly
-Header:                  Accept: application/vnd.api.v1+json
-Query param:             /api/users?version=1 → messy, avoid
-
-Rules:
-  - Start at v1, never v0
-  - Breaking changes = new major version (v2)
-  - Non-breaking additions (new optional fields) do NOT need a version bump
-  - Deprecate before removing — give consumers 6+ months notice
-```
+## 🚨 Edge-Case & Failure Mode Matrix
 
----
+| 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 |
 
-## Rate Limiting
 
-```
-Strategy         How                          When
-Token bucket   → Burst allowed, refills       Most APIs (recommended)
-Sliding window → Smooth distribution          Strict fairness required
-Fixed window   → Simple counter per period    Basic needs only
-
-Response headers to always include:
-  X-RateLimit-Limit        (max requests in window)
-  X-RateLimit-Remaining    (requests left)
-  X-RateLimit-Reset        (Unix timestamp when limit resets)
-  Retry-After              (seconds to wait on 429)
-```
+## 🏛️ Tribunal Verification & Guardrails
 
----
+**Active Reviewers:** `logic-reviewer` · `security-auditor` · `api-architect` · `resilience-reviewer`
+**Slash Command:** `/review` or `/tribunal-full`
 
-## GraphQL Security
+### 🔬 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
 ```
-Protect against:
-  Depth attacks    → Set max query depth (typically 7–10)
-  Cost attacks     → Calculate query complexity score, reject > threshold
-  Batch abuse      → Limit batch size / alias count
-  Introspection    → Disable in production (exposes full schema to attackers)
+✅ Are all inputs and boundary payloads validated against schemas (Zod/Pydantic)?
+✅ Are SQL and database queries parameterized with zero string concatenation?
+✅ Are error boundaries and timeout/retry policies explicitly declared?
+✅ Are authentication and object-level authorization (IDOR/BOLA) checked before business logic?
+✅ Did I verify that imported dependencies exist in package manifests?
 ```
 
----
-
-## Authentication Selection
-
-| Pattern                                         | Best For                               |
-| ----------------------------------------------- | -------------------------------------- |
-| **JWT** (short-lived access + httpOnly refresh) | Stateless services, microservices      |
-| **Session**                                     | Traditional server-rendered apps       |
-| **OAuth 2.0 / OIDC**                            | Third-party login, delegated access    |
-| **API Key**                                     | Server-to-server, public API consumers |
-| **Passkey (WebAuthn)**                          | Modern passwordless (2026+)            |
+### 🛑 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.