tribunal-kit 9.2.4 → 9.2.5

package/.agent/workflows/changelog.md

@@ -1,152 +1,152 @@
----
-description: Auto-generate changelogs from git history. Categorizes commits by type (feat/fix/chore/breaking) and follows Keep a Changelog format. Requires conventional commit messages for accurate categorization.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 3.0.0
-last-updated: 2026-07-30
-required-skills:
-  - github-operations
-  - git-pro
-  - readme-builder
-scripts-binding:
-  - .agent/scripts/lint_runner.js
----
-
-# /changelog — Git History to Changelog
-
-$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
-
-4. Required Skills → Before executing, load and follow procedural rules from:
-   - `github-operations` (.agent/skills/github-operations/SKILL.md): Git workflows, branching strategies, and PR management
-   - `git-pro` (.agent/skills/git-pro/SKILL.md): Advanced git operations, rebasing, cherry-picking
-   - `readme-builder` (.agent/skills/readme-builder/SKILL.md): README generation and documentation structure
-
----
-
-## When to Use /changelog
-
-| Use `/changelog` when...               |                                     |
-| :------------------------------------- | :---------------------------------- |
-| Preparing a release                    | Generate for specific version range |
-| Documenting recent changes             | Generate since last tag             |
-| Onboarding someone to codebase history | Generate entire history             |
-
----
-
-## Commit Convention (Required for Accuracy)
-
-```
-Format: <type>(<scope>): <description>
-
-Types:
-  feat:     New functionality (appears in "Added")
-  fix:      Bug fix (appears in "Fixed")
-  chore:    Maintenance, deps (appears in "Changed")
-  docs:     Documentation only
-  perf:     Performance improvement (appears in "Changed")
-  refactor: Internal restructuring (appears in "Changed")
-  test:     Test-only changes
-  BREAKING CHANGE: Footer or body annotation (appears in "Breaking Changes")
-```
-
----
-
-## Git Log Commands
-
-```bash
-# Since last tag
-git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
-
-# Since a specific date
-git log --since="2026-01-01" --oneline --no-merges
-
-# Since specific commit
-git log abc123def..HEAD --oneline --no-merges
-
-# With full commit message (for BREAKING CHANGE in body)
-git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s%n%b"
-```
-
----
-
-## Output Format (Keep a Changelog)
-
-```markdown
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [Unreleased]
-
-## [1.2.0] — 2026-04-02
-
-### Breaking Changes
-
-- **auth**: JWT token format changed — clients must re-authenticate ([abc123](link))
-
-### Added
-
-- User notification system with email and in-app alerts ([def456](link))
-- Pagination on /api/users endpoint with meta.total in response ([ghi789](link))
-
-### Fixed
-
-- JWT verify no longer accepts 'none' algorithm ([jkl012](link))
-- Checkout form no longer loses data on page refresh ([mno345](link))
-
-### Changed
-
-- Upgraded Prisma 5 to 6 — findOne calls migrated to findUnique ([pqr678](link))
-- Bundle size reduced 64% via dynamic import for chart library ([stu901](link))
-
-## [1.1.0] — 2026-03-15
-
-[...]
-
-[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
-[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
-```
-
----
-
-## Semver Decision Guide
-
-```
-MAJOR (1.0.0 → 2.0.0): Any BREAKING CHANGE
-MINOR (1.0.0 → 1.1.0): New features, backward-compatible (feat:)
-PATCH (1.0.0 → 1.0.1): Bug fixes only (fix:)
-```
-
----
-
-## Usage Examples
-
-```
-/changelog since last release tag
-/changelog for version 1.2.0 including all commits since v1.1.0
-/changelog since 2026-01-01
-/changelog what changed in the authentication module this month
-```
-
----
-
-## After /changelog — Next Steps
-
-| Outcome                             | Next Command                        |
-| :---------------------------------- | :---------------------------------- |
-| Changelog updated, ready to release | → `/deploy` or tag version          |
-| Need to summarize for non-technical | → Request PR description generation |
-
----
+---
+description: Auto-generate changelogs from git history. Categorizes commits by type (feat/fix/chore/breaking) and follows Keep a Changelog format. Requires conventional commit messages for accurate categorization.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - github-operations
+  - git-pro
+  - readme-builder
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+---
+
+# /changelog — Git History to Changelog
+
+$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
+
+4. Required Skills → Before executing, load and follow procedural rules from:
+   - `github-operations` (.agent/skills/github-operations/SKILL.md): Git workflows, branching strategies, and PR management
+   - `git-pro` (.agent/skills/git-pro/SKILL.md): Advanced git operations, rebasing, cherry-picking
+   - `readme-builder` (.agent/skills/readme-builder/SKILL.md): README generation and documentation structure
+
+---
+
+## When to Use /changelog
+
+| Use `/changelog` when...               |                                     |
+| :------------------------------------- | :---------------------------------- |
+| Preparing a release                    | Generate for specific version range |
+| Documenting recent changes             | Generate since last tag             |
+| Onboarding someone to codebase history | Generate entire history             |
+
+---
+
+## Commit Convention (Required for Accuracy)
+
+```
+Format: <type>(<scope>): <description>
+
+Types:
+  feat:     New functionality (appears in "Added")
+  fix:      Bug fix (appears in "Fixed")
+  chore:    Maintenance, deps (appears in "Changed")
+  docs:     Documentation only
+  perf:     Performance improvement (appears in "Changed")
+  refactor: Internal restructuring (appears in "Changed")
+  test:     Test-only changes
+  BREAKING CHANGE: Footer or body annotation (appears in "Breaking Changes")
+```
+
+---
+
+## Git Log Commands
+
+```bash
+# Since last tag
+git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
+
+# Since a specific date
+git log --since="2026-01-01" --oneline --no-merges
+
+# Since specific commit
+git log abc123def..HEAD --oneline --no-merges
+
+# With full commit message (for BREAKING CHANGE in body)
+git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s%n%b"
+```
+
+---
+
+## Output Format (Keep a Changelog)
+
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [1.2.0] — 2026-04-02
+
+### Breaking Changes
+
+- **auth**: JWT token format changed — clients must re-authenticate ([abc123](link))
+
+### Added
+
+- User notification system with email and in-app alerts ([def456](link))
+- Pagination on /api/users endpoint with meta.total in response ([ghi789](link))
+
+### Fixed
+
+- JWT verify no longer accepts 'none' algorithm ([jkl012](link))
+- Checkout form no longer loses data on page refresh ([mno345](link))
+
+### Changed
+
+- Upgraded Prisma 5 to 6 — findOne calls migrated to findUnique ([pqr678](link))
+- Bundle size reduced 64% via dynamic import for chart library ([stu901](link))
+
+## [1.1.0] — 2026-03-15
+
+[...]
+
+[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
+[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
+```
+
+---
+
+## Semver Decision Guide
+
+```
+MAJOR (1.0.0 → 2.0.0): Any BREAKING CHANGE
+MINOR (1.0.0 → 1.1.0): New features, backward-compatible (feat:)
+PATCH (1.0.0 → 1.0.1): Bug fixes only (fix:)
+```
+
+---
+
+## Usage Examples
+
+```
+/changelog since last release tag
+/changelog for version 1.2.0 including all commits since v1.1.0
+/changelog since 2026-01-01
+/changelog what changed in the authentication module this month
+```
+
+---
+
+## After /changelog — Next Steps
+
+| Outcome                             | Next Command                        |
+| :---------------------------------- | :---------------------------------- |
+| Changelog updated, ready to release | → `/deploy` or tag version          |
+| Need to summarize for non-technical | → Request PR description generation |
+
+---

package/.agent/workflows/compare-web.md

@@ -1,35 +1,35 @@
----
-description: Visual regression comparison between two URLs (e.g. dev/staging vs. production). Captures synchronized screenshots, computes pixel mismatch percentage, and enforces release gating.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 1.0.0
-last-updated: 2026-09-13
-required-skills:
-  - browser-audit
-  - web-quality-audit
-scripts-binding:
-  - dist/commands/compare-web.js
----
-
-# /compare-web — Visual Regression & Layout Diffing
-
-$ARGUMENTS
-
----
-
-## 1. Objective
-
-Compares a staging or local development build against production to detect accidental layout shifts, broken styling, or visual regressions before shipping.
-
-## 2. Usage
-
-```bash
-# Terminal execution
-tk compare-web http://localhost:3000 https://prod.example.com --max-diff 1.0
-```
-
-## 3. Reviewer Behavior
-
-1. Captures viewports at standard 1280x800 resolution.
-2. Compares pixel difference ratio.
-3. If difference is within `--max-diff` threshold (default 1.0%), passes verification.
-4. If difference exceeds threshold, highlights regression and requests human review.
+---
+description: Visual regression comparison between two URLs (e.g. dev/staging vs. production). Captures synchronized screenshots, computes pixel mismatch percentage, and enforces release gating.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 1.0.0
+last-updated: 2026-09-13
+required-skills:
+  - browser-audit
+  - web-quality-audit
+scripts-binding:
+  - src/commands/compare-web.js
+---
+
+# /compare-web — Visual Regression & Layout Diffing
+
+$ARGUMENTS
+
+---
+
+## 1. Objective
+
+Compares a staging or local development build against production to detect accidental layout shifts, broken styling, or visual regressions before shipping.
+
+## 2. Usage
+
+```bash
+# Terminal execution
+tk compare-web http://localhost:3000 https://prod.example.com --max-diff 1.0
+```
+
+## 3. Reviewer Behavior
+
+1. Captures viewports at standard 1280x800 resolution.
+2. Compares pixel difference ratio.
+3. If difference is within `--max-diff` threshold (default 1.0%), passes verification.
+4. If difference exceeds threshold, highlights regression and requests human review.

package/.agent/workflows/context.md

@@ -1,102 +1,102 @@
----
-description: Generates an elite Flight Data HUD context dossier for any file, multi-file pair, or project folder. Maintains a living codebase context vault with drift detection.
-tools: Read, Grep, Glob, Bash, Write
-version: 3.0.0
-last-updated: 2026-09-13
-required-skills:
-  - plan-writing
-  - clean-code
-  - documentation-templates
-scripts-binding:
-  - scripts/context_compiler.js
----
-
-# /context — Living Codebase & File Context Engine
-
-$ARGUMENTS
-
----
-
-## Mandatory Pre-Flight Context Inspection
-
-Before generating context dossiers or inspecting workspace files, you MUST:
-
-1. **Input Normalization** → Strip any surrounding single or double quotes, resolve IDE drag-and-drop file paths, and handle Windows/POSIX path separators.
-2. **Execute Context Compiler Engine** → Call `node scripts/context_compiler.js` to compute deterministic SHA-256 hashes, extract AST skeletons, and identify inbound callers.
-3. **Living Vault Registration** → Ensure generated dossiers are saved to `docs/context/` and cataloged in `docs/context/INDEX.md`.
-
----
-
-## When to Use /context
-
-| Scenario                          | Command Pattern               | Output Generated                                             |
-| :-------------------------------- | :---------------------------- | :----------------------------------------------------------- |
-| Single File Dragged into Chat     | `/context <file_path>`        | `docs/context/[name].context.md` (Flight Data HUD)           |
-| Multi-File Pair Dragged into Chat | `/context <fileA> <fileB>`    | `docs/context/[nameA]__[nameB].bridge.md` (Interface Bridge) |
-| Whole Project / Subsystem Folder  | `/context <dir_path>`         | `docs/context/[folder].context.md` (Subsystem Macro Map)     |
-| Audit Vault Freshness             | `/context --check`            | Terminal report flagging Fresh vs Stale context              |
-| Batch Vault Crawling              | `/context <dir_path> --crawl` | Crawls entire directory and populates context vault          |
-
----
-
-## Execution Protocol
-
-### Step 1: Parse Arguments & Detect Mode
-
-Examine `$ARGUMENTS`:
-
-- If `$ARGUMENTS` contains `--check`:
-  ```bash
-  node scripts/context_compiler.js --check
-  ```
-  Report the freshness status to the user.
-- If `$ARGUMENTS` contains two file paths (e.g. `path/to/A.ts path/to/B.ts`):
-  Execute multi-file bridge mode:
-  ```bash
-  node scripts/context_compiler.js --multi "<pathA>" "<pathB>" --write
-  ```
-- If `$ARGUMENTS` is a directory:
-  Execute directory subsystem mode:
-  ```bash
-  node scripts/context_compiler.js --dir "<dir_path>" --write
-  ```
-- If `$ARGUMENTS` is a single file:
-  Execute single-file mode:
-  ```bash
-  node scripts/context_compiler.js --file "<file_path>" --write
-  ```
-
----
-
-### Step 2: Synthesis & Flight Data HUD Formatting
-
-When presenting the result in the AI IDE chat, format the response using the **Flight Data HUD Dossier** structure:
-
-1. **Header HUD:** Target file, layer badge, language, and SHA-256 snapshot hash.
-2. **30-Second Mental Model:** Single-sentence mission statement and ASCII/Mermaid sequence.
-3. **Public API & Contract Table:** Exported functions, types, parameters, and error/panic conditions.
-4. **Blast Radius & Topology:** Inbound callers, line numbers, and callers vector.
-5. **⚠️ Chesterton's Fences & Landmines:** Critical gotchas, defensive guards, and `// VERIFY` invariants.
-6. **Isolated Verification Recipe:** Exact 1-line shell command to run tests for that file.
-7. **AI Quick-Inject Card:** Fenced snippet for immediate copy-pasting into future prompts.
-
----
-
-### Step 3: Vault Sync
-
-Confirm that:
-
-1. Dossier was written to `docs/context/[target].context.md`.
-2. Master registry `docs/context/INDEX.md` was updated.
-3. If `--link` flag was passed, verify or add top-line comment `// @context docs/context/...` to the target file.
-
----
-
-## Anti-Hallucination Guardrails
-
-```
-❌ Never invent callers that were not verified by ripgrep/compiler.
-❌ Never delete or omit // VERIFY comments from code or dossiers.
-❌ Never paraphrase obvious code without highlighting invariants and gotchas.
-❌ Always report exact file paths and line numbers.
-```
+---
+description: Generates an elite Flight Data HUD context dossier for any file, multi-file pair, or project folder. Maintains a living codebase context vault with drift detection.
+tools: Read, Grep, Glob, Bash, Write
+version: 3.0.0
+last-updated: 2026-09-13
+required-skills:
+  - plan-writing
+  - clean-code
+  - documentation-templates
+scripts-binding:
+  - scripts/context_compiler.js
+---
+
+# /context — Living Codebase & File Context Engine
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before generating context dossiers or inspecting workspace files, you MUST:
+
+1. **Input Normalization** → Strip any surrounding single or double quotes, resolve IDE drag-and-drop file paths, and handle Windows/POSIX path separators.
+2. **Execute Context Compiler Engine** → Call `node scripts/context_compiler.js` to compute deterministic SHA-256 hashes, extract AST skeletons, and identify inbound callers.
+3. **Living Vault Registration** → Ensure generated dossiers are saved to `docs/context/` and cataloged in `docs/context/INDEX.md`.
+
+---
+
+## When to Use /context
+
+| Scenario                          | Command Pattern               | Output Generated                                             |
+| :-------------------------------- | :---------------------------- | :----------------------------------------------------------- |
+| Single File Dragged into Chat     | `/context <file_path>`        | `docs/context/[name].context.md` (Flight Data HUD)           |
+| Multi-File Pair Dragged into Chat | `/context <fileA> <fileB>`    | `docs/context/[nameA]__[nameB].bridge.md` (Interface Bridge) |
+| Whole Project / Subsystem Folder  | `/context <dir_path>`         | `docs/context/[folder].context.md` (Subsystem Macro Map)     |
+| Audit Vault Freshness             | `/context --check`            | Terminal report flagging Fresh vs Stale context              |
+| Batch Vault Crawling              | `/context <dir_path> --crawl` | Crawls entire directory and populates context vault          |
+
+---
+
+## Execution Protocol
+
+### Step 1: Parse Arguments & Detect Mode
+
+Examine `$ARGUMENTS`:
+
+- If `$ARGUMENTS` contains `--check`:
+  ```bash
+  node scripts/context_compiler.js --check
+  ```
+  Report the freshness status to the user.
+- If `$ARGUMENTS` contains two file paths (e.g. `path/to/A.ts path/to/B.ts`):
+  Execute multi-file bridge mode:
+  ```bash
+  node scripts/context_compiler.js --multi "<pathA>" "<pathB>" --write
+  ```
+- If `$ARGUMENTS` is a directory:
+  Execute directory subsystem mode:
+  ```bash
+  node scripts/context_compiler.js --dir "<dir_path>" --write
+  ```
+- If `$ARGUMENTS` is a single file:
+  Execute single-file mode:
+  ```bash
+  node scripts/context_compiler.js --file "<file_path>" --write
+  ```
+
+---
+
+### Step 2: Synthesis & Flight Data HUD Formatting
+
+When presenting the result in the AI IDE chat, format the response using the **Flight Data HUD Dossier** structure:
+
+1. **Header HUD:** Target file, layer badge, language, and SHA-256 snapshot hash.
+2. **30-Second Mental Model:** Single-sentence mission statement and ASCII/Mermaid sequence.
+3. **Public API & Contract Table:** Exported functions, types, parameters, and error/panic conditions.
+4. **Blast Radius & Topology:** Inbound callers, line numbers, and callers vector.
+5. **⚠️ Chesterton's Fences & Landmines:** Critical gotchas, defensive guards, and `// VERIFY` invariants.
+6. **Isolated Verification Recipe:** Exact 1-line shell command to run tests for that file.
+7. **AI Quick-Inject Card:** Fenced snippet for immediate copy-pasting into future prompts.
+
+---
+
+### Step 3: Vault Sync
+
+Confirm that:
+
+1. Dossier was written to `docs/context/[target].context.md`.
+2. Master registry `docs/context/INDEX.md` was updated.
+3. If `--link` flag was passed, verify or add top-line comment `// @context docs/context/...` to the target file.
+
+---
+
+## Anti-Hallucination Guardrails
+
+```
+❌ Never invent callers that were not verified by ripgrep/compiler.
+❌ Never delete or omit // VERIFY comments from code or dossiers.
+❌ Never paraphrase obvious code without highlighting invariants and gotchas.
+❌ Always report exact file paths and line numbers.
+```