tribunal-kit 9.2.3 → 9.2.5

package/.agent/workflows/api-tester.md

@@ -1,189 +1,189 @@
----
-description: Automated multi-stage API endpoint testing. Generates and runs auth-aware request sequences (login → use token → test CRUD → verify errors). Reports response codes, schema mismatches, and unexpected data.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 3.0.0
-last-updated: 2026-07-30
-required-skills:
-  - testing-patterns
-  - api-patterns
-  - backend-security-expert
-scripts-binding:
-  - .agent/scripts/test_runner.js
-  - .agent/scripts/security_scan.js
----
-
-# /api-tester — Automated API Testing
-
-$ARGUMENTS
-
----
-
-## Mandatory Pre-Flight Context Inspection
-
-Before running automated API endpoint tests or auth-aware request sequences, you MUST inspect:
-
-1. Target Route Definition & Data Schemas → Inspect route parameters, body validation schemas (Zod/Pydantic), and auth middleware
-2. Test Server URL & Credentials (`.env.test`) → Verify base URL and test token environment variables
-3. Multi-Stage Request Sequence → Enforce sequential execution: Auth Login → Token Capture → CRUD Operations → Error Edge Case Verification
-
-4. Required Skills → Before executing, load and follow procedural rules from:
-   - `testing-patterns` (.agent/skills/testing-patterns/SKILL.md): Testing Trophy strategy (unit → integration → E2E)
-   - `api-patterns` (.agent/skills/api-patterns/SKILL.md): REST/GraphQL API design, versioning, and error contracts
-   - `backend-security-expert` (.agent/skills/backend-security-expert/SKILL.md): Server-side security, auth, JWT, ORM injection, RBAC
-
----
-
-## When to Use /api-tester
-
-| Use `/api-tester` when...             | Use something else when...                |
-| :------------------------------------ | :---------------------------------------- |
-| Testing REST API endpoints manually   | Unit tests needed → `/test`               |
-| Verifying auth token flows end-to-end | Full security audit → `/audit`            |
-| After generating new endpoints        | Load testing → `/performance-benchmarker` |
-| Checking response schemas             |                                           |
-
----
-
-## Phase 1 — Endpoint Discovery
-
-```bash
-# Find all defined routes
-grep -r "app.get\|app.post\|app.put\|app.delete\|app.patch" src/ --include="*.ts"
-grep -r "router.get\|router.post\|router.put" src/ --include="*.ts"
-
-# Next.js Route Handlers
-find src/app/api -name "route.ts" | sort
-```
-
----
-
-## Phase 2 — Auth Flow (Token Acquisition)
-
-Before testing protected endpoints, acquire auth token:
-
-```bash
-# Acquire JWT
-curl -X POST http://localhost:3000/api/auth/login \
-  -H "Content-Type: application/json" \
-  -d '{"email":"test@example.com","password":"testpassword"}' \
-  -s | jq '.token'
-
-# Assign to variable
-TOKEN=$(curl -X POST http://localhost:3000/api/auth/login \
-  -H "Content-Type: application/json" \
-  -d '{"email":"test@example.com","password":"testpassword"}' \
-  -s | jq -r '.token')
-```
-
----
-
-## Phase 3 — CRUD Sequence Testing
-
-Test endpoints in the correct order (create before read, read before delete):
-
-```bash
-# 1. CREATE (POST)
-CREATE_RESPONSE=$(curl -X POST http://localhost:3000/api/users \
-  -H "Authorization: Bearer $TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"name":"Test User","email":"new@test.com"}')
-CREATED_ID=$(echo $CREATE_RESPONSE | jq -r '.id')
-echo "Created: $CREATED_ID"
-
-# 2. READ (GET)
-curl -X GET "http://localhost:3000/api/users/$CREATED_ID" \
-  -H "Authorization: Bearer $TOKEN" \
-  | jq .
-
-# 3. UPDATE (PATCH)
-curl -X PATCH "http://localhost:3000/api/users/$CREATED_ID" \
-  -H "Authorization: Bearer $TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"name":"Updated Name"}'
-
-# 4. DELETE
-curl -X DELETE "http://localhost:3000/api/users/$CREATED_ID" \
-  -H "Authorization: Bearer $TOKEN"
-```
-
----
-
-## Phase 4 — Error Case Testing
-
-Test that errors are handled correctly:
-
-```bash
-# 4xx errors (client errors — must NOT return 200!)
-echo "--- Unauthenticated request (expect 401) ---"
-curl -X GET http://localhost:3000/api/users -s -o /dev/null -w "%{http_code}\n"
-
-echo "--- Invalid ID (expect 404 or 400) ---"
-curl -X GET "http://localhost:3000/api/users/not-a-real-id" \
-  -H "Authorization: Bearer $TOKEN" \
-  -s -o /dev/null -w "%{http_code}\n"
-
-echo "--- Invalid body (expect 400) ---"
-curl -X POST http://localhost:3000/api/users \
-  -H "Authorization: Bearer $TOKEN" \
-  -H "Content-Type: application/json" \
-  -d '{"invalid":"field"}' \
-  -s -o /dev/null -w "%{http_code}\n"
-
-echo "--- Rate limiting (expect 429 after N requests) ---"
-for i in {1..15}; do
-  STATUS=$(curl -X POST http://localhost:3000/api/auth/login \
-    -H "Content-Type: application/json" \
-    -d '{"email":"x","password":"wrong"}' \
-    -s -o /dev/null -w "%{http_code}")
-  echo "Attempt $i: $STATUS"
-done
-```
-
----
-
-## Phase 5 — Test Report
-
-```
-━━━ API Test Report ━━━━━━━━━━━━━━━━━━━━━━
-
-Auth Flow:   ✅ Login → token acquired
-POST /users: ✅ 201 Created — id returned
-GET /users:  ✅ 200 — data matches expected schema
-PATCH /users: ✅ 200 — update reflected
-DELETE /users: ✅ 204 No Content
-
-Error Cases:
-  Unauthenticated: ✅ 401 (expected)
-  Invalid ID:      ✅ 404 (expected)
-  Invalid body:    ✅ 400 (expected) — Zod error returned
-  Rate limiting:   ✅ 429 on attempt 11 (expected)
-
-━━━ Issues Found ━━━━━━━━━━━━━━━━━━━━━━━━
-
-  ❌ GET /api/users returns 200 with no auth (should be 401)
-  ⚠️ PATCH /api/users doesn't validate Content-Type (accepts any body)
-```
-
----
-
-## Usage Examples
-
-```
-/api-tester POST /api/auth/login then test /api/users CRUD
-/api-tester test the /api/checkout flow with Stripe test card
-/api-tester verify all auth routes return 401 for unauthenticated requests
-/api-tester test rate limiting on /api/auth/login
-```
-
----
-
-## After /api-tester — Next Steps
-
-| Outcome                     | Next Command                                        |
-| :-------------------------- | :-------------------------------------------------- |
-| Tests fail due to code bugs | → `/debug` to isolate the fix                       |
-| Tests pass, coverage needed | → `/test` to convert to automated Jest/Vitest suite |
-| API is slow                 | → `/tribunal-speed` to profile latency              |
-| Ready to ship               | → `/deploy` with full pre-flight                    |
-
----
+---
+description: Automated multi-stage API endpoint testing. Generates and runs auth-aware request sequences (login → use token → test CRUD → verify errors). Reports response codes, schema mismatches, and unexpected data.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - testing-patterns
+  - api-patterns
+  - backend-security-expert
+scripts-binding:
+  - .agent/scripts/test_runner.js
+  - .agent/scripts/security_scan.js
+---
+
+# /api-tester — Automated API Testing
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before running automated API endpoint tests or auth-aware request sequences, you MUST inspect:
+
+1. Target Route Definition & Data Schemas → Inspect route parameters, body validation schemas (Zod/Pydantic), and auth middleware
+2. Test Server URL & Credentials (`.env.test`) → Verify base URL and test token environment variables
+3. Multi-Stage Request Sequence → Enforce sequential execution: Auth Login → Token Capture → CRUD Operations → Error Edge Case Verification
+
+4. Required Skills → Before executing, load and follow procedural rules from:
+   - `testing-patterns` (.agent/skills/testing-patterns/SKILL.md): Testing Trophy strategy (unit → integration → E2E)
+   - `api-patterns` (.agent/skills/api-patterns/SKILL.md): REST/GraphQL API design, versioning, and error contracts
+   - `backend-security-expert` (.agent/skills/backend-security-expert/SKILL.md): Server-side security, auth, JWT, ORM injection, RBAC
+
+---
+
+## When to Use /api-tester
+
+| Use `/api-tester` when...             | Use something else when...                |
+| :------------------------------------ | :---------------------------------------- |
+| Testing REST API endpoints manually   | Unit tests needed → `/test`               |
+| Verifying auth token flows end-to-end | Full security audit → `/audit`            |
+| After generating new endpoints        | Load testing → `/performance-benchmarker` |
+| Checking response schemas             |                                           |
+
+---
+
+## Phase 1 — Endpoint Discovery
+
+```bash
+# Find all defined routes
+grep -r "app.get\|app.post\|app.put\|app.delete\|app.patch" src/ --include="*.ts"
+grep -r "router.get\|router.post\|router.put" src/ --include="*.ts"
+
+# Next.js Route Handlers
+find src/app/api -name "route.ts" | sort
+```
+
+---
+
+## Phase 2 — Auth Flow (Token Acquisition)
+
+Before testing protected endpoints, acquire auth token:
+
+```bash
+# Acquire JWT
+curl -X POST http://localhost:3000/api/auth/login \
+  -H "Content-Type: application/json" \
+  -d '{"email":"test@example.com","password":"testpassword"}' \
+  -s | jq '.token'
+
+# Assign to variable
+TOKEN=$(curl -X POST http://localhost:3000/api/auth/login \
+  -H "Content-Type: application/json" \
+  -d '{"email":"test@example.com","password":"testpassword"}' \
+  -s | jq -r '.token')
+```
+
+---
+
+## Phase 3 — CRUD Sequence Testing
+
+Test endpoints in the correct order (create before read, read before delete):
+
+```bash
+# 1. CREATE (POST)
+CREATE_RESPONSE=$(curl -X POST http://localhost:3000/api/users \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"name":"Test User","email":"new@test.com"}')
+CREATED_ID=$(echo $CREATE_RESPONSE | jq -r '.id')
+echo "Created: $CREATED_ID"
+
+# 2. READ (GET)
+curl -X GET "http://localhost:3000/api/users/$CREATED_ID" \
+  -H "Authorization: Bearer $TOKEN" \
+  | jq .
+
+# 3. UPDATE (PATCH)
+curl -X PATCH "http://localhost:3000/api/users/$CREATED_ID" \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"name":"Updated Name"}'
+
+# 4. DELETE
+curl -X DELETE "http://localhost:3000/api/users/$CREATED_ID" \
+  -H "Authorization: Bearer $TOKEN"
+```
+
+---
+
+## Phase 4 — Error Case Testing
+
+Test that errors are handled correctly:
+
+```bash
+# 4xx errors (client errors — must NOT return 200!)
+echo "--- Unauthenticated request (expect 401) ---"
+curl -X GET http://localhost:3000/api/users -s -o /dev/null -w "%{http_code}\n"
+
+echo "--- Invalid ID (expect 404 or 400) ---"
+curl -X GET "http://localhost:3000/api/users/not-a-real-id" \
+  -H "Authorization: Bearer $TOKEN" \
+  -s -o /dev/null -w "%{http_code}\n"
+
+echo "--- Invalid body (expect 400) ---"
+curl -X POST http://localhost:3000/api/users \
+  -H "Authorization: Bearer $TOKEN" \
+  -H "Content-Type: application/json" \
+  -d '{"invalid":"field"}' \
+  -s -o /dev/null -w "%{http_code}\n"
+
+echo "--- Rate limiting (expect 429 after N requests) ---"
+for i in {1..15}; do
+  STATUS=$(curl -X POST http://localhost:3000/api/auth/login \
+    -H "Content-Type: application/json" \
+    -d '{"email":"x","password":"wrong"}' \
+    -s -o /dev/null -w "%{http_code}")
+  echo "Attempt $i: $STATUS"
+done
+```
+
+---
+
+## Phase 5 — Test Report
+
+```
+━━━ API Test Report ━━━━━━━━━━━━━━━━━━━━━━
+
+Auth Flow:   ✅ Login → token acquired
+POST /users: ✅ 201 Created — id returned
+GET /users:  ✅ 200 — data matches expected schema
+PATCH /users: ✅ 200 — update reflected
+DELETE /users: ✅ 204 No Content
+
+Error Cases:
+  Unauthenticated: ✅ 401 (expected)
+  Invalid ID:      ✅ 404 (expected)
+  Invalid body:    ✅ 400 (expected) — Zod error returned
+  Rate limiting:   ✅ 429 on attempt 11 (expected)
+
+━━━ Issues Found ━━━━━━━━━━━━━━━━━━━━━━━━
+
+  ❌ GET /api/users returns 200 with no auth (should be 401)
+  ⚠️ PATCH /api/users doesn't validate Content-Type (accepts any body)
+```
+
+---
+
+## Usage Examples
+
+```
+/api-tester POST /api/auth/login then test /api/users CRUD
+/api-tester test the /api/checkout flow with Stripe test card
+/api-tester verify all auth routes return 401 for unauthenticated requests
+/api-tester test rate limiting on /api/auth/login
+```
+
+---
+
+## After /api-tester — Next Steps
+
+| Outcome                     | Next Command                                        |
+| :-------------------------- | :-------------------------------------------------- |
+| Tests fail due to code bugs | → `/debug` to isolate the fix                       |
+| Tests pass, coverage needed | → `/test` to convert to automated Jest/Vitest suite |
+| API is slow                 | → `/tribunal-speed` to profile latency              |
+| Ready to ship               | → `/deploy` with full pre-flight                    |
+
+---

