tribunal-kit 4.5.0 → 4.6.0

package/.agent/skills/powershell-windows/SKILL.md

@@ -1,166 +1,164 @@
----
-name: powershell-windows
-description: PowerShell and Windows environment mastery. Object-oriented piping, strict error handling (ErrorActionPreference), PSProviders, active directory querying, credential management, and execution policies. Use when automating Azure, Windows environments, or writing .ps1 scripts.
-allowed-tools: Read, Write, Edit, Glob, Grep
-version: 2.0.0
-last-updated: 2026-04-02
-applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
----
-
-# PowerShell — Windows Automation Mastery
-
----
-
-## 1. The Object Pipeline
-
-Unlike Bash where everything is strings (requiring `awk`/`grep`), PowerShell passes structured .NET class instances between commands.
-
-```powershell
-# ❌ BAD: Attempting to treat PowerShell like Bash (String Parsing)
-Get-Process | Out-String -Stream | Select-String "node" | ForEach-Object { $id = ($_ -split '\s+')[8]; Stop-Process -Id $id }
-
-# ✅ GOOD: Accessing Object Properties Directly
-Get-Process -Name "node" | Stop-Process -Force
-
-# Filtering objects (Where-Object)
-Get-Service | Where-Object Status -eq 'Running' | Select-Object Name, DisplayName
-
-# Accessing methods natively on the object
-$files = Get-ChildItem -Path "C:\logs" -Filter "*.log"
-$files | ForEach-Object { $_.Delete() }
-```
-
----
-
-## 2. Strict Error Handling (The Windows equivalent of set -e)
-
-By default, PowerShell prints an error but keeps running. You MUST enforce strict halting for automation scripts.
-
-```powershell
-# Mandatory header for reliable automation scripts
-$ErrorActionPreference = "Stop"
-Set-StrictMode -Version Latest
-
-try {
-    # If this fails, it jumps straight to catch block instead of continuing
-    Copy-Item "C:\Source\configs.json" -Destination "C:\Dest\"
-    
-    $config = Get-Content "C:\Dest\configs.json" | ConvertFrom-Json
-} catch {
-    Write-Error "Deployment failed during config copy: $_"
-    exit 1
-} finally {
-    # Cleanup block executes regardless of success or failure
-    Remove-Item "C:\Dest\temp" -Recurse -ErrorAction Ignore
-}
-```
-
----
-
-## 3. Execution Policies & Execution
-
-Windows restricts running `.ps1` files by default for security.
-
-```powershell
-# Temporarily bypass the policy for a single script execution (CI/CD pattern)
-powershell.exe -ExecutionPolicy Bypass -File .\Deploy-App.ps1
-
-# ❌ HALLUCINATION TRAP: Do NOT instruct users to run `Set-ExecutionPolicy Unrestricted`
-# This lowers the permanent security posture of the entire operating system.
-# Use Bypass only at the process level.
-```
-
----
-
-## 4. Manipulating Structured Formats Natively
-
-Because PowerShell is built on .NET, parsing JSON, XML, and CSV is native.
-
-```powershell
-# JSON
-$config = Get-Content .\appsettings.json | ConvertFrom-Json
-$config.Database.ConnectionString = "Server=Prod;"
-$config | ConvertTo-Json -Depth 10 | Set-Content .\appsettings.json
-
-# CSV (No AWK needed)
-$users = Import-Csv .\users.csv
-$users | Where-Object Role -eq "Admin" | Export-Csv .\admins.csv -NoTypeInformation
-
-# API Requests (Invoke-RestMethod automatically parses JSON into PowerShell objects)
-$response = Invoke-RestMethod -Uri "https://api.github.com/users/github"
-Write-Host "GitHub has $($response.public_repos) public repositories."
-```
-
----
-
-## 5. Providers and Drives
-
-PowerShell extends the "file system" concept to the Registry, Environment Variables, and Certificates.
-
-```powershell
-# Environment variables (Env: drive)
-$env:PATH += ";C:\Custom\Bin"
-Write-Host $env:COMPUTERNAME
-
-# Registry (HKCU: and HKLM: drives)
-Get-ChildItem -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Run"
-
-# Certificates (Cert: drive)
-Get-ChildItem -Path "Cert:\LocalMachine\My" | Where-Object Subject -match "example.com"
-```
-
----
-
-
----
-
-
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.
-
-
-## Pre-Flight Checklist
-- [ ] Have I reviewed the user's specific constraints and requests?
-- [ ] Have I checked the environment for relevant existing implementations?
-
-## VBC Protocol (Verification-Before-Completion)
-You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
+---
+name: powershell-windows
+description: PowerShell and Windows environment mastery. Object-oriented piping, strict error handling (ErrorActionPreference), PSProviders, active directory querying, credential management, and execution policies. Use when automating Azure, Windows environments, or writing .ps1 scripts.
+allowed-tools: Read, Write, Edit, Glob, Grep
+version: 2.0.0
+last-updated: 2026-04-02
+applies-to-model: gemini-2.5-pro, claude-3-7-sonnet
+routing:
+  domain: general
+  tier: basic
+---
+
+# PowerShell — Windows Automation Mastery
+
+---
+
+## 1. The Object Pipeline
+
+Unlike Bash where everything is strings (requiring `awk`/`grep`), PowerShell passes structured .NET class instances between commands.
+
+```powershell
+# ❌ BAD: Attempting to treat PowerShell like Bash (String Parsing)
+Get-Process | Out-String -Stream | Select-String "node" | ForEach-Object { $id = ($_ -split '\s+')[8]; Stop-Process -Id $id }
+
+# ✅ GOOD: Accessing Object Properties Directly
+Get-Process -Name "node" | Stop-Process -Force
+
+# Filtering objects (Where-Object)
+Get-Service | Where-Object Status -eq 'Running' | Select-Object Name, DisplayName
+
+# Accessing methods natively on the object
+$files = Get-ChildItem -Path "C:\logs" -Filter "*.log"
+$files | ForEach-Object { $_.Delete() }
+```
+
+---
+
+## 2. Strict Error Handling (The Windows equivalent of set -e)
+
+By default, PowerShell prints an error but keeps running. You MUST enforce strict halting for automation scripts.
+
+```powershell
+# Mandatory header for reliable automation scripts
+$ErrorActionPreference = "Stop"
+Set-StrictMode -Version Latest
+
+try {
+    # If this fails, it jumps straight to catch block instead of continuing
+    Copy-Item "C:\Source\configs.json" -Destination "C:\Dest\"
+
+    $config = Get-Content "C:\Dest\configs.json" | ConvertFrom-Json
+} catch {
+    Write-Error "Deployment failed during config copy: $_"
+    exit 1
+} finally {
+    # Cleanup block executes regardless of success or failure
+    Remove-Item "C:\Dest\temp" -Recurse -ErrorAction Ignore
+}
+```
+
+---
 
