tribunal-kit 3.0.0 → 3.1.0

package/.agent/workflows/changelog.md

@@ -1,112 +1,112 @@
----
-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.
----
-
-# /changelog — Git History to Changelog
-
-$ARGUMENTS
-
----
-
-## 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
-```
+---
+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.
+---
+
+# /changelog — Git History to Changelog
+
+$ARGUMENTS
+
+---
+
+## 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
+```

package/.agent/workflows/create.md

@@ -1,124 +1,124 @@
----
-description: Create new application command. Triggers full stack creation from requirements gathering → stack selection → scaffolding → Tribunal code generation. Everything through the pipeline before writing a single file.
----
-
-# /create — Full Application Builder
-
-$ARGUMENTS
-
----
-
-## When to Use /create
-
-| Use `/create` when... | Use something else when... |
-|:---|:---|
-| Starting a new project from scratch | Adding to an existing project → `/enhance` |
-| No codebase exists yet | Generating a focused code snippet → `/generate` |
-| You need a working scaffold with structure | Planning and understanding → `/plan` |
-
----
-
-## Phase 1 — Requirements Gathering (Socratic Gate)
-
-Before a single line of code is written, the `app-builder` agent asks these questions:
-
-```
-1. What does this application DO? (one sentence — the core user action)
-2. Who uses it? (end users, internal team, API consumers)
-3. What is the target platform? (web, mobile, server, CLI, desktop)
-4. Are there any tech constraints? (must use X, must run on Y)
-5. What data does it store? (users, products, documents, real-time events)
-6. Is authentication required? (yes/no/type: email, OAuth, API key)
-7. Are there external integrations? (Stripe, OpenAI, Twilio, etc.)
-```
-
-No scaffolding starts until all questions are answered.
-
----
-
-## Phase 2 — Stack Selection
-
-Based on the answers, the agent selects the appropriate stack:
-
-| App Type | Recommended Stack |
-|:---|:---|
-| Web app (content + interaction) | Next.js 15, TypeScript, Tailwind v4, Prisma |
-| API server only | Hono on Node 22, Zod, TypeScript |
-| Real-time app | Next.js 15 + WebSocket (Socket.io) or SSE |
-| Mobile app | Expo + React Native, Expo Router v4 |
-| CLI tool | Node 22, Commander.js, TypeScript |
-| E-commerce | Next.js 15 + Stripe + Prisma |
-
-Stack selection is presented to the user for approval before scaffolding begins.
-
----
-
-## Phase 3 — Scaffolding Plan
-
-The agent produces an implementation plan showing:
-
-```
-Files to create:
-├── Core structure (package.json, tsconfig, config files)
-├── Database schema (prisma/schema.prisma)
-├── Authentication setup (auth.ts, middleware.ts)
-├── Core API routes or Server Actions
-├── Base UI components and layouts
-└── Initial tests and CI pipeline
-```
-
-> **Human Gate:** User approves the plan before any files are written.
-
----
-
-## Phase 4 — Tribunal Generation
-
-All generated code runs through the Tribunal pipeline:
-
-```
-Maker generates each module individually
-    → logic-reviewer + security-auditor on every module
-    → domain-specific reviewers activated by module type
-    → Human Gate before each major file group is written
-```
-
-No module is written without passing Tribunal review.
-
----
-
-## Phase 5 — Verification
-
-After scaffolding:
-
-```
-□ npm install completes without errors
-□ npx tsc --noEmit passes clean
-□ npm run dev starts successfully
-□ npm test runs and passes (for any generated tests)
-□ Linting passes (if configured)
-```
-
----
-
-## Hallucination Guard (Create-Specific)
-
-```
-❌ Never generate the entire application as one massive code block
-❌ Never import packages not added to package.json in this session
-❌ Never assume a framework's default file structure — check with --help or docs
-❌ Never hardcode environment variables in generated files
-❌ Never use deprecated Next.js 13/14 patterns (pages/, getServerSideProps)
-❌ Never use React 18 hooks deprecated in React 19
-```
-
----
-
-## Usage Examples
-
-```
-/create a REST API for a todo app with JWT auth and PostgreSQL
-/create a Next.js 15 e-commerce site with Stripe and Prisma
-/create a CLI tool for generating Tribunal-compliant code reviews
-/create an Expo app for tracking workout sessions with offline support
-/create a real-time chat app using Next.js and Server-Sent Events
-```
+---
+description: Create new application command. Triggers full stack creation from requirements gathering → stack selection → scaffolding → Tribunal code generation. Everything through the pipeline before writing a single file.
+---
+
+# /create — Full Application Builder
+
+$ARGUMENTS
+
+---
+
+## When to Use /create
+
+|Use `/create` when...|Use something else when...|
+|:---|:---|
+|Starting a new project from scratch|Adding to an existing project → `/enhance`|
+|No codebase exists yet|Generating a focused code snippet → `/generate`|
+|You need a working scaffold with structure|Planning and understanding → `/plan`|
+
+---
+
+## Phase 1 — Requirements Gathering (Socratic Gate)
+
+Before a single line of code is written, the `app-builder` agent asks these questions:
+
+```
+1. What does this application DO? (one sentence — the core user action)
+2. Who uses it? (end users, internal team, API consumers)
+3. What is the target platform? (web, mobile, server, CLI, desktop)
+4. Are there any tech constraints? (must use X, must run on Y)
+5. What data does it store? (users, products, documents, real-time events)
+6. Is authentication required? (yes/no/type: email, OAuth, API key)
+7. Are there external integrations? (Stripe, OpenAI, Twilio, etc.)
+```
+
+No scaffolding starts until all questions are answered.
+
+---
+
+## Phase 2 — Stack Selection
+
+Based on the answers, the agent selects the appropriate stack:
+
+|App Type|Recommended Stack|
+|:---|:---|
+|Web app (content + interaction)|Next.js 15, TypeScript, Tailwind v4, Prisma|
+|API server only|Hono on Node 22, Zod, TypeScript|
+|Real-time app|Next.js 15 + WebSocket (Socket.io) or SSE|
+|Mobile app|Expo + React Native, Expo Router v4|
+|CLI tool|Node 22, Commander.js, TypeScript|
+|E-commerce|Next.js 15 + Stripe + Prisma|
+
+Stack selection is presented to the user for approval before scaffolding begins.
+
+---
+
+## Phase 3 — Scaffolding Plan
+
+The agent produces an implementation plan showing:
+
+```
+Files to create:
+├── Core structure (package.json, tsconfig, config files)
+├── Database schema (prisma/schema.prisma)
+├── Authentication setup (auth.ts, middleware.ts)
+├── Core API routes or Server Actions
+├── Base UI components and layouts
+└── Initial tests and CI pipeline
+```
+
+**Human Gate:** User approves the plan before any files are written.
+
+---
+
+## Phase 4 — Tribunal Generation
+
+All generated code runs through the Tribunal pipeline:
+
+```
+Maker generates each module individually
+    → logic-reviewer + security-auditor on every module
+    → domain-specific reviewers activated by module type
+    → Human Gate before each major file group is written
+```
+
+No module is written without passing Tribunal review.
+
+---
+
+## Phase 5 — Verification
+
+After scaffolding:
+
+```
+□ npm install completes without errors
+□ npx tsc --noEmit passes clean
+□ npm run dev starts successfully
+□ npm test runs and passes (for any generated tests)
+□ Linting passes (if configured)
+```
+
+---
+
+## Hallucination Guard (Create-Specific)
+
+```
+❌ Never generate the entire application as one massive code block
+❌ Never import packages not added to package.json in this session
+❌ Never assume a framework's default file structure — check with --help or docs
+❌ Never hardcode environment variables in generated files
+❌ Never use deprecated Next.js 13/14 patterns (pages/, getServerSideProps)
+❌ Never use React 18 hooks deprecated in React 19
+```
+
+---
+
+## Usage Examples
+
+```
+/create a REST API for a todo app with JWT auth and PostgreSQL
+/create a Next.js 15 e-commerce site with Stripe and Prisma
+/create a CLI tool for generating Tribunal-compliant code reviews
+/create an Expo app for tracking workout sessions with offline support
+/create a real-time chat app using Next.js and Server-Sent Events
+```