tribunal-kit 6.0.0 → 7.0.0

package/.agent/templates/DESIGN.md

@@ -10,41 +10,42 @@
 
 Choose **ONE** direction from the list below to define the brand visual system. Do not mix directions:
 
-*   **Swiss Precision:** Clean, grid-locked alignment, sans-serif typography, clinical whitespace, no decoration.
-*   **Brutalist:** Raw, exposed 1px borders, monospace display fonts, high contrast, sharp corners (`radius: 2px`).
-*   **Editorial:** Magazine-inspired layout, large display headings, generous margins, serif headings, single-column reading paths.
-*   **Neo-Glassmorphism:** Tinted overlays, high backdrop blur (`blur(20px)`), luminous hairlines, floating modules.
-*   **Soft Minimal:** Warm tinted grays (`oklch`), rounded shapes (`radius: 12px`), deep shadows, spacious margins.
-*   **Dark Luxury:** Near-black base (`#0A0A0F`), gold/amber accent lines, thin fonts, subtle animations.
-*   **Neon Cyberpunk:** Dark base surfaces, highly saturated vivid accents (neon cyan/green), glow effects, sharp geometry.
-*   **Retro Analog:** Warm grain overlay, rounded typography, muted color palettes, physical paper-like textures.
+- **Swiss Precision:** Clean, grid-locked alignment, sans-serif typography, clinical whitespace, no decoration.
+- **Brutalist:** Raw, exposed 1px borders, monospace display fonts, high contrast, sharp corners (`radius: 2px`).
+- **Editorial:** Magazine-inspired layout, large display headings, generous margins, serif headings, single-column reading paths.
+- **Neo-Glassmorphism:** Tinted overlays, high backdrop blur (`blur(20px)`), luminous hairlines, floating modules.
+- **Soft Minimal:** Warm tinted grays (`oklch`), rounded shapes (`radius: 12px`), deep shadows, spacious margins.
+- **Dark Luxury:** Near-black base (`#0A0A0F`), gold/amber accent lines, thin fonts, subtle animations.
+- **Neon Cyberpunk:** Dark base surfaces, highly saturated vivid accents (neon cyan/green), glow effects, sharp geometry.
+- **Retro Analog:** Warm grain overlay, rounded typography, muted color palettes, physical paper-like textures.
 
 ---
 
 ## 2. Visual Identities CSS Tokens Definition
 
 ### 1. Swiss Precision
+
 ```css
 :root {
-  --font-display: "General Sans", sans-serif;
-  --font-body: "Satoshi", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-display: 'General Sans', sans-serif;
+  --font-body: 'Satoshi', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
   /* Surfaces */
-  --bg-base:           oklch(0.98 0.002 240);
-  --bg-surface:        oklch(1.00 0 0);
+  --bg-base: oklch(0.98 0.002 240);
+  --bg-surface: oklch(1 0 0);
   --bg-surface-raised: oklch(0.95 0.003 240);
 
   /* Accents */
-  --color-primary:     oklch(0.20 0.01 240);      /* Minimal black/slate */
-  --color-primary-hover: oklch(0.40 0.01 240);
+  --color-primary: oklch(0.2 0.01 240); /* Minimal black/slate */
+  --color-primary-hover: oklch(0.4 0.01 240);
 
   /* Spacing Grid */
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   /* Radii */
   --radius-sm: 0px;
@@ -59,54 +60,56 @@ Choose **ONE** direction from the list below to define the brand visual system.
 ```
 
 ### 2. Brutalist
+
 ```css
 :root {
-  --font-display: "JetBrains Mono", monospace;
-  --font-body: "General Sans", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-display: 'JetBrains Mono', monospace;
+  --font-body: 'General Sans', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
-  --bg-base:           oklch(1.00 0 0);
-  --bg-surface:        oklch(1.00 0 0);
+  --bg-base: oklch(1 0 0);
+  --bg-surface: oklch(1 0 0);
   --bg-surface-raised: oklch(0.95 0.005 240);
 
-  --color-primary:     oklch(0.60 0.28 140);      /* Acid Green */
-  --color-primary-hover: oklch(0.50 0.28 140);
+  --color-primary: oklch(0.6 0.28 140); /* Acid Green */
+  --color-primary-hover: oklch(0.5 0.28 140);
 
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   --radius-sm: 2px;
   --radius-md: 2px;
   --radius-lg: 2px;
 
-  --shadow-sm: 2px 2px 0px oklch(10% 0.01 240);  /* Hard drop shadows */
+  --shadow-sm: 2px 2px 0px oklch(10% 0.01 240); /* Hard drop shadows */
   --shadow-md: 4px 4px 0px oklch(10% 0.01 240);
   --border-subtle: 2px solid oklch(10% 0.01 240);
 }
 ```
 
 ### 3. Editorial