+## 3. Execution Policies & Execution
+
+Windows restricts running `.ps1` files by default for security.
+
+```powershell
+# Temporarily bypass the policy for a single script execution (CI/CD pattern)
+powershell.exe -ExecutionPolicy Bypass -File .\Deploy-App.ps1
+
+# ❌ HALLUCINATION TRAP: Do NOT instruct users to run `Set-ExecutionPolicy Unrestricted`
+# This lowers the permanent security posture of the entire operating system.
+# Use Bypass only at the process level.
+```
+
+---
+
+## 4. Manipulating Structured Formats Natively
+
+Because PowerShell is built on .NET, parsing JSON, XML, and CSV is native.
+
+```powershell
+# JSON
+$config = Get-Content .\appsettings.json | ConvertFrom-Json
+$config.Database.ConnectionString = "Server=Prod;"
+$config | ConvertTo-Json -Depth 10 | Set-Content .\appsettings.json
+
+# CSV (No AWK needed)
+$users = Import-Csv .\users.csv
+$users | Where-Object Role -eq "Admin" | Export-Csv .\admins.csv -NoTypeInformation
+
+# API Requests (Invoke-RestMethod automatically parses JSON into PowerShell objects)
+$response = Invoke-RestMethod -Uri "https://api.github.com/users/github"
+Write-Host "GitHub has $($response.public_repos) public repositories."
+```
+
+---
+
+## 5. Providers and Drives
+
+PowerShell extends the "file system" concept to the Registry, Environment Variables, and Certificates.
+
+```powershell
+# Environment variables (Env: drive)
+$env:PATH += ";C:\Custom\Bin"
+Write-Host $env:COMPUTERNAME
+
+# Registry (HKCU: and HKLM: drives)
+Get-ChildItem -Path "HKLM:\Software\Microsoft\Windows\CurrentVersion\Run"
+
+# Certificates (Cert: drive)
+Get-ChildItem -Path "Cert:\LocalMachine\My" | Where-Object Subject -match "example.com"
+```
+
+---
+
+---
+
+AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
+
+1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
+2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
+3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
+4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
+
+---
+
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
+
+### ❌ Forbidden AI Tropes
+
+1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
+2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
+3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+
+Review these questions before confirming output:
+
+```
+✅ Did I rely ONLY on real, verified tools and methods?
+✅ Is this solution appropriately scoped to the user's constraints?
+✅ Did I handle potential failure modes and edge cases?
+✅ Have I avoided generic boilerplate that doesn't add value?
+```
+
+### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.
+
+## Pre-Flight Checklist
+
+- [ ] Have I reviewed the user's specific constraints and requests?
+- [ ] Have I checked the environment for relevant existing implementations?
+
+## VBC Protocol (Verification-Before-Completion)
+
+You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
 
 ---
 