package/.agent/workflows/assimilate.md

@@ -0,0 +1,21 @@
+---
+name: assimilate
+description: "Trigger the learning pipeline to extract, validate, and store Tribunal Instincts."
+version: 1.0.0
+---
+
+# ASSIMILATE (LEARNING PIPELINE)
+
+## Invocation
+`/assimilate` or `/learn`
+
+## Behavior
+Instead of learning in real-time and bloating the execution path, learning is an offline batch job.
+
+1. **Extraction**: Invokes the `memory_archivist.js` which reads the most recent session logs.
+2. **Analysis**: Searches for repeated errors, test failures, and ultimate successful fixes.
+3. **Validation**: Converts successful fixes into candidate "Tribunal Instincts".
+4. **Storage**: Saves the verified evidence-backed instinct into `instincts.json` where `context_broker.js` can retrieve it for future related tasks.
+
+## Limits
+Do not trigger this workflow automatically after every prompt. Use it specifically after a long debugging session or a complex architectural setup to persist the hard-earned lessons.

package/.agent/workflows/audit-live.md

@@ -1,53 +1,53 @@
----
-description: Live website audit using native browser automation. Audits accessibility (WCAG 2.2), console errors, network failures, Core Web Vitals, and security headers. Passes findings through Tribunal's Maker-Reviewer pipeline before proposing fixes.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 1.0.0
-last-updated: 2026-09-13
-required-skills:
-  - browser-audit
-  - web-quality-audit
-  - audit-and-fix
-scripts-binding:
-  - .agent/scripts/browser_audit.js
-  - .agent/scripts/checklist.js
----
-
-# /audit-live — Live Website Health & Accessibility Audit
-
-$ARGUMENTS
-
----
-
-## 1. Objective
-
-Audits a running local server (`http://localhost:3000`) or live staging URL using Tribunal Kit's native browser automation engine.
-
-## 2. Execution Pipeline
-
-```
-1. Ingest URL from arguments
-      │
-2. Execute Browser Audit
-   node .agent/scripts/browser_audit.js <url> --json
-      │
-3. Multi-Reviewer Fan-Out Analysis:
-   - web-quality-audit: Evaluates WCAG 2.2 AA contrast & labels
-   - frontend-specialist: Analyzes heading hierarchy & layout shifts
-   - security-auditor: Checks CSP and security headers
-      │
-4. Synthesize Prioritized Action Plan:
-   - P0: Fatal console errors & unhandled promise rejections
-   - P1: Form labels, missing alt text, keyboard focus
-   - P2: Security headers & performance optimizations
-      │
-5. Human Gate Approval:
-   Present proposed code fixes to human before editing files.
-```
-
-## 3. Human Gate Verification
-
-No code is modified on disk without explicit approval. Findings are presented as:
-
-- Issue Description & Location
-- Proposed Fix (Code diff)
-- Re-test command to verify resolution.
+---
+description: Live website audit using native browser automation. Audits accessibility (WCAG 2.2), console errors, network failures, Core Web Vitals, and security headers. Passes findings through Tribunal's Maker-Reviewer pipeline before proposing fixes.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 1.0.0
+last-updated: 2026-09-13
+required-skills:
+  - browser-audit
+  - web-quality-audit
+  - audit-and-fix
+scripts-binding:
+  - .agent/scripts/browser_audit.js
+  - .agent/scripts/checklist.js
+---
+
+# /audit-live — Live Website Health & Accessibility Audit
+
+$ARGUMENTS
+
+---
+
+## 1. Objective
+
+Audits a running local server (`http://localhost:3000`) or live staging URL using Tribunal Kit's native browser automation engine.
+
+## 2. Execution Pipeline
+
+```
+1. Ingest URL from arguments
+      │
+2. Execute Browser Audit
+   node .agent/scripts/browser_audit.js <url> --json
+      │
+3. Multi-Reviewer Fan-Out Analysis:
+   - web-quality-audit: Evaluates WCAG 2.2 AA contrast & labels
+   - frontend-specialist: Analyzes heading hierarchy & layout shifts
+   - security-auditor: Checks CSP and security headers
+      │
+4. Synthesize Prioritized Action Plan:
+   - P0: Fatal console errors & unhandled promise rejections
+   - P1: Form labels, missing alt text, keyboard focus
+   - P2: Security headers & performance optimizations
+      │
+5. Human Gate Approval:
+   Present proposed code fixes to human before editing files.
+```
+
+## 3. Human Gate Verification
+
+No code is modified on disk without explicit approval. Findings are presented as:
+
+- Issue Description & Location
+- Proposed Fix (Code diff)
+- Re-test command to verify resolution.