+
 ```css
 :root {
-  --font-display: "Playfair Display", serif;
-  --font-body: "Source Sans 3", sans-serif;
-  --font-mono: "Courier New", monospace;
+  --font-display: 'Playfair Display', serif;
+  --font-body: 'Source Sans 3', sans-serif;
+  --font-mono: 'Courier New', monospace;
 
-  --bg-base:           oklch(0.97 0.005 60);      /* Warm alabaster tint */
-  --bg-surface:        oklch(0.99 0.002 60);
+  --bg-base: oklch(0.97 0.005 60); /* Warm alabaster tint */
+  --bg-surface: oklch(0.99 0.002 60);
   --bg-surface-raised: oklch(0.94 0.008 60);
 
-  --color-primary:     oklch(0.35 0.12 25);       /* Deep terracotta red */
+  --color-primary: oklch(0.35 0.12 25); /* Deep terracotta red */
   --color-primary-hover: oklch(0.25 0.12 25);
 
-  --space-xs:  6px;
-  --space-sm:  12px;
-  --space-md:  24px;
-  --space-lg:  36px;
-  --space-xl:  48px;
+  --space-xs: 6px;
+  --space-sm: 12px;
+  --space-md: 24px;
+  --space-lg: 36px;
+  --space-xl: 48px;
 
   --radius-sm: 4px;
   --radius-md: 8px;
@@ -119,24 +122,25 @@ Choose **ONE** direction from the list below to define the brand visual system.
 ```
 
 ### 4. Neo-Glassmorphism
+
 ```css
 :root {
-  --font-display: "Clash Display", sans-serif;
-  --font-body: "Satoshi", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-display: 'Clash Display', sans-serif;
+  --font-body: 'Satoshi', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
-  --bg-base:           oklch(0.12 0.01 220);      /* Deep indigo gradient base */
-  --bg-surface:        oklch(100% 0 0 / 0.15);    /* Translucent glass */
+  --bg-base: oklch(0.12 0.01 220); /* Deep indigo gradient base */
+  --bg-surface: oklch(100% 0 0 / 0.15); /* Translucent glass */
   --bg-surface-raised: oklch(100% 0 0 / 0.25);
 
-  --color-primary:     oklch(0.70 0.22 200);      /* Electric cyan */
-  --color-primary-hover: oklch(0.60 0.22 200);
+  --color-primary: oklch(0.7 0.22 200); /* Electric cyan */
+  --color-primary-hover: oklch(0.6 0.22 200);
 
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   --radius-sm: 4px;
   --radius-md: 16px;
@@ -149,24 +153,25 @@ Choose **ONE** direction from the list below to define the brand visual system.
 ```
 
 ### 5. Soft Minimal
+
 ```css
 :root {
-  --font-display: "Geist Sans", sans-serif;
-  --font-body: "Geist Sans", sans-serif;
-  --font-mono: "Geist Mono", monospace;
+  --font-display: 'Geist Sans', sans-serif;
+  --font-body: 'Geist Sans', sans-serif;
+  --font-mono: 'Geist Mono', monospace;
 
-  --bg-base:           oklch(0.98 0.003 80);      /* Warm off-white */
-  --bg-surface:        oklch(1.00 0 0);
+  --bg-base: oklch(0.98 0.003 80); /* Warm off-white */
+  --bg-surface: oklch(1 0 0);
   --bg-surface-raised: oklch(0.96 0.005 80);
 
-  --color-primary:     oklch(0.40 0.06 200);      /* Muted graphite slate */
-  --color-primary-hover: oklch(0.30 0.06 200);
+  --color-primary: oklch(0.4 0.06 200); /* Muted graphite slate */
+  --color-primary-hover: oklch(0.3 0.06 200);
 
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   --radius-sm: 6px;
   --radius-md: 12px;
@@ -179,24 +184,25 @@ Choose **ONE** direction from the list below to define the brand visual system.
 ```
 
 ### 6. Dark Luxury
