tribunal-kit 9.0.2 → 9.2.3

package/.agents/skills/webgpu-performance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: webgpu-performance
-description: Use when High-performance browser graphics and compute mastery. Transitioning from WebGL to WebGPU API, WGSL compute shaders, explicit GPU memory management, and browser-side tensor calculations.
+description: "Use when High-performance browser graphics and compute mastery. Transitioning from WebGL to WebGPU API, WGSL compute shaders, explicit GPU memory management, and browser-side tensor calculations."
 version: 5.0.0
 last-updated: 2026-09-13
 skills:
@@ -15,42 +15,12 @@ scripts-binding:
 
 # WebGPU Performance Mastery
 
-## Mandatory Pre-Flight Context Inspection
-
-Before generating, refactoring, or reviewing code in the `webgpu-performance` 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 High-performance browser graphics and compute mastery. Transitioning from WebGL to WebGPU API, WGSL compute shaders, explicit GPU memory management, and browser-side tensor calculations.
-- **DO NOT activate when:** The task falls outside the `webgpu-performance` domain or is managed by a different dedicated specialist.
-
-## 🔁 Multi-Pass Execution Protocol
-
-Execute all non-trivial tasks through this 7-pass cognitive loop:
-
-| Pass | Phase | Core Action |
-|:---|:---|:---|
-| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
-| **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
-| **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
-| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
-| **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
-| **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
-| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
-
 ---
 
 ## 🛠️ Technical Architecture & Reference Recipes
 
 ---
 
-
 ## 1. Core Principles
 
 - **Explicit > Implicit:** Unlike WebGL, WebGPU doesn't hide state. You must explicitly configure Pipelines, BindGroups, and CommandEncoders.
@@ -116,48 +86,3 @@ Before submitting code, ensure:
 1. Devices and adapters are properly null-checked.
 2. WGSL workgroup sizes align with the dispatch sizes dynamically.
 3. GPUBuffers used for compute have `GPUBufferUsage.STORAGE` flags.
-
----
-
-## 🚨 Edge-Case & Failure Mode Matrix
-
-| Scenario | Risk | Mitigation Strategy |
-|:---|:---|:---|
-| **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 |
-|:---|:---|:---|
-| **Hallucinated Tool Capabilities** | Assuming an external library or CLI command exists without verification | Run a verification check or verify package.json before referencing tools |
-| **Premature Completion Claim** | Declaring a task finished because code was generated without verification | Execute tests, linters, or terminal commands to provide concrete proof |
-| **Context Bloat Dumping** | Pasting entire multi-thousand-line files into prompt context | Extract targeted excerpts, symbols, and signatures to preserve tokens |
-
----
-
-## 🏛️ Tribunal Verification & Guardrails
-
-**Active Reviewers:** `orchestrator` · `agent-organizer` · `logic-reviewer`
-**Slash Command:** `/review` or `/tribunal-full`
-
-### ✅ Pre-Flight Self-Audit Checklist
-
-```
-✅ Did I deconstruct the root objective before proposing architecture?
-✅ Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
-✅ Did I avoid over-engineering and select the simplest effective pattern?
-✅ Did I verify assumptions with concrete file reads instead of speculation?
-✅ Did I establish measurable verification criteria before completion?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/whimsy-injector/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: whimsy-injector
-description: Use when Micro-delight generator for frontend interfaces. Suggests and implements subtle animations, playful transitions, and interaction polish across any frontend stack.
+description: "Use when Micro-delight generator for frontend interfaces. Suggests and implements subtle animations, playful transitions, and interaction polish across any frontend stack."
 version: 5.0.0
 last-updated: 2026-09-13
 skills:
@@ -16,42 +16,12 @@ scripts-binding:
 
 # Whimsy Injector Skill — Micro-Delight Generator
 
-## Mandatory Pre-Flight Context Inspection
-
-Before generating, refactoring, or reviewing code in the `whimsy-injector` 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 Micro-delight generator for frontend interfaces. Suggests and implements subtle animations, playful transitions, and interaction polish across any frontend stack.
-- **DO NOT activate when:** The task falls outside the `whimsy-injector` domain or is managed by a different dedicated specialist.
-
-## 🔁 Multi-Pass Execution Protocol
-
-Execute all non-trivial tasks through this 7-pass cognitive loop:
-
-| Pass | Phase | Core Action |
-|:---|:---|:---|
-| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
-| **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
-| **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
-| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
-| **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
-| **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
-| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
-
 ---
 
 ## 🛠️ Technical Architecture & Reference Recipes
 
 ---
 
-
 ## When to Activate
 
 - During `/enhance` or `/ui-ux-pro-max` workflows as a polish pass.
@@ -333,48 +303,3 @@ Every file with animations MUST include:
 - **Mark experimental APIs** with `// VERIFY: [API] — check browser support for your target`.
 - **Never suggest animations that cause layout shift** — enforce `transform` and `opacity` only.
 - **Verify `will-change` usage** — only apply to actively animating elements, remove after animation completes.