@@ -190,6 +188,7 @@ AI coding assistants often fall into specific bad habits when dealing with this
 ### ✅ Pre-Flight Self-Audit
 
 Review these questions before confirming output:
+
 ```
 ✅ Did I rely ONLY on real, verified tools and methods?
 ✅ Is this solution appropriately scoped to the user's constraints?
@@ -200,5 +199,6 @@ Review these questions before confirming output:
 ### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.

package/.agent/skills/project-idioms/SKILL.md

@@ -1,141 +1,139 @@
----
-name: project-idioms
-description: >
-  Auto-evolved skill containing project-specific architectural idioms extracted
-  from the developer's own code decisions. Generated by skill_evolution.py.
-  Commit this file to share your Engineering Culture across the team.
-  Every agent MUST respect these idioms above generic defaults.
-version: auto
-last-updated: 2026-04-09
-digest-cycles: 0
-pattern: generator
----
-
-## Hallucination Traps (Read First)
-- ❌ Overriding project idioms without explicit justification -> ✅ Idioms represent team decisions; flag deviations with reasoning
-- ❌ Applying idioms from one project to a different project -> ✅ Idioms are project-specific; verify they apply to the current codebase
-
----
-
-
-# Project Idioms — Auto-Evolved Skill
-
-> **Authority Level: ABSOLUTE**
-> These idioms were extracted from this project's actual code decisions.
-> They override all generic agent defaults and best practices.
-> Every agent reads this file on activation and adapts its proposals accordingly.
-
----
-
-## How Idioms Are Born
-
-1. Developer commits code that **differs** from what the AI proposed.
-2. `skill_evolution.py digest` extracts the architectural delta (semantic filter).
-3. A minimal LLM prompt (< 500 tokens) identifies the **WHY** behind the change.
-4. The idiom is recorded here with a stable pattern + reason pair.
-5. All future code generations must align with these idioms.
-
----
-
-## Recorded Idioms
-
-| ID | Pattern | Why This Project Uses It | Domain | Since |
-|:---|:--------|:-------------------------|:-------|:------|
-| — | — | _No idioms recorded yet. Run your first digest cycle._ | — | — |
-
----
-
-## How to Add New Idioms
-
-Run after committing or staging a meaningful architectural change:
-
-```bash
-# Analyze staged changes (default)
-python .agent/scripts/skill_evolution.py digest
-
-# Preview without writing
-python .agent/scripts/skill_evolution.py digest --dry-run
-
-# Analyze last commit instead of staged
-python .agent/scripts/skill_evolution.py digest --head
-
-# Check current idiom count and token savings
-python .agent/scripts/skill_evolution.py status
-```
-
----
-
-## Enforcement Rules for All Agents
-
-```
-□ Before proposing any code: scan the idiom table above
-□ If your proposal contradicts an idiom → flag it explicitly with:
-     "⚠️ Note: My proposal differs from Project Idiom #N. Reason: [explain]"
-□ Never override an idiom silently
-□ When citing an idiom in a review:
-     "Per Project Idiom #N: [pattern] — [reason]"
-□ If no idioms yet → proceed with domain-standard approaches
-```
-
----
-
-## Digest History
-
-Last digest: `never`
-Total cycles: `0`
-
-Run `python .agent/scripts/skill_evolution.py status` to see full statistics.
-
-
----
-
-
-
-AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
-
-1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
-2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
-3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
-4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
-
----
-
-
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
-
-
-Review these questions before confirming output:
-```
-✅ Did I rely ONLY on real, verified tools and methods?
-✅ Is this solution appropriately scoped to the user's constraints?
-✅ Did I handle potential failure modes and edge cases?
-✅ Have I avoided generic boilerplate that doesn't add value?
-```
-
-### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.
-
-
-## Pre-Flight Checklist
-- [ ] Have I reviewed the user's specific constraints and requests?
-- [ ] Have I checked the environment for relevant existing implementations?
-
-## VBC Protocol (Verification-Before-Completion)
-You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
+---
+name: project-idioms
+description: >
+  Auto-evolved skill containing project-specific architectural idioms extracted
+  from the developer's own code decisions. Generated by skill_evolution.py.
+  Commit this file to share your Engineering Culture across the team.
+  Every agent MUST respect these idioms above generic defaults.
+version: auto
+last-updated: 2026-04-09
+digest-cycles: 0
+pattern: generator
+routing:
+  domain: general
+  tier: basic
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Overriding project idioms without explicit justification -> ✅ Idioms represent team decisions; flag deviations with reasoning
+- ❌ Applying idioms from one project to a different project -> ✅ Idioms are project-specific; verify they apply to the current codebase
+
+---
+
+# Project Idioms — Auto-Evolved Skill
+
+> **Authority Level: ABSOLUTE**
+> These idioms were extracted from this project's actual code decisions.
+> They override all generic agent defaults and best practices.
+> Every agent reads this file on activation and adapts its proposals accordingly.
+
+---
+
+## How Idioms Are Born
+
+1. Developer commits code that **differs** from what the AI proposed.
+2. `skill_evolution.py digest` extracts the architectural delta (semantic filter).
+3. A minimal LLM prompt (< 500 tokens) identifies the **WHY** behind the change.
+4. The idiom is recorded here with a stable pattern + reason pair.
+5. All future code generations must align with these idioms.
+
+---
+
+## Recorded Idioms
+
+| ID  | Pattern | Why This Project Uses It                               | Domain | Since |
+| :-- | :------ | :----------------------------------------------------- | :----- | :---- |
+| —   | —       | _No idioms recorded yet. Run your first digest cycle._ | —      | —     |
+
+---
+
+## How to Add New Idioms
+
+Run after committing or staging a meaningful architectural change:
+
+```bash
+# Analyze staged changes (default)
+python .agent/scripts/skill_evolution.py digest
+
+# Preview without writing
+python .agent/scripts/skill_evolution.py digest --dry-run
+
+# Analyze last commit instead of staged
+python .agent/scripts/skill_evolution.py digest --head
+
+# Check current idiom count and token savings
+python .agent/scripts/skill_evolution.py status
+```
+
+---
+
+## Enforcement Rules for All Agents
+
+```
+□ Before proposing any code: scan the idiom table above
+□ If your proposal contradicts an idiom → flag it explicitly with:
+     "⚠️ Note: My proposal differs from Project Idiom #N. Reason: [explain]"
+□ Never override an idiom silently
+□ When citing an idiom in a review:
+     "Per Project Idiom #N: [pattern] — [reason]"
+□ If no idioms yet → proceed with domain-standard approaches
+```
+
+---
+
+## Digest History
+
+Last digest: `never`
+Total cycles: `0`
+
+Run `python .agent/scripts/skill_evolution.py status` to see full statistics.
+
+---
+
+AI coding assistants often fall into specific bad habits when dealing with this domain. These are strictly forbidden:
 
+1. **Over-engineering:** Proposing complex abstractions or distributed systems when a simpler approach suffices.
+2. **Hallucinated Libraries/Methods:** Using non-existent methods or packages. Always `// VERIFY` or check `package.json` / `requirements.txt`.
+3. **Skipping Edge Cases:** Writing the "happy path" and ignoring error handling, timeouts, or data validation.
+4. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+5. **Silent Degradation:** Catching and suppressing errors without logging or re-raising.
+
+---
+
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
+
+### ❌ Forbidden AI Tropes
+
+1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
+2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
+3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+
+Review these questions before confirming output:
+
+```
+✅ Did I rely ONLY on real, verified tools and methods?
+✅ Is this solution appropriately scoped to the user's constraints?
+✅ Did I handle potential failure modes and edge cases?
+✅ Have I avoided generic boilerplate that doesn't add value?
+```
+
+### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.
+
+## Pre-Flight Checklist
+
+- [ ] Have I reviewed the user's specific constraints and requests?
+- [ ] Have I checked the environment for relevant existing implementations?
+
+## VBC Protocol (Verification-Before-Completion)
+
+You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
 
 ---
 
@@ -165,6 +163,7 @@ AI coding assistants often fall into specific bad habits when dealing with this
 ### ✅ Pre-Flight Self-Audit
 
 Review these questions before confirming output:
+
 ```
 ✅ Did I rely ONLY on real, verified tools and methods?
 ✅ Is this solution appropriately scoped to the user's constraints?
@@ -175,5 +174,6 @@ Review these questions before confirming output:
 ### 🛑 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 tests, compile success, or equivalent proof) that your output works as intended.