tribunal-kit 4.5.1 → 4.6.1

package/package.json

@@ -1,94 +1,94 @@
-{
-    "name": "tribunal-kit",
-    "version": "4.5.1",
-    "description": "Anti-Hallucination AI Agent Kit — 40 specialist agents, 32 slash commands, 16 parallel Tribunal reviewers, Performance Swarm engine, Supreme Court case law pipeline, and long-running agent harness.",
-    "keywords": [
-        "ai",
-        "ai-agent",
-        "long-running-agents",
-        "agent",
-        "agents",
-        "multi-agent",
-        "agentic",
-        "swarm",
-        "orchestration",
-        "llm",
-        "anti-hallucination",
-        "hallucination",
-        "code-review",
-        "code-quality",
-        "cursor",
-        "cursor-rules",
-        "cursorrules",
-        "windsurf",
-        "copilot",
-        "cline",
-        "gemini",
-        "antigravity",
-        "tribunal",
-        "mcp",
-        "model-context-protocol",
-        "cli",
-        "devtools",
-        "ai-coding",
-        "autonomous-agents",
-        "coding-assistant",
-        "automation"
-    ],
-    "homepage": "https://github.com/Harmitx7/tribunal-kit",
-    "repository": {
-        "type": "git",
-        "url": "git+https://github.com/Harmitx7/tribunal-kit.git"
-    },
-    "license": "MIT",
-    "bin": {
-        "tribunal-kit": "bin/wrapper.js",
-        "tk": "bin/wrapper.js"
-    },
-    "files": [
-        "bin/",
-        "scripts/",
-        ".agent/",
-        "README.md",
-        "LICENSE",
-        "mcp_config.json"
-    ],
-    "engines": {
-        "node": ">=18.0.0"
-    },
-    "scripts": {
-        "test": "npm run validate-payload && jest --coverage",
-        "test:unit": "jest test/unit --coverage",
-        "test:integration": "jest test/integration --coverage",
-        "preversion": "node scripts/sync-version.js",
-        "version": "node scripts/changelog.js && git add CHANGELOG.md",
-        "changelog": "node scripts/changelog.js",
-        "changelog:preview": "node scripts/changelog.js --preview",
-        "sync": "node scripts/sync-version.js",
-        "validate-payload": "node scripts/validate-payload.js",
-        "build": "echo 'No build step required for this project'"
-    },
-    "devDependencies": {
-        "eslint": "^9.1.1",
-        "jest": "^25.0.0",
-        "typescript": "^5.4.5"
-    },
-    "optionalDependencies": {
-        "@tribunal-kit/core-darwin-arm64": "^4.5.1",
-        "@tribunal-kit/core-darwin-x64": "^4.5.1",
-        "@tribunal-kit/core-linux-arm64": "^4.5.1",
-        "@tribunal-kit/core-linux-x64": "^4.5.1",
-        "@tribunal-kit/core-win32-arm64": "^4.5.1",
-        "@tribunal-kit/core-win32-x64": "^4.5.1"
-    },
-    "jest": {
-        "testMatch": [
-            "**/test/**/*.test.js"
-        ],
-        "testEnvironment": "node",
-        "coverageDirectory": "coverage",
-        "collectCoverageFrom": [
-            "bin/**/*.js"
-        ]
-    }
-}
+{
+  "name": "tribunal-kit",
+  "version": "4.6.1",
+  "description": "Anti-Hallucination AI Agent Kit — 43 specialist agents, 32 slash commands, 19 parallel Tribunal reviewers, Performance Swarm engine, Supreme Court case law pipeline, and long-running agent harness.",
+  "keywords": [
+    "ai",
+    "ai-agent",
+    "long-running-agents",
+    "agent",
+    "agents",
+    "multi-agent",
+    "agentic",
+    "swarm",
+    "orchestration",
+    "llm",
+    "anti-hallucination",
+    "hallucination",
+    "code-review",
+    "code-quality",
+    "cursor",
+    "cursor-rules",
+    "cursorrules",
+    "windsurf",
+    "copilot",
+    "cline",
+    "gemini",
+    "antigravity",
+    "tribunal",
+    "mcp",
+    "model-context-protocol",
+    "cli",
+    "devtools",
+    "ai-coding",
+    "autonomous-agents",
+    "coding-assistant",
+    "automation"
+  ],
+  "homepage": "https://github.com/Harmitx7/tribunal-kit",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Harmitx7/tribunal-kit.git"
+  },
+  "license": "MIT",
+  "bin": {
+    "tribunal-kit": "bin/wrapper.js",
+    "tk": "bin/wrapper.js"
+  },
+  "files": [
+    "bin/",
+    "scripts/",
+    ".agent/",
+    "README.md",
+    "LICENSE",
+    "mcp_config.json"
+  ],
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "scripts": {
+    "test": "npm run validate-payload && jest --coverage",
+    "test:unit": "jest test/unit --coverage",
+    "test:integration": "jest test/integration --coverage",
+    "preversion": "node scripts/sync-version.js",
+    "version": "node scripts/changelog.js && git add CHANGELOG.md",
+    "changelog": "node scripts/changelog.js",
+    "changelog:preview": "node scripts/changelog.js --preview",
+    "sync": "node scripts/sync-version.js",
+    "validate-payload": "node scripts/validate-payload.js",
+    "build": "echo 'No build step required for this project'"
+  },
+  "devDependencies": {
+    "eslint": "^9.1.1",
+    "jest": "^25.0.0",
+    "typescript": "^5.4.5"
+  },
+  "optionalDependencies": {
+    "@tribunal-kit/core-darwin-arm64": "^4.5.1",
+    "@tribunal-kit/core-darwin-x64": "^4.5.1",
+    "@tribunal-kit/core-linux-arm64": "^4.5.1",
+    "@tribunal-kit/core-linux-x64": "^4.5.1",
+    "@tribunal-kit/core-win32-arm64": "^4.5.1",
+    "@tribunal-kit/core-win32-x64": "^4.5.1"
+  },
+  "jest": {
+    "testMatch": [
+      "**/test/**/*.test.js"
+    ],
+    "testEnvironment": "node",
+    "coverageDirectory": "coverage",
+    "collectCoverageFrom": [
+      "bin/**/*.js"
+    ]
+  }
+}