-
----
-
-## 🚨 Edge-Case & Failure Mode Matrix
-
-| Scenario | Risk | Mitigation Strategy |
-|:---|:---|:---|
-| **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`
-
-### ✅ 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 focus, contrast) 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/.agents/skills/workflow-optimizer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-optimizer
-description: Use when Analyzes agent tool-calling patterns and task execution efficiency to suggest process improvements.
+description: "Use when Analyzes agent tool-calling patterns and task execution efficiency to suggest process improvements."
 version: 5.0.0
 last-updated: 2026-09-13
 skills:
@@ -16,42 +16,12 @@ scripts-binding:
 
 # Workflow Optimizer Skill
 
-## Mandatory Pre-Flight Context Inspection
-
-Before generating, refactoring, or reviewing code in the `workflow-optimizer` 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 Analyzes agent tool-calling patterns and task execution efficiency to suggest process improvements.
-- **DO NOT activate when:** The task falls outside the `workflow-optimizer` domain or is managed by a different dedicated specialist.
-
-## 🔁 Multi-Pass Execution Protocol
-
-Execute all non-trivial tasks through this 7-pass cognitive loop:
-
-| Pass | Phase | Core Action |
-|:---|:---|:---|
-| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
-| **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
-| **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
-| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
-| **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
-| **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
-| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
-
 ---
 
 ## 🛠️ Technical Architecture & Reference Recipes
 
 ---
 
-
 ## When to Activate
 
 - When a task takes significantly more tool calls than expected.
@@ -216,48 +186,3 @@ Before analyzing, check for these common quick wins:
 - **Recommendations must reference real tools** — only suggest tools available in the current environment.
 - **Never fabricate efficiency scores** — always calculate from actual vs optimal counts.
 - **Acknowledge uncertainty**: "Cannot determine if calls 3-5 had data dependency — may be correctly sequential."
-
----
-
-## 🚨 Edge-Case & Failure Mode Matrix
-
-| Scenario | Risk | Mitigation Strategy |
-|:---|:---|:---|
-| **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 |
-|:---|:---|:---|
-| **Hallucinated Tool Capabilities** | Assuming an external library or CLI command exists without verification | Run a verification check or verify package.json before referencing tools |
-| **Premature Completion Claim** | Declaring a task finished because code was generated without verification | Execute tests, linters, or terminal commands to provide concrete proof |
-| **Context Bloat Dumping** | Pasting entire multi-thousand-line files into prompt context | Extract targeted excerpts, symbols, and signatures to preserve tokens |
-
----
-
-## 🏛️ Tribunal Verification & Guardrails
-
-**Active Reviewers:** `orchestrator` · `agent-organizer` · `logic-reviewer`
-**Slash Command:** `/review` or `/tribunal-full`
-
-### ✅ Pre-Flight Self-Audit Checklist
-
-```
-✅ Did I deconstruct the root objective before proposing architecture?
-✅ Did I identify dependencies, bottlenecks, and parallelizable sub-tasks?
-✅ Did I avoid over-engineering and select the simplest effective pattern?
-✅ Did I verify assumptions with concrete file reads instead of speculation?
-✅ Did I establish measurable verification criteria before completion?
-```
-
-### 🛑 Verification-Before-Completion (VBC) Protocol
-
-**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
-- ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
-- ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.

package/.agents/skills/zero-trust-passkeys/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: zero-trust-passkeys
-description: Use when Modern passwordless authentication using WebAuthn, FIDO2 biometric passkeys, SimpleWebAuthn v13+, Conditional UI (Passkey Autofill), and Zero-Trust security.
+description: "Use when Modern passwordless authentication using WebAuthn, FIDO2 biometric passkeys, SimpleWebAuthn v13+, Conditional UI (Passkey Autofill), and Zero-Trust security."
 version: 5.0.0
 last-updated: 2026-09-13
 skills:
@@ -16,35 +16,6 @@ scripts-binding:
 
 # Zero-Trust Passkeys & WebAuthn (SimpleWebAuthn v13+)
 
-## Mandatory Pre-Flight Context Inspection
-
-Before generating, refactoring, or reviewing code in the `zero-trust-passkeys` 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 Modern passwordless authentication using WebAuthn, FIDO2 biometric passkeys, SimpleWebAuthn v13+, Conditional UI (Passkey Autofill), and Zero-Trust security.
-- **DO NOT activate when:** The task falls outside the `zero-trust-passkeys` domain or is managed by a different dedicated specialist.
-
-## 🔁 Multi-Pass Execution Protocol
-
-Execute all non-trivial tasks through this 7-pass cognitive loop:
-
-| Pass | Phase | Core Action |
-|:---|:---|:---|
-| **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
-| **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
-| **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
-| **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
-| **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
-| **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
-| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
-
 ---
 
 ## 🛠️ Technical Architecture & Reference Recipes
@@ -109,48 +80,3 @@ export async function verifyPasskeyAuth(
   return verification.verified;
 }
 ```
