tribunal-kit 9.2.4 → 9.2.6

package/.agent/workflows/swarm.md

@@ -1,218 +1,218 @@
----
-description: Multi-Agent Swarm Orchestration. Supervisor decomposes a complex goal into sub-tasks, dispatches to specialist Workers via structured JSON contracts, collects results via allSettled fan-in, and synthesizes a unified deliverable. Validates payloads via swarm_dispatcher.js before dispatch.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 3.0.0
-last-updated: 2026-07-30
-required-skills:
-  - parallel-agents
-  - agent-organizer
-  - agentic-workflows-2026
-scripts-binding:
-  - .agent/scripts/swarm_dispatcher.js
-  - .agent/scripts/verify_all.js
----
-
-# /swarm — Multi-Agent Swarm Execution
-
-$ARGUMENTS
-
----
-
-## Mandatory Pre-Flight Context Inspection
-
-Before decomposing goals into worker sub-tasks or triggering swarm execution, you MUST inspect:
-
-1. Swarm Dispatcher Validator (`.agent/scripts/swarm_dispatcher.js`) → Run payload validation script to ensure valid worker JSON payloads
-2. Non-Overlapping File Boundary Rule → Verify worker tasks target disjoint file sets to prevent git write conflicts during parallel execution
-3. `Promise.allSettled()` Fan-In Protocol → Collect all worker status reports and synthesize final deliverable before Human Gate confirmation
-
-4. Required Skills → Before executing, load and follow procedural rules from:
-   - `parallel-agents` (the parallel-agents skill): Parallel agent dispatch patterns and fan-in synthesis
-   - `agent-organizer` (.agent/skills/agent-organizer/SKILL.md): Multi-agent coordination and task decomposition
-   - `agentic-workflows-2026` (.agent/skills/agentic-workflows-2026/SKILL.md): Advanced agent loops, ReAct planning, and structured tool calling
-
----
-
-## When to Use /swarm Over /orchestrate
-
-| Use `/swarm` when...                                | Use `/orchestrate` when...        |
-| :-------------------------------------------------- | :-------------------------------- |
-| 5+ workers needed simultaneously                    | 2-4 workers in a review           |
-| Tasks are explicitly JSON-contracted                | Tasks can be described informally |
-| Supervisor/Worker role separation matters           | Simple coordination needed        |
-| Wave execution needs session persisting across time | Single-session orchestration      |
-
----
-
-## Phase 1 — Swarm Initialization
-
-The Supervisor agent activates and:
-
-1. Reads the goal and identifies all atomic sub-tasks
-2. Validates that sub-tasks don't share output files
-3. Estimates context budget per worker
-4. Writes initial state to task.md
-
----
-
-## Phase 2 — Worker Dispatch Contracts
-
-Every worker receives a structured JSON contract (not natural language):
-
-```json
-{
-  "task_id": "audit-auth-routes",
-  "worker_type": "backend-specialist",
-  "scope": "Audit all files in src/app/api/auth/ for security and type safety",
-  "files_to_read": [
-    "src/app/api/auth/login/route.ts",
-    "src/app/api/auth/register/route.ts",
-    "src/middleware.ts"
-  ],
-  "files_to_write": [],
-  "context_summary": [
-    "Next.js 15 App Router project",
-    "Auth uses next-auth v5 (auth.ts pattern)",
-    "Database: Prisma 6 on PostgreSQL"
-  ],
-  "constraints": [
-    "Report findings only — do not modify files",
-    "Report BLOCKED if you cannot determine auth pattern from provided files"
-  ],
-  "output_format": {
-    "status": "COMPLETE | BLOCKED | ERROR",
-    "findings": ["list of specific issues found with file+line references"],
-    "summary": "2-3 sentence summary"
-  }
-}
-```
-
----
-
-## Phase 3 — Payload Validation
-
-Before dispatching, validate all worker contracts:
-
-```bash
-node .agent/scripts/swarm_dispatcher.js --file payload.json
-```
-
-If validation passes → dispatch workers in parallel.
-If validation fails → fix payload before dispatch.
-
----
-
-## Phase 4 — Fan-Out Execution
-
-```
-Wave dispatch: POST all contracts simultaneously
-               ↓
-               Wait for completion via allSettled (not Promise.all)
-               ↓
-               Collect ALL results — COMPLETE + BLOCKED + ERROR
-               ↓
-Fan-In:        Supervisor aggregates, resolves conflicts
-               ↓
-               Human Gate before writing anything to disk
-```
-
-**allSettled vs Promise.all:** A single failed worker must NOT cancel all sibling workers. Collect all results, then handle failures.
-
----
-
-## Phase 5 — Status Protocol
-
-Workers report exactly one of three terminal statuses:
-
-```
-COMPLETE: Work done. Include output_format fields.
-
-BLOCKED: Cannot proceed without missing prerequisite.
-  blocked_by: [specific missing information]
-  unblocked_by: [what must happen first]
-  → Supervisor: provide missing input or escalate to human
-
-ERROR: Unrecoverable after 3 attempts.
-  error: [specific message]
-  attempts: 3
-  → Supervisor: report to human with ⚠️ Agent Failure Report
-```
-
----
-
-## Phase 6 — Session Persistence
-
-Supervisor writes task.md after each wave:
-
-```markdown
-# Swarm Session: [goal-slug]
-
-## Wave 1 — [timestamp]
-
-- [task-id]: COMPLETE — [2-line summary]
-- [task-id]: BLOCKED — [reason] → redispatched with [context added]
-
-## Issues Carrying Forward
-
-- [cross-task issue affecting Wave 2]
-
-## Human Gate Status
-
-- [ ] Pending review
-```
-
----
-
-## Phase 7 — Human Gate
-
-```
-━━━ Swarm Complete ━━━━━━━━━━━━━━━━━━━━━░░░
-
-Workers: [N dispatched / N complete / N blocked / N error]
-
-━━━ Synthesized Results ━━━━━━━━━━━━━━━━━━
-[Findings by severity — critical → high → medium → low]
-
-━━━ Files to Write ━━━━━━━━━━━━━━━━━━━━━━
-[List all files with change summaries]
-
-━━━ Human Gate ━━━━━━━━━━━━━━━━━━━━━━━━━
-Approve?  Y = write to disk | N = discard | R = revise
-```
-
----
-
-## Failure Report Format
-
-```
-⚠️ Agent Failure Report
-━━━━━━━━━━━━━━━━━━━━━
-Agent:       backend-specialist (Worker A)
-Task:        audit-auth-routes
-Attempts:    3 of 3
-Last Error:  Could not resolve auth.ts import path — tsconfig paths not in scope
-Context:     Files provided: src/app/api/auth/*.ts — missing: tsconfig.json
-Suggestion:  Include tsconfig.json in files_to_read for next dispatch
-```
-
----
-
-## Usage Examples
-
-```
-/swarm comprehensive pre-launch audit: security + tests + performance + accessibility
-/swarm analyze all API routes for OWASP vulnerabilities simultaneously
-/swarm generate full test suite for auth, checkout, and user management
-/swarm review and optimize all N+1 query patterns across the codebase
-```
-
----
-
-## After /swarm — Next Steps
-
-| Outcome                    | Next Command                                    |
-| :------------------------- | :---------------------------------------------- |
-| Findings generated         | → Route to specific `/tribunal-*` to fix issues |
-| Architecture tasks blocked | → `/plan` to resolve blocked items              |
-
----
+---
+description: Multi-Agent Swarm Orchestration. Supervisor decomposes a complex goal into sub-tasks, dispatches to specialist Workers via structured JSON contracts, collects results via allSettled fan-in, and synthesizes a unified deliverable. Validates payloads via swarm_dispatcher.js before dispatch.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - parallel-agents
+  - agent-organizer
+  - agentic-workflows-2026
+scripts-binding:
+  - .agent/scripts/swarm_dispatcher.js
+  - .agent/scripts/verify_all.js
+---
+
+# /swarm — Multi-Agent Swarm Execution
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before decomposing goals into worker sub-tasks or triggering swarm execution, you MUST inspect:
+
+1. Swarm Dispatcher Validator (`.agent/scripts/swarm_dispatcher.js`) → Run payload validation script to ensure valid worker JSON payloads
+2. Non-Overlapping File Boundary Rule → Verify worker tasks target disjoint file sets to prevent git write conflicts during parallel execution
+3. `Promise.allSettled()` Fan-In Protocol → Collect all worker status reports and synthesize final deliverable before Human Gate confirmation
+
+4. Required Skills → Before executing, load and follow procedural rules from:
+   - `parallel-agents` (the parallel-agents skill): Parallel agent dispatch patterns and fan-in synthesis
+   - `agent-organizer` (.agent/skills/agent-organizer/SKILL.md): Multi-agent coordination and task decomposition
+   - `agentic-workflows-2026` (.agent/skills/agentic-workflows-2026/SKILL.md): Advanced agent loops, ReAct planning, and structured tool calling
+
+---
+
+## When to Use /swarm Over /orchestrate
+
+| Use `/swarm` when...                                | Use `/orchestrate` when...        |
+| :-------------------------------------------------- | :-------------------------------- |
+| 5+ workers needed simultaneously                    | 2-4 workers in a review           |
+| Tasks are explicitly JSON-contracted                | Tasks can be described informally |
+| Supervisor/Worker role separation matters           | Simple coordination needed        |
+| Wave execution needs session persisting across time | Single-session orchestration      |
+
+---
+
+## Phase 1 — Swarm Initialization
+
+The Supervisor agent activates and:
+
+1. Reads the goal and identifies all atomic sub-tasks
+2. Validates that sub-tasks don't share output files
+3. Estimates context budget per worker
+4. Writes initial state to task.md
+
+---
+
+## Phase 2 — Worker Dispatch Contracts
+
+Every worker receives a structured JSON contract (not natural language):
+
+```json
+{
+  "task_id": "audit-auth-routes",
+  "worker_type": "backend-specialist",
+  "scope": "Audit all files in src/app/api/auth/ for security and type safety",
+  "files_to_read": [
+    "src/app/api/auth/login/route.ts",
+    "src/app/api/auth/register/route.ts",
+    "src/middleware.ts"
+  ],
+  "files_to_write": [],
+  "context_summary": [
+    "Next.js 15 App Router project",
+    "Auth uses next-auth v5 (auth.ts pattern)",
+    "Database: Prisma 6 on PostgreSQL"
+  ],
+  "constraints": [
+    "Report findings only — do not modify files",
+    "Report BLOCKED if you cannot determine auth pattern from provided files"
+  ],
+  "output_format": {
+    "status": "COMPLETE | BLOCKED | ERROR",
+    "findings": ["list of specific issues found with file+line references"],
+    "summary": "2-3 sentence summary"
+  }
+}
+```
+
+---
+
+## Phase 3 — Payload Validation
+
+Before dispatching, validate all worker contracts:
+
+```bash
+node .agent/scripts/swarm_dispatcher.js --file payload.json
+```
+
+If validation passes → dispatch workers in parallel.
+If validation fails → fix payload before dispatch.
+
+---
+
+## Phase 4 — Fan-Out Execution
+
+```
+Wave dispatch: POST all contracts simultaneously
+               ↓
+               Wait for completion via allSettled (not Promise.all)
+               ↓
+               Collect ALL results — COMPLETE + BLOCKED + ERROR
+               ↓
+Fan-In:        Supervisor aggregates, resolves conflicts
+               ↓
+               Human Gate before writing anything to disk
+```
+
+**allSettled vs Promise.all:** A single failed worker must NOT cancel all sibling workers. Collect all results, then handle failures.
+
+---
+
+## Phase 5 — Status Protocol
+
+Workers report exactly one of three terminal statuses:
+
+```
+COMPLETE: Work done. Include output_format fields.
+
+BLOCKED: Cannot proceed without missing prerequisite.
+  blocked_by: [specific missing information]
+  unblocked_by: [what must happen first]
+  → Supervisor: provide missing input or escalate to human
+
+ERROR: Unrecoverable after 3 attempts.
+  error: [specific message]
+  attempts: 3
+  → Supervisor: report to human with ⚠️ Agent Failure Report
+```
+
+---
+
+## Phase 6 — Session Persistence
+
+Supervisor writes task.md after each wave:
+
+```markdown
+# Swarm Session: [goal-slug]
+
+## Wave 1 — [timestamp]
+
+- [task-id]: COMPLETE — [2-line summary]
+- [task-id]: BLOCKED — [reason] → redispatched with [context added]
+
+## Issues Carrying Forward
+
+- [cross-task issue affecting Wave 2]
+
+## Human Gate Status
+
+- [ ] Pending review
+```
+
+---
+
+## Phase 7 — Human Gate
+
+```
+━━━ Swarm Complete ━━━━━━━━━━━━━━━━━━━━━░░░
+
+Workers: [N dispatched / N complete / N blocked / N error]
+
+━━━ Synthesized Results ━━━━━━━━━━━━━━━━━━
+[Findings by severity — critical → high → medium → low]
+
+━━━ Files to Write ━━━━━━━━━━━━━━━━━━━━━━
+[List all files with change summaries]
+
+━━━ Human Gate ━━━━━━━━━━━━━━━━━━━━━━━━━
+Approve?  Y = write to disk | N = discard | R = revise
+```
+
+---
+
+## Failure Report Format
+
+```
+⚠️ Agent Failure Report
+━━━━━━━━━━━━━━━━━━━━━
+Agent:       backend-specialist (Worker A)
+Task:        audit-auth-routes
+Attempts:    3 of 3
+Last Error:  Could not resolve auth.ts import path — tsconfig paths not in scope
+Context:     Files provided: src/app/api/auth/*.ts — missing: tsconfig.json
+Suggestion:  Include tsconfig.json in files_to_read for next dispatch
+```
+
+---
+
+## Usage Examples
+
+```
+/swarm comprehensive pre-launch audit: security + tests + performance + accessibility
+/swarm analyze all API routes for OWASP vulnerabilities simultaneously
+/swarm generate full test suite for auth, checkout, and user management
+/swarm review and optimize all N+1 query patterns across the codebase
+```
+
+---
+
+## After /swarm — Next Steps
+
+| Outcome                    | Next Command                                    |
+| :------------------------- | :---------------------------------------------- |
+| Findings generated         | → Route to specific `/tribunal-*` to fix issues |
+| Architecture tasks blocked | → `/plan` to resolve blocked items              |
+
+---