package/.agent/GEMINI.md

@@ -1,121 +0,0 @@
----
-trigger: always_on
----
-
-# HALLUCINATION-GUARD GEMINI.md
-
-This file defines the AI behaviour for the Anti-Hallucination Tribunal system.
-Works with Cursor, Windsurf, Antigravity, and any AI IDE that supports `.agent` folders.
-
----
-
-## CRITICAL: AGENT & SKILL PROTOCOL
-
-Before responding to ANY complex or ambiguous coding request, you MUST:
-1. **Invoke the Pre-Router:** Read `.agent/skills/intelligent-routing/SKILL.md` to accurately determine the domain and required skills. Do NOT rely on guessing.
-2. **Select the correct reviewer agents** based on the Pre-Router's output.
-3. **Announce** which skills and agents are active.
-4. **Apply** the Tribunal workflow to your code generation.
-
----
-
-## BASIC REQUEST CLASSIFICATION (Fallback)
-
-If the request is extremely simple, you may use this fallback table. Otherwise, rely on the `intelligent-routing` Pre-Router.
-
-|Request Type|Trigger Words|Tribunal Agents Activated|
-|---|---|---|
-|**General Code**|"write", "create", "generate"|Logic + Security (default)|
-|**Backend / API**|"api", "server", "endpoint", "route"|Logic + Security + Dependency + Types|
-|**Database / SQL**|"query", "database", "sql", "prisma", "orm"|Logic + Security + SQL|
-|**React / Frontend**|"component", "hook", "react", "next", "ui"|Logic + Security + Frontend + Types|
-|**Performance**|"optimize", "speed", "bottleneck", "slow"|Logic + Performance|
-|**Performance (Full-Stack)**|"latency", "throughput", "end-to-end perf"|vitals-reviewer + db-latency-auditor + throughput-optimizer|
-|**Tests**|"test", "spec", "coverage", "vitest", "jest"|Logic + TestCoverage|
-|**AI / LLM**|"openai", "anthropic", "llm", "embedding", "prompt"|Logic + Security + AI-Code-Reviewer|
-|**Accessibility**|"a11y", "wcag", "aria", "accessibility"|Logic + Accessibility-Reviewer|
-|**Mobile**|"mobile", "react native", "flutter"|Logic + Security + Mobile-Reviewer|
-|**Design / UX**|"design", "trend", "palette", "inspiration", "ux audit"|`trend-researcher` + `ui-ux-researcher`|
-|**API Testing**|"test api", "endpoint test", "api flow"|`api-tester` workflow|
-|**Performance**|"benchmark", "lighthouse", "bundle size", "latency"|`performance-benchmarker` workflow|
-|**Test Analysis**|"test failed", "analyze tests", "what broke"|`test-result-analyzer`|
-|**All Domains**|"/tribunal-full" or "audit everything"|ALL 14 agents|
-|**Review Only**|"/review", "check this", "audit"|All relevant agents, no Maker|
-|**Swarm / Multi-Domain**|"/swarm", "multiple agents", "parallel tasks"|`supervisor-agent` → dispatches to specialist Workers|
-
----
-
-## TIER 0: UNIVERSAL RULES (Always Active)
-
-### Anti-Hallucination Constraints (MANDATORY)
-Every code response MUST:
-1. **Only reference real imports** — never invent library methods or package names
-2. **Ground in context** — if no context is provided, say what assumptions are being made
-3. **Be iterative** — generate one function/feature at a time, not entire apps
-4. **Flag uncertainty** — when unsure, write `// VERIFY: this method may not exist`
-5. **Respect the active schema** — don't invent database columns or table names
-
-### Code Quality (MANDATORY)
-- No `any` types in TypeScript without a comment explaining why
-- Every exported function needs a return type annotation
-- Async functions must handle errors (try/catch or `.catch()`)
-- No `eval()`, `innerHTML`, unparameterized SQL string concatenation
-
----
-
-## SLASH COMMANDS AVAILABLE
-
-|Command|Description|
-|---|---|
-|`/generate`|Run the full Tribunal (Maker → Parallel Review → Human Gate)|
-|`/create`|Structured 4-stage app creation|
-|`/enhance`|Add or update features in existing apps|
-|`/plan`|Project planning only — no code written|
-|`/review`|Review an existing file or snippet for hallucinations|
-|`/review-sql`|SQL-specific deep audit|
-|`/review-react`|React/Frontend-specific deep audit|
-|`/review-types`|TypeScript type safety audit|
-|`/review-deps`|Dependency hallucination audit (checks against package.json)|
-|`/tribunal-full`|All 14 reviewer agents run in parallel|
-|`/tribunal-backend`|Logic + Security + Dependency + Types|
-|`/tribunal-frontend`|Logic + Security + Frontend + Types|
-|`/tribunal-database`|Logic + Security + SQL|
-|`/tribunal-mobile`|Logic + Security + Mobile — for React Native, Flutter, responsive web|
-|`/tribunal-performance`|Logic + Performance — for optimization, profiling, bottlenecks|
-|`/tribunal-speed`|Full-stack parallel performance audit — CWV + DB latency + Node throughput|
-|`/brainstorm`|Explore implementation options before coding|
-|`/debug`|Systematic debugging with root cause analysis|
-|`/refactor`|Dependency-safe code refactoring with behavior preservation|
-|`/migrate`|Framework upgrades, dependency bumps, DB migrations|
-|`/deploy`|Pre-flight checks and deployment execution|
-|`/test`|Test generation and test running|
-|`/preview`|Start / stop local dev server|
-|`/status`|Agent and project status board|
-|`/session`|Multi-session state tracking|
-|`/orchestrate`|Coordinate multiple agents for complex tasks|
-|`/swarm`|Supervisor decomposes goal → dispatches to specialist Workers → synthesizes unified output|
-|`/ui-ux-pro-max`|Plan and implement cutting-edge UI/UX|
-|`/audit`|Full project health audit (security → lint → tests → deps → bundle)|
-|`/fix`|Auto-fix lint, formatting, and import issues (with human gate)|
-|`/changelog`|Generate changelog from git history|
-|`/api-tester`|Multi-stage API endpoint testing with auth-aware request sequences|
-|`/performance-benchmarker`|Lighthouse, bundle analysis, and API latency benchmarks|
-
----
-
-## RESPONSE FORMAT (MANDATORY)
-
-When generating code, always respond as:
-
-```markdown
-🏛️ **Tribunal [domain] review active**
-🤖 Applying agents: [list active agents]
-
-[Generated code]
-
----
-⚖️ **Self-audit notes:**
-- [Any assumption made]
-- [Any `// VERIFY` tags placed and why]
-- [Dependencies added and where to install them]
-```

package/.agent/skills/doc.md

@@ -1,177 +0,0 @@
-# Antigravity Skills
-
-**Guide to creating and using Skills in the Antigravity Kit**
-
----
-
-## 📋 Overview
-
-While Antigravity's base models (like Gemini) are powerful generalists, they don't know your specific project context or your team's standards. Loading every rule or tool into the agent's context window leads to "tool bloat," higher costs, latency, and confusion.
-
-**Antigravity Skills** solve this through **Progressive Disclosure**. A Skill is a package of specialized knowledge that remains dormant until needed. This information is only loaded into the agent's context when your specific request matches the skill's description.
-
----
-
-## 📁 Structure and Scope
-
-Skills are folder-based packages. You can define these scopes based on your needs:
-
-|Scope|Path|Description|
-|-------------|---------------------------------|------------------------------------|
-|**Workspace**|`<workspace-root>/.agent/skills/`|Available only in a specific project|
-
-### Skill Directory Structure
-
-```
-my-skill/
-├── SKILL.md      # (Required) Metadata & instructions
-├── scripts/      # (Optional) Python or Bash scripts
-├── references/   # (Optional) Text, documentation, templates
-└── assets/       # (Optional) Images or logos
-```
-
----
-
-## 🔍 Example 1: Code Review Skill
-
-This is an instruction-only skill; you only need to create the `SKILL.md` file.
-
-### Step 1: Create the directory
-
-```bash
-mkdir -p .agent/skills/code-review
-```
-
-### Step 2: Create SKILL.md
-
-```markdown
----
-name: code-review
-description: Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
----
-
-# Code Review Skill
-
-When reviewing code, follow these steps:
-
-## Review checklist
-
-1. **Correctness**: Does the code do what it's supposed to?
-2. **Edge cases**: Are error conditions handled?
-3. **Style**: Does it follow project conventions?
-4. **Performance**: Are there obvious inefficiencies?
-
-## How to provide feedback
-
-- Be specific about what needs to change
-- Explain why, not just what
-- Suggest alternatives when possible
-```
-
-**Note**: The `SKILL.md` file contains metadata (name, description) at the top, followed by the instructions. The agent will only read the metadata and load the full instructions only when needed.
-
-### Try it out
-
-Create a file `demo_bad_code.py`:
-
-```python
-import time
-
-def get_user_data(users, id):
-    # Find user by ID
-    for u in users:
-        if u['id'] == id:
-            return u
-    return None
-
-def process_payments(items):
-    total = 0
-    for i in items:
-        # Calculate tax
-        tax = i['price'] * 0.1
-        total = total + i['price'] + tax
-        time.sleep(0.1)  # Simulate slow network call
-    return total
-
-def run_batch():
-    users = [{'id': 1, 'name': 'Alice'}, {'id': 2, 'name': 'Bob'}]
-    items = [{'price': 10}, {'price': 20}, {'price': 100}]
-
-    u = get_user_data(users, 3)
-    print("User found: " + u['name'])  # Will crash if None
-
-    print("Total: " + str(process_payments(items)))
-
-if __name__ == "__main__":
-    run_batch()
-```
-
-**Prompt**: `review the @demo_bad_code.py file`
-
-The Agent will automatically identify the `code-review` skill, load the information, and follow the instructions.
-
----
-
-## 📄 Example 2: License Header Skill
-
-This skill uses a reference file in the `resources/` (or `references/`) directory.
-
-### Step 1: Create the directory
-
-```bash
-mkdir -p .agent/skills/license-header-adder/resources
-```
-
-### Step 2: Create the template file
-
-**`.agent/skills/license-header-adder/resources/HEADER.txt`**:
-
-```
-/*
- * Copyright (c) 2026 YOUR_COMPANY_NAME LLC.
- * All rights reserved.
- * This code is proprietary and confidential.
- */
-```
-
-### Step 3: Create SKILL.md
-
-**`.agent/skills/license-header-adder/SKILL.md`**:
-
-```markdown
----
-name: license-header-adder
-description: Adds the standard corporate license header to new source files.
----
-
-# License Header Adder
-
-This skill ensures that all new source files have the correct copyright header.
-
-## Instructions
-
-1. **Read the Template**: Read the content of `resources/HEADER.txt`.
-2. **Apply to File**: When creating a new file, prepend this exact content.
-3. **Adapt Syntax**:
-   - For C-style languages (Java, TS), keep the `/* */` block.
-   - For Python/Shell, convert to `#` comments.
-```
-
-### Try it out
-
-**Prompt**: `Create a new Python script named data_processor.py that prints 'Hello World'.`
-
-The Agent will read the template, convert the comments to Python style, and automatically add it to the top of the file.
-
----
-
-## 🎯 Conclusion
-
-By creating Skills, you transform a general AI model into an expert for your project:
-
-- ✅ Systematize best practices
-- ✅ Adhere to code review rules
-- ✅ Automatically add license headers
-- ✅ The Agent automatically knows how to work with your team
-
-Instead of constantly reminding the AI to "remember to add the license" or "fix the commit format," now the Agent will do it automatically!