-
----
-
-## 🚨 Edge-Case & Failure Mode Matrix
-
-| Scenario | Risk | Mitigation Strategy |
-|:---|:---|:---|
-| **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 |
-|:---|:---|:---|
-| **Hardcoded Secret Pattern** | Committing API keys, tokens, or private salts into source code | Load credentials strictly via runtime environment variables and secret stores |
-| **Prompt Injection Surface** | Directly concatenating untrusted user input into LLM system prompts | Wrap user content in isolated delimiters and strip injection control sequences |
-| **Missing Authorization Check** | Relying only on authentication token presence without checking tenant/object RBAC | Verify user permissions against the specific target record ID before mutation |
-
----
-
-## 🏛️ Tribunal Verification & Guardrails
-
-**Active Reviewers:** `security-auditor` · `penetration-tester` · `backend-security-expert`
-**Slash Command:** `/review` or `/tribunal-full`
-
-### ✅ Pre-Flight Self-Audit Checklist
-
-```
-✅ Are user inputs sanitized and treated as untrusted at system boundaries?
-✅ Are secrets loaded strictly via environment variables with zero hardcoding?
-✅ Is least-privilege enforcement active on APIs, tokens, and storage buckets?
-✅ Are prompt-injection delimiters and sanitizers wrapped around LLM inputs?
-✅ Did I verify encryption in transit and at rest for sensitive customer data?
-```
-
-### 🛑 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/.codex-plugin/plugin.json

@@ -30,11 +30,7 @@
     "longDescription": "Use Tribunal Kit to govern coding agents through Socratic brainstorming, bite-sized implementation planning, strict test-driven development, out-of-band context isolation, 28-specialist review waves, and persistent Case Law memory.",
     "developerName": "Harmitx7",
     "category": "Developer Tools",
-    "capabilities": [
-      "Interactive",
-      "Read",
-      "Write"
-    ],
+    "capabilities": ["Interactive", "Read", "Write"],
     "defaultPrompt": [
       "Let's design and implement a new feature using Tribunal SDD.",
       "Run a full Tribunal code audit on this repository."

package/.kimi-plugin/plugin.json

@@ -28,11 +28,7 @@
     "shortDescription": "28-Specialist Review Waves & Subagent-Driven Development (SDD) Engine",
     "longDescription": "Tribunal Kit provides institutional-grade code review, anti-hallucination guardrails, Subagent-Driven Development (SDD), and automated testing pipelines for AI coding agents.",
     "developerName": "Harmitx7",
-    "capabilities": [
-      "Interactive",
-      "Read",
-      "Write"
-    ],
+    "capabilities": ["Interactive", "Read", "Write"],
     "websiteURL": "https://github.com/Harmitx7/tribunal-kit"
   }
 }

package/.opencode/INSTALL.md

@@ -37,5 +37,6 @@ use skill tool to load verification-before-completion
 ## Subagent-Driven Development (SDD)
 
 OpenCode delegates tasks to subagents via the `task` tool:
+
 - Implementers execute tasks following `.tribunal/sdd/<plan>/task-<N>-brief.md`.
 - Reviewers evaluate diffs via `tk sdd diff` out-of-band.

package/.opencode/plugins/tribunal.js