package/.agent/workflows/team-mode.md

@@ -1,22 +1,25 @@
----
-name: team-mode
-description: "Enable dynamic multi-agent task execution, DAG routing, and parallel reviews."
-version: 1.0.0
----
-
-# TEAM MODE (DAG ORCHESTRATION)
-
-## Invocation
-`/team-mode [task_prompt]`
-
-## Behavior
-Activates the `swarm_dispatcher.js` using the `--mode dag` flag to execute highly complex, multi-domain tasks.
-
-1. **Decomposition**: The Orchestrator agent splits the `task_prompt` into a Topological DAG.
-2. **Delegation**: Specialized agents (e.g., `frontend-specialist`, `database-architect`) are assigned specific nodes in the graph.
-3. **Parallel Execution**: Independent tasks execute simultaneously.
-4. **Handoffs**: Output from a database task is explicitly passed as context to the dependent frontend task.
-5. **Review**: The entire output is passed through `/tribunal-full` before being marked complete.
-
-## Guardrails
-Team Mode cannot bypass the Human Gate. If any subagent proposes a destructive action, the entire DAG is paused, and the Human Gate Negotiator is summoned.
+---
+name: team-mode
+description: 'Enable dynamic multi-agent task execution, DAG routing, and parallel reviews.'
+version: 1.0.0
+---
+
+# TEAM MODE (DAG ORCHESTRATION)
+
+## Invocation
+
+`/team-mode [task_prompt]`
+
+## Behavior
+
+Activates the `swarm_dispatcher.js` using the `--mode dag` flag to execute highly complex, multi-domain tasks.
+
+1. **Decomposition**: The Orchestrator agent splits the `task_prompt` into a Topological DAG.
+2. **Delegation**: Specialized agents (e.g., `frontend-specialist`, `database-architect`) are assigned specific nodes in the graph.
+3. **Parallel Execution**: Independent tasks execute simultaneously.
+4. **Handoffs**: Output from a database task is explicitly passed as context to the dependent frontend task.
+5. **Review**: The entire output is passed through `/tribunal-full` before being marked complete.
+
+## Guardrails
+
+Team Mode cannot bypass the Human Gate. If any subagent proposes a destructive action, the entire DAG is paused, and the Human Gate Negotiator is summoned.