+
 ```css
 :root {
-  --font-display: "Cabinet Grotesk", sans-serif;
-  --font-body: "Satoshi", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-display: 'Cabinet Grotesk', sans-serif;
+  --font-body: 'Satoshi', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
-  --bg-base:           oklch(0.08 0.005 250);     /* OLED-friendly black */
-  --bg-surface:        oklch(0.12 0.008 250);
+  --bg-base: oklch(0.08 0.005 250); /* OLED-friendly black */
+  --bg-surface: oklch(0.12 0.008 250);
   --bg-surface-raised: oklch(0.16 0.01 250);
 
-  --color-primary:     oklch(0.78 0.12 85);       /* Gold/Amber */
+  --color-primary: oklch(0.78 0.12 85); /* Gold/Amber */
   --color-primary-hover: oklch(0.68 0.12 85);
 
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   --radius-sm: 2px;
   --radius-md: 6px;
@@ -204,29 +210,30 @@ Choose **ONE** direction from the list below to define the brand visual system.
 
   --shadow-sm: 0 1px 2px oklch(0% 0 0 / 0.3);
   --shadow-md: 0 4px 16px oklch(0% 0 0 / 0.5);
-  --border-subtle: oklch(22% 0.01 250 / 0.5);   /* Thin hairline borders */
+  --border-subtle: oklch(22% 0.01 250 / 0.5); /* Thin hairline borders */
 }
 ```
 
 ### 7. Neon Cyberpunk
+
 ```css
 :root {
-  --font-display: "Space Grotesk", sans-serif;
-  --font-body: "General Sans", sans-serif;
-  --font-mono: "JetBrains Mono", monospace;
+  --font-display: 'Space Grotesk', sans-serif;
+  --font-body: 'General Sans', sans-serif;
+  --font-mono: 'JetBrains Mono', monospace;
 
-  --bg-base:           oklch(0.05 0.01 280);      /* Deep space navy */
-  --bg-surface:        oklch(0.08 0.015 280);
+  --bg-base: oklch(0.05 0.01 280); /* Deep space navy */
+  --bg-surface: oklch(0.08 0.015 280);
   --bg-surface-raised: oklch(0.12 0.02 280);
 
-  --color-primary:     oklch(0.75 0.28 160);      /* Neon green glow */
+  --color-primary: oklch(0.75 0.28 160); /* Neon green glow */
   --color-primary-hover: oklch(0.85 0.28 160);
 
-  --space-xs:  4px;
-  --space-sm:  8px;
-  --space-md:  16px;
-  --space-lg:  24px;
-  --space-xl:  32px;
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 32px;
 
   --radius-sm: 0px;
   --radius-md: 4px;
@@ -239,24 +246,25 @@ Choose **ONE** direction from the list below to define the brand visual system.
 ```
 
 ### 8. Retro Analog