@@ -11,7 +11,7 @@ import { fileURLToPath } from 'url';
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 
-const extractAndStripFrontmatter = (content) => {
+const extractAndStripFrontmatter = content => {
   const match = content.match(/^---\n([\s\S]*?)\n---\n([\s\S]*)$/);
   if (!match) return { frontmatter: {}, content };
 
@@ -23,7 +23,10 @@ const extractAndStripFrontmatter = (content) => {
     const colonIdx = line.indexOf(':');
     if (colonIdx > 0) {
       const key = line.slice(0, colonIdx).trim();
-      const value = line.slice(colonIdx + 1).trim().replace(/^["']|["']$/g, '');
+      const value = line
+        .slice(colonIdx + 1)
+        .trim()
+        .replace(/^["']|["']$/g, '');
       frontmatter[key] = value;
     }
   }
@@ -47,7 +50,8 @@ export const TribunalPlugin = async ({ client: _client, directory: _directory }
       const { content } = extractAndStripFrontmatter(raw);
       rulesContent = content;
     } else {
-      rulesContent = '# Tribunal Kit Master Governance Active\nEnforce strict TDD, out-of-band reviews, and 28-specialist waves.';
+      rulesContent =
+        '# Tribunal Kit Master Governance Active\nEnforce strict TDD, out-of-band reviews, and 28-specialist waves.';
     }
 
     const toolMapping = `**Tool Mapping for OpenCode:**
@@ -76,7 +80,7 @@ ${toolMapping}
   };
 
   return {
-    config: async (config) => {
+    config: async config => {
       config.skills = config.skills || {};
       config.skills.paths = config.skills.paths || [];
       if (!config.skills.paths.includes(tribunalSkillsDir)) {
@@ -90,11 +94,16 @@ ${toolMapping}
       const firstUser = output.messages.find(m => m.info && m.info.role === 'user');
       if (!firstUser || !firstUser.parts || !firstUser.parts.length) return;
 
-      if (firstUser.parts.some(p => p.type === 'text' && p.text && p.text.includes('EXTREMELY_IMPORTANT'))) return;
+      if (
+        firstUser.parts.some(
+          p => p.type === 'text' && p.text && p.text.includes('EXTREMELY_IMPORTANT'),
+        )
+      )
+        return;
 
       const ref = firstUser.parts[0];
       firstUser.parts.unshift({ ...ref, type: 'text', text: bootstrap });
-    }
+    },
   };
 };
 

package/.pi/extensions/tribunal.ts

@@ -1,41 +1,41 @@
-import { readFileSync, existsSync } from "node:fs";
-import { dirname, resolve } from "node:path";
-import { fileURLToPath } from "node:url";
+import { readFileSync, existsSync } from 'node:fs';
+import { dirname, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
 
 export interface ExtensionAPI {
   on(event: string, handler: (payload?: any) => Promise<any> | any): void;
 }
 
-const EXTREMELY_IMPORTANT_MARKER = "<EXTREMELY_IMPORTANT>";
-const BOOTSTRAP_MARKER = "tribunal-kit:master-governance bootstrap for pi";
+const EXTREMELY_IMPORTANT_MARKER = '<EXTREMELY_IMPORTANT>';
+const BOOTSTRAP_MARKER = 'tribunal-kit:master-governance bootstrap for pi';
 
 const extensionDir = dirname(fileURLToPath(import.meta.url));
-const packageRoot = resolve(extensionDir, "../..");
-const skillsDir = resolve(packageRoot, ".agent", "skills");
-const rulesPath = resolve(packageRoot, ".agent", "rules", "GEMINI.md");
+const packageRoot = resolve(extensionDir, '../..');
+const skillsDir = resolve(packageRoot, '.agent', 'skills');
+const rulesPath = resolve(packageRoot, '.agent', 'rules', 'GEMINI.md');
 
 let cachedBootstrap: string | null | undefined;
 
 export default function tribunalPiExtension(pi: ExtensionAPI) {
   let injectBootstrap = true;
 
-  pi.on("resources_discover", async () => ({
+  pi.on('resources_discover', async () => ({
     skillPaths: [skillsDir],
   }));
 
-  pi.on("session_start", async () => {
+  pi.on('session_start', async () => {
     injectBootstrap = true;
   });
 
-  pi.on("session_compact", async () => {
+  pi.on('session_compact', async () => {
     injectBootstrap = true;
   });
 
-  pi.on("agent_end", async () => {
+  pi.on('agent_end', async () => {
     injectBootstrap = false;
   });
 
-  pi.on("context", async (event: any) => {
+  pi.on('context', async (event: any) => {
     if (!injectBootstrap) return;
     if (event?.messages?.some(messageContainsBootstrap)) return;
 
@@ -43,8 +43,8 @@ export default function tribunalPiExtension(pi: ExtensionAPI) {
     if (!bootstrap) return;
 
     const bootstrapMessage = {
-      role: "user" as const,
-      content: [{ type: "text" as const, text: bootstrap }],
+      role: 'user' as const,
+      content: [{ type: 'text' as const, text: bootstrap }],
       timestamp: Date.now(),
     };
 
@@ -52,11 +52,7 @@ export default function tribunalPiExtension(pi: ExtensionAPI) {
     const insertAt = firstNonCompactionSummaryIndex(messages);
 
     return {
-      messages: [
-        ...messages.slice(0, insertAt),
-        bootstrapMessage,
-        ...messages.slice(insertAt),
-      ],
+      messages: [...messages.slice(0, insertAt), bootstrapMessage, ...messages.slice(insertAt)],
     };
   });
 }
@@ -65,12 +61,13 @@ function getBootstrapContent(): string | null {
   if (cachedBootstrap !== undefined) return cachedBootstrap;
 
   try {
-    let body = "";
+    let body = '';
     if (existsSync(rulesPath)) {
-      const raw = readFileSync(rulesPath, "utf8");
+      const raw = readFileSync(rulesPath, 'utf8');
       body = stripFrontmatter(raw);
     } else {
-      body = "# Tribunal Kit Master Governance Active\nEnforce strict TDD and 28-specialist reviewer waves.";
+      body =
+        '# Tribunal Kit Master Governance Active\nEnforce strict TDD and 28-specialist reviewer waves.';
     }
 
     cachedBootstrap = `${EXTREMELY_IMPORTANT_MARKER}
@@ -111,14 +108,14 @@ Subagent-Driven Development (SDD):
 
 function messageContainsBootstrap(message: unknown): boolean {
   const content = (message as { content?: unknown })?.content;
-  if (typeof content === "string") return content.includes(BOOTSTRAP_MARKER);
+  if (typeof content === 'string') return content.includes(BOOTSTRAP_MARKER);
   if (!Array.isArray(content)) return false;
-  return content.some((part) => {
+  return content.some(part => {
     return (
       part &&
-      typeof part === "object" &&
-      (part as { type?: unknown }).type === "text" &&
-      typeof (part as { text?: unknown }).text === "string" &&
+      typeof part === 'object' &&
+      (part as { type?: unknown }).type === 'text' &&
+      typeof (part as { text?: unknown }).text === 'string' &&
       (part as { text: string }).text.includes(BOOTSTRAP_MARKER)
     );
   });
@@ -126,7 +123,7 @@ function messageContainsBootstrap(message: unknown): boolean {
 
 function firstNonCompactionSummaryIndex(messages: unknown[]): number {
   let index = 0;
-  while ((messages[index] as { role?: unknown } | undefined)?.role === "compactionSummary") {
+  while ((messages[index] as { role?: unknown } | undefined)?.role === 'compactionSummary') {
     index += 1;
   }
   return index;

package/AGENTS.md

@@ -52,21 +52,22 @@ Am I importing a package/method that exists?
 
 When you detect code or design requests, apply the specialist agent profile:
 
-| Domain                       | Specialist              |
-| ---------------------------- | ----------------------- |
-| API / server / backend       | `backend-specialist`    |
-| React / Next.js / UI         | `frontend-specialist`   |
-| Database / schema / SQL      | `database-architect`    |
-| Python / FastAPI / Django    | `python-pro`            |
-| Mobile (RN / Flutter)        | `mobile-developer`      |
-| Debugging / errors           | `debugger`              |
-| Security / vulnerabilities   | `security-auditor`      |
-| Performance / optimization   | `performance-optimizer` |
-| DevOps / CI-CD / Docker      | `devops-engineer`       |
-| Test generation              | `test-engineer`         |
-| Architecture / planning      | `project-planner`       |
+| Domain                     | Specialist              |
+| -------------------------- | ----------------------- |
+| API / server / backend     | `backend-specialist`    |
+| React / Next.js / UI       | `frontend-specialist`   |
+| Database / schema / SQL    | `database-architect`    |
+| Python / FastAPI / Django  | `python-pro`            |
+| Mobile (RN / Flutter)      | `mobile-developer`      |
+| Debugging / errors         | `debugger`              |
+| Security / vulnerabilities | `security-auditor`      |
+| Performance / optimization | `performance-optimizer` |
+| DevOps / CI-CD / Docker    | `devops-engineer`       |
+| Test generation            | `test-engineer`         |
+| Architecture / planning    | `project-planner`       |
 
 Always announce the active specialist:
+
 ```
 🤖 Applying knowledge of @[agent-name]...
 ```
@@ -84,6 +85,7 @@ Always announce the active specialist:
 ## 4. Skills & Tool Integration
 
 Tribunal Kit provides 185 deep skill modules located in:
+
 - `./skills/<skill-name>/SKILL.md`
 - `./.agent/skills/<skill-name>/SKILL.md`
 - `./.agents/skills/<skill-name>/SKILL.md`