+
 ```css
 :root {
-  --font-display: "Clash Display", sans-serif;
-  --font-body: "Switzer", sans-serif;
-  --font-mono: "Courier New", monospace;
+  --font-display: 'Clash Display', sans-serif;
+  --font-body: 'Switzer', sans-serif;
+  --font-mono: 'Courier New', monospace;
 
-  --bg-base:           oklch(0.94 0.015 70);      /* Warm paper beige */
-  --bg-surface:        oklch(0.96 0.015 70);
+  --bg-base: oklch(0.94 0.015 70); /* Warm paper beige */
+  --bg-surface: oklch(0.96 0.015 70);
   --bg-surface-raised: oklch(0.91 0.02 70);
 
-  --color-primary:     oklch(0.50 0.18 45);       /* Muted rust brown */
-  --color-primary-hover: oklch(0.40 0.18 45);
+  --color-primary: oklch(0.5 0.18 45); /* Muted rust brown */
+  --color-primary-hover: oklch(0.4 0.18 45);
 
-  --space-xs:  5px;
-  --space-sm:  10px;
-  --space-md:  20px;
-  --space-lg:  30px;
-  --space-xl:  40px;
+  --space-xs: 5px;
+  --space-sm: 10px;
+  --space-md: 20px;
+  --space-lg: 30px;
+  --space-xl: 40px;
 
   --radius-sm: 4px;
   --radius-md: 8px;
@@ -272,21 +280,22 @@ Choose **ONE** direction from the list below to define the brand visual system.
 
 ## 3. Typographical Scaling (Fluid Type)
 
-*   Headings must use `clamp()` to scale fluidly with the screen width.
-*   Always include `text-wrap: balance` to prevent typographical orphans.
-*   Body text line length must be clamped to `65ch` max width.
+- Headings must use `clamp()` to scale fluidly with the screen width.
+- Always include `text-wrap: balance` to prevent typographical orphans.
+- Body text line length must be clamped to `65ch` max width.
 
 ---
 
 ## 4. Spacing Rules & Nested Radii
 
-*   Maintain the 8px grid alignment.
-*   Nested Radius Formula: `outer_radius = inner_radius + padding_inner`.
+- Maintain the 8px grid alignment.
+- Nested Radius Formula: `outer_radius = inner_radius + padding_inner`.
 
 ---
 
 ## 5. Interaction States & Transitions
 
 All buttons and active controls must define styled properties for:
-*   `hover`, `focus-visible`, `active`/`pressed`, and `disabled` states.
-*   Use spring easing curves: `cubic-bezier(0.34, 1.56, 0.64, 1)`.
+
+- `hover`, `focus-visible`, `active`/`pressed`, and `disabled` states.
+- Use spring easing curves: `cubic-bezier(0.34, 1.56, 0.64, 1)`.

package/.agent/templates/design-tokens.json

@@ -59,7 +59,10 @@
         "md": { "$value": "16px", "$type": "dimension" }
       },
       "typography": {
-        "family-sans": { "$value": "Plus Jakarta Sans, system-ui, sans-serif", "$type": "fontFamily" }
+        "family-sans": {
+          "$value": "Plus Jakarta Sans, system-ui, sans-serif",
+          "$type": "fontFamily"
+        }
       }
     },
     "soft-minimal": {
@@ -122,11 +125,11 @@
   },
 
   "spacing": {
-    "xs":  { "$value": "4px",  "$type": "dimension" },
-    "sm":  { "$value": "8px",  "$type": "dimension" },
-    "md":  { "$value": "16px", "$type": "dimension" },
-    "lg":  { "$value": "24px", "$type": "dimension" },
-    "xl":  { "$value": "32px", "$type": "dimension" }
+    "xs": { "$value": "4px", "$type": "dimension" },
+    "sm": { "$value": "8px", "$type": "dimension" },
+    "md": { "$value": "16px", "$type": "dimension" },
+    "lg": { "$value": "24px", "$type": "dimension" },
+    "xl": { "$value": "32px", "$type": "dimension" }
   },
 
   "shadow": {

package/.agent/workflows/acf.md

@@ -19,6 +19,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before distilling markdown specs into `.acf` YAML files, you MUST inspect:
+
 1. Target Document Source → Read source `.md` specification (PRD, design spec, or architecture doc)
 2. Existing Context Registry (`context/*.acf`) → Check target directory to prevent duplicate context creation
 3. YAML Schema Strictness → Validate output against ACF schema (rules, constraints, tech-stack, boundaries) before writing to disk

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

@@ -21,6 +21,7 @@ $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

package/.agent/workflows/audit.md

@@ -25,6 +25,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before triggering a full project audit, you MUST inspect:
+
 1. Workspace Package Manifest (`package.json`) → Verify installed test frameworks, linters, and dependencies
 2. Executable Scripts Inventory (`.agent/scripts/`) → Verify presence of `security_scan.js`, `lint_runner.js`, and `test_runner.js`
 3. Pipeline Execution Constraints → Confirm fixed execution order (Security → Dependencies → Type Check → Lint → Schema → Tests → Bundle) and HALT rules on critical CVE findings

package/.agent/workflows/brainstorm.md

@@ -20,6 +20,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating options or conducting Socratic architectural exploration, you MUST inspect:
+
 1. Technology Stack Manifest (`package.json`, `tsconfig.json`) → Confirm existing language/framework versions and active library boundaries
 2. Workspace File Layout → Understand current module scale and project structure before proposing architectural shifts
 3. Pure Exploration Constraint → Enforce zero code edits or file creation during brainstorm phase; restrict output to options, tradeoffs, and recommendations

package/.agent/workflows/changelog.md

@@ -20,6 +20,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating changelogs or parsing git history, you MUST inspect:
+
 1. Git Commit Trajectory (`git log --oneline -30`) → Verify presence of conventional commit tags (`feat:`, `fix:`, `chore:`, `BREAKING CHANGE:`)
 2. Package Manifest & Version (`package.json`) → Retrieve current release version and target release tag
 3. Keep a Changelog Formatting Standard → Enforce categories: Added, Changed, Deprecated, Removed, Fixed, Security

package/.agent/workflows/contract.md

@@ -0,0 +1,60 @@
+# /contract — AI Agent Behavioral Contract Testing & Trace Replay
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before running behavioral contract validation, inspect:
+
+1. Active Contracts Directory (`.tribunal/contracts/`) → Verify active `.yaml` rules and severities
+2. Target File Scope → Determine modified or targeted files for contract validation
+3. Failure Context Snapshots (`.tribunal/traces/`) → Check past captured trace snapshots for context
+
+---
+
+## When to Use /contract
+
+| Use `/contract` when...                | Move to...                             |
+| :------------------------------------- | :------------------------------------- |
+| Defining team behavioral rules         | After contract violation → `/fix`      |
+| Verifying AI code before merge         | On failure → `tk contract replay <id>` |
+| Converting Case Law to permanent rules | After verification → `/deploy`         |
+
+---
+
+## Subcommands Overview
+
+```bash
+# Scaffold .tribunal/contracts/ with starter rules
+npx tribunal-kit contract init
+
+# Verify all project code against loaded contracts
+npx tribunal-kit contract verify
+
+# Verify a single file against contracts
+npx tribunal-kit contract verify --file src/api/user.ts
+
+# List active loaded contracts and rules
+npx tribunal-kit contract list
+
+# List failure context snapshots
+npx tribunal-kit contract trace list
+
+# Replay a failure context trace snapshot in CLI
+npx tribunal-kit contract replay <trace_id>
+
+# Auto-generate a contract template from a Case Law entry
+npx tribunal-kit contract generate --from-case 14
+```
+
+---
+
+## Behavioral Contract Guard
+
+```
+❌ Never ignore 'block' severity contract violations before push
+❌ Never bypass contract checks without explicit team approval
+❌ Always convert repeated Case Law rejections into behavioral contracts
+```

package/.agent/workflows/create.md

@@ -22,6 +22,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before scaffolding a new application, you MUST inspect:
+
 1. Target Directory State → Confirm directory listing is empty or obtain explicit user confirmation before overwriting existing files
 2. Runtime & Environment Context → Check Node/npm version and inspect `.env.example` if available
 3. Human Gate Before Disk Modification → Enforce explicit approval of Socratic requirements, stack selection, and scaffolding plan before creating any files

package/.agent/workflows/debug.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before investigating or attempting any code modification during a bug report, you MUST inspect:
+
 1. Exact Error Traceback / Stack Log → Read raw error logs without paraphrasing; ban making diagnostic hypotheses without tracebacks
 2. Target File & Callers → Inspect file referenced in error trace along with its upstream callers
 3. Recent Changes (`git diff`) → Inspect recent edits to identify regressions before mutating code

package/.agent/workflows/deploy.md

@@ -22,6 +22,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before triggering production deployment or executing deploy scripts, you MUST inspect:
+
 1. Full Pre-Flight Verification Suite (`verify_all.js`) → Verify tests, type-checking, lint, security scans, and production build output cleanly
 2. CI/CD Manifests (`.github/workflows`, `fly.toml`, `render.yaml`, etc.) → Check deployment targets and environment variable requirements
 3. Human Gate & Rollback Baseline → Confirm baseline git tag/commit and secure explicit human approval before publishing release

package/.agent/workflows/enhance.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before modifying existing features or appending functionality, you MUST inspect:
+
 1. Impact Zone Identification → Grep for all callers and importers of the target file to map blast radius
 2. Existing Contract & Unit Tests → Inspect existing tests and type signatures for the target module to prevent regression
 3. Breaking Change Detection → Ensure signature changes update all dependent call sites simultaneously before writing to disk

package/.agent/workflows/fix-ci.md

@@ -0,0 +1,89 @@
+---
+description: Automated CI/CD Failure Diagnosis & Repair. Parses raw GitHub Actions/GitLab CI runner logs, identifies the root cause (lockfile drift, missing environment variables, matrix incompatibilities, test timeouts, or syntax errors), and produces validated fixes.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-08-14
+required-skills:
+  - cicd-pro
+  - diagnosing-bugs
+  - devops-engineer
+scripts-binding:
+  - .agent/scripts/cicd_validator.js
+  - .agent/scripts/test_runner.js
+  - .agent/scripts/lint_runner.js
+---
+
+# /fix-ci — Automated Pipeline Failure Resolution
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before attempting to fix CI pipeline failures:
+
+1. Parse Failing Runner Log → Identify exact step, exit code, and stack trace or runner error message
+2. Inspect Workflow YAML & Project Configs → Compare runner environment (Node/Python/OS version) with local workspace
+3. Human Gate Before Disk Write → Present root cause explanation and proposed diff for approval
+
+---
+
+## 4-Step CI Diagnosis & Repair Loop
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ 1. LOG INGESTION                                            │
+│    User pastes failed CI log or step output                 │
+│    Extract: Step Name, Error Code, Root Stack Trace        │
+│                                                             │
+│ 2. CLASSIFICATION                                           │
+│    □ Lockfile / Dependency Drift (npm ci vs package.json)   │
+│    □ Environment / Missing Secret / Missing Env Var        │
+│    □ Version / Runner Matrix Incompatibility               │
+│    □ Test / Lint / Typecheck Failure in CI Context         │
+│    □ Service Container (DB/Redis) Connection Timeout       │
+│                                                             │
+│ 3. REPRODUCTION & ROOT CAUSE ISOLATION                      │
+│    Simulate failing step locally using test/lint runners   │
+│                                                             │
+│ 4. REMEDIATION & VALIDATION                                 │
+│    Apply fix to code or workflow YAML                       │
+│    Run .agent/scripts/cicd_validator.js                     │
+│    Submit through /tribunal-cicd Human Gate                │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Common CI Failure Root Causes & Fix Recipes
+
+### 1. `npm ci` ERESOLVE / Lockfile Drift
+
+- **Symptom:** `npm error code EUSAGE / ERESOLVE` or `npm ci can only install when package.json and package-lock.json are in sync`.
+- **Fix:** Run `npm install` locally to update lockfile and commit the synced `package-lock.json`.
+
+### 2. Missing Environment Variables / Secrets
+
+- **Symptom:** `process.env.DATABASE_URL is undefined` during build or test steps in CI.
+- **Fix:** Add dummy or mock environment variables to the workflow step `env:` block (e.g. `DATABASE_URL: "postgresql://postgres:postgres@localhost:5432/test"`).
+
+### 3. Missing Service Container Healthchecks
+
+- **Symptom:** Test step cannot connect to Postgres/Redis service in GitHub Actions runner.
+- **Fix:** Add `options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5` to the service container definition.
+
+### 4. Runner OS / Architecture Differences
+
+- **Symptom:** Native binary module (e.g. `sharp`, `bcrypt`, `@swc/core`) fails to load on `ubuntu-latest`.
+- **Fix:** Ensure correct optional dependencies or add OS matrix build steps.
+
+---
+
+## Usage Examples
+
+```
+/fix-ci [paste failed GitHub Actions log]
+/fix-ci the test job failed on ubuntu-latest Node 22 with exit code 1
+/fix-ci error: package-lock.json out of sync during npm ci
+```

package/.agent/workflows/fix.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before executing auto-fixers or modifying code files to resolve lint/type issues, you MUST inspect:
+
 1. Workspace Linter & Compiler Settings (`tsconfig.json`, `.eslintrc`, `biome.json`) → Confirm rule strictness and formatting standards
 2. Target File Lint Output → Execute `node .agent/scripts/lint_runner.js` to gather precise error line numbers and rule IDs
 3. Diff Verification Before Disk Write → Show explicit diff of proposed changes and confirm Human Gate approval before saving

package/.agent/workflows/generate.md

@@ -22,6 +22,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before generating code modules or invoking the Maker pipeline, you MUST inspect:
+
 1. Workspace Package Dependencies (`package.json`) → Confirm all imported libraries exist; ban unverified phantom imports
 2. Type Definitions & Path Aliases (`tsconfig.json`) → Verify module resolution paths and compiler strictness
 3. Parallel Tribunal Review Assignment → Select relevant domain reviewers (`logic`, `security`, `frontend`, `backend`, `database`, `mobile`) prior to Human Gate submission

package/.agent/workflows/marathon.md

@@ -21,6 +21,7 @@ $ARGUMENTS
 ## Mandatory Pre-Flight Context Inspection
 
 Before initiating or resuming a multi-session marathon harness, you MUST inspect:
+
 1. Marathon State Ledger (`progress.json`, `feature_list.json`) → Verify current session index, completed features, and active task
 2. Session Continuity Manager (`.agent/scripts/session_manager.js`) → Verify state snapshot before context truncation
 3. Atomic Feature Handoff Protocol → Ensure each session completes exactly ONE atomic feature, runs `verify_all.js`, and commits state before handoff