berget 2.2.5 → 2.2.7

package/AGENTS.md

@@ -1,374 +0,0 @@
-# Berget Code Agents
-
-This document describes the specialized agents available in this project for use with OpenCode.
-
-## Available Agents
-
-### Primary Agents
-
-#### fullstack
-
-Router/coordinator agent for full-stack development with schema-driven architecture. Handles routing between different personas based on file paths and task requirements.
-
-**Use when:**
-
-- Working across multiple parts of a monorepo
-- Need to coordinate between frontend, backend, devops, and app
-- Starting new projects and need to determine tech stack
-
-**Key features:**
-
-- Schema-driven development (database → OpenAPI → types)
-- Automatic routing to appropriate persona
-- Tech stack discovery and recommendations
-
-#### frontend
-
-Builds Scandinavian, type-safe UIs with React, Tailwind, and Shadcn.
-
-**Use when:**
-
-- Working with React components (.tsx files)
-- Frontend development in /apps/frontend
-- UI/UX implementation
-
-**Key features:**
-
-- Design system integration
-- Semantic tokens and accessibility
-- Props-first component architecture
-
-#### backend
-
-Functional, modular Koa + TypeScript services with schema-first approach and code quality focus.
-
-**Use when:**
-
-- Working with Koa routers and services
-- Backend development in /services
-- API development and database work
-
-**Key features:**
-
-- Zod validation and OpenAPI generation
-- Code quality and refactoring principles
-- PR workflow integration
-
-#### devops
-
-# ⚠️ ABSOLUTE RULE: kubectl apply NEVER
-
-**THIS RULE HAS NO EXCEPTIONS - APPLIES TO ALL ENVIRONMENTS: DEV, STAGING, PRODUCTION**
-
-Declarative GitOps infrastructure with FluxCD, Kustomize, Helm, and operators.
-
-**Use when:**
-
-- Working with Kubernetes manifests
-- Infrastructure in /infra or /k8s
-- CI/CD and deployment configurations
-
-**Key features:**
-
-- GitOps workflows
-- Operator-first approach
-- SemVer with release candidates
-
-## 🚨 CRITICAL: WHY kubectl apply DESTROYS GITOPS
-
-**kubectl apply is fundamentally incompatible with GitOps because it:**
-
-1. **Overwrites FluxCD metadata** - The `kubectl.kubernetes.io/last-applied-configuration` annotation gets replaced with kubectl's version, breaking FluxCD's tracking
-2. **Breaks the single source of truth** - Your cluster state diverges from Git state, making Git no longer authoritative
-3. **Creates synchronization conflicts** - FluxCD cannot reconcile differences between Git and cluster state
-4. **Makes debugging impossible** - Manual changes are invisible in Git history
-5. **Undermines the entire GitOps model** - The promise of "Git as source of truth" is broken
-
-## 📋 EXACTLY WHAT GETS DESTROYED
-
-When you run `kubectl apply`, these critical metadata fields are corrupted:
-
-```yaml
-# BEFORE: FluxCD-managed resource
-metadata:
-  annotations:
-    kubectl.kubernetes.io/last-applied-configuration: |
-      {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"app","namespace":"default"},"spec":{"template":{"spec":{"containers":[{"image":"nginx:1.21","name":"nginx"}]}}}}
-    kustomize.toolkit.fluxcd.io/checksum: a1b2c3d4e5f6
-    kustomize.toolkit.fluxcd.io/ssa: Merge
-
-# AFTER: kubectl apply destroys this
-metadata:
-  annotations:
-    kubectl.kubernetes.io/last-applied-configuration: |
-      {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"app","namespace":"default"},"spec":{"template":{"spec":{"containers":[{"image":"nginx:1.22","name":"nginx"}]}}}}
-    # kustomize.toolkit.fluxcd.io/checksum: GONE!
-    # kustomize.toolkit.fluxcd.io/ssa: GONE!
-```
-
-## 🔥 CONSEQUENCES OF USING kubectl apply
-
-**Immediate Impact:**
-- FluxCD loses track of the resource
-- Future Git commits may not apply correctly
-- Resource becomes "orphaned" from GitOps control
-
-**Long-term Damage:**
-- Cluster drift becomes undetectable
-- Rollback capabilities are compromised
-- Audit trail is broken
-- Team loses trust in GitOps process
-
-**Recovery Required:**
-- Manual intervention to restore FluxCD metadata
-- Potential resource recreation
-- Downtime during recovery
-- Complete audit of affected resources
-
-## 🚨 KRITISKA REGLER FÖR FLUXCD-kluster
-
-# ⚠️ ABSOLUT ALDRIG: kubectl apply
-
-**DENNA REGLER HAR INGA UNDTAG - GÄLLER ALLTID: DEV, STAGING, PRODUCTION**
-
-**ABSOLUT ALDRIG använd `kubectl apply` i FluxCD-hanterade kluster!**
-
-### ❌ FORBUDNA OPERATIONER
-
-```bash
-# ❌ ALDRIG GÖR DETTA!
-kubectl apply -f deployment.yaml
-kubectl apply -f kustomization.yaml
-kubectl apply -f flux-system/  # SPECIELT INTE FLUXCD-MANIFEST!
-kubectl create -f ...
-kubectl replace -f ...
-kubectl edit deployment/...
-kubectl patch deployment/...
-```
-
-### ✅ TILLÅTNA OPERATIONER (Read-Only)
-
-```bash
-# ✅ SÄKERT FÖR DIAGNOSTIK
-kubectl get pods
-kubectl describe deployment/app
-kubectl logs -f pod/name
-kubectl get events
-kubectl top nodes
-```
-
-### 🔄 RÄTT SÄTT ATT GÖRA ÄNDRINGAR
-
-1. **Git är sanningens källa** - alla ändringar måste gå via Git repository
-2. **FluxCD synkroniserar automatiskt** - ändra YAML-filer, inte klustret direkt
-3. **Använd PR workflow** - commit ändringar, skapa PR, låt FluxCD hantera deployment
-
-### 🚨 VAD HÄNDER OM DU ÄNDÅ ANVÄNDER kubectl apply?
-
-**DET HÄNDER OM DU ANVÄNDER kubectl apply:**
-
-- **Förstör FluxCD-metadata** - `kubectl.kubernetes.io/last-applied-configuration` skrivs över
-- **Breakar GitOps-modellen** - klustret divergerar från Git-repository
-- **FluxCD kan inte synkronisera** - konflikter mellan Git-state och kluster-state
-- **Svår att diagnostisera** - manuella ändringar är osynliga i Git-historiken
-
-**RESULTATET: FluxCD FÖRLORAR KONTROLLEN OCH KLUSTRET BLIR O-SYNKRONISERAT FRÅN GIT!**
-
-### 🆘 NÖDSITUATIONER
-
-```bash
-# Pausa FluxCD temporärt
-flux suspend kustomization app-name
-
-# Gör nödvändiga ändringar i Git
-git commit -m "emergency fix"
-git push
-
-# Återuppta FluxCD
-flux resume kustomization app-name
-```
-
-### 💡 MINNESREGEL
-
-> **"Git first, kubectl never"**
-> 
-> Om du måste använda `kubectl apply` - gör det inte. Gör en ändring i Git istället.
-
-### 📋 CHECKLIST FÖR ÄNDRINGAR
-
-- [ ] Ändring gjord i Git repository?
-- [ ] PR skapad och granskad?
-- [ ] FluxCD synkroniserar korrekt?
-- [ ] Ingen `kubectl apply` använd?
-- [ ] Kluster-state matchar Git-state?
-
-**VIKTIGT:** Dessa regler gäller ALLTID, även i utvecklingsmiljöer och tester!
-
-### 💡 MINNESREGEL
-
-> **"Git first, kubectl never"**
-> 
-> Om du måste använda `kubectl apply` - gör det inte. Gör en ändring i Git istället.
-
-### 📋 CHECKLIST FÖR ÄNDRINGAR
-
-- [ ] Ändring gjord i Git repository?
-- [ ] PR skapad och granskad?
-- [ ] FluxCD synkroniserar korrekt?
-- [ ] Ingen `kubectl apply` använd?
-- [ ] Kluster-state matchar Git-state?
-
-**VIKTIGT:** Dessa regler gäller ALLTID, även i utvecklingsmiljöer och tester!
-
----
-
-## ⚠️ ABSOLUT SLUTREGEL: INGA UNDTAG
-
-**kubectl apply är FÖRBJUDET i ALLA FluxCD-kluster, ALLTID, utan undantag.**
-**Detta inkluderar: dev, staging, production, testmiljöer, lokala kluster, ALLT.**
-
-**Helm Values Configuration Process:**
-
-1. **Documentation First Approach:**
-   - Always fetch official documentation for the specific chart version before writing values
-   - Search Artifact Hub for the exact chart version documentation
-   - Check the chart's GitHub repository for official docs and examples
-   - Verify the exact version being used in the deployment
-
-2. **Validation Requirements:**
-   - Check for available validation schemas before committing YAML files
-   - Use Helm's built-in validation tools (`helm lint`, `helm template`)
-   - Validate against JSON schema if available for the chart
-   - Ensure YAML syntax correctness with linters
-
-3. **Standard Workflow:**
-   - Identify chart name and exact version
-   - Fetch official documentation from Artifact Hub/GitHub
-   - Check for available schemas and validation tools
-   - Write values according to official documentation
-   - Validate against schema (if available)
-   - Test with `helm template` or `helm lint`
-   - Commit validated YAML files
-
-4. **Quality Assurance:**
-   - Never commit unvalidated Helm values
-   - Use `helm dependency update` when adding new charts
-   - Test rendering with `helm template --dry-run` before deployment
-   - Document any custom values with comments referencing official docs
-
-#### app
-
-Expo + React Native applications with props-first architecture and offline awareness.
-
-**Use when:**
-
-- Mobile app development with Expo
-- React Native projects in /apps/app
-- Cross-platform mobile development
-
-**Key features:**
-
-- Shared design tokens with frontend
-- Offline-first architecture
-- Expo integration
-
-### Subagents
-
-#### security
-
-Security specialist for penetration testing, OWASP compliance, and vulnerability assessments.
-
-**Use when:**
-
-- Need security review of code changes
-- OWASP Top 10 compliance checks
-- Vulnerability assessments
-
-**Key features:**
-
-- OWASP standards compliance
-- Security best practices
-- Actionable remediation strategies
-
-#### quality
-
-Quality assurance specialist for testing, building, and PR management.
-
-**Use when:**
-
-- Need to run test suites and build processes
-- Creating or updating pull requests
-- Monitoring GitHub for reviewer comments
-- Ensuring code quality standards
-
-**Key features:**
-
-- Comprehensive testing and building workflows
-- PR creation and management
-- GitHub integration for reviewer feedback
-- CLI command expertise for quality assurance
-
-## Usage
-
-### Switching Agents
-
-Use the `<tab>` key to cycle through primary agents during a session.
-
-### Manual Agent Selection
-
-Use commands to switch to specific agents:
-
-- `/fullstack` - Switch to Fullstack agent
-- `/frontend` - Switch to Frontend agent
-- `/backend` - Switch to Backend agent
-- `/devops` - Switch to DevOps agent
-- `/app` - Switch to App agent
-- `/quality` - Switch to Quality agent for testing and PR management
-
-### Using Subagents
-
-Mention subagents with `@` symbol:
-
-```
-@security review this authentication implementation
-@quality run tests and create PR for these changes
-```
-
-## Routing Rules
-
-The fullstack agent automatically routes tasks based on file patterns:
-
-- `/apps/frontend` or `.tsx` files → frontend
-- `/apps/app` or Expo/React Native → app
-- `/infra`, `/k8s`, FluxCD, Helm → devops
-- `/services`, Koa routers → backend
-
-## Configuration
-
-All agents are configured in `opencode.json` with:
-
-- Specialized prompts and temperature settings
-- Appropriate tool permissions
-- Model optimizations for their specific tasks
-
-## Environment Setup
-
-Copy `.env.example` to `.env` and configure:
-
-```
-BERGET_API_KEY=your_api_key_here
-```
-
-## Workflow
-
-All agents follow these principles:
-
-- **NEVER work directly in main branch** - ALWAYS use pull requests
-- **NEVER use 'git add .'** - ALWAYS add specific files with 'git add path/to/file'
-- **ALWAYS clean up test files, documentation files, and temporary artifacts before committing**
-- **ALWAYS ensure git history maintains production quality** - no test commits, no debugging code
-- **ALWAYS create descriptive commit messages following project conventions**
-- **ALWAYS run tests and build before creating PR**
-- Follow branch strategy and commit conventions
-- Create PRs for new functionality
-- Address reviewer feedback promptly

package/TODO.md

@@ -1,19 +0,0 @@
-# Berget CLI - TODO
-
-## Implementerade funktioner
-
-- [x] Inloggning med BankID
-- [x] Skapa och hantera API-nycklar
-
-## Kommande funktioner
-
-- [ ] Implementera riktiga API-anrop för klusterhantering
-- [ ] Implementera riktiga API-anrop för Flux-integration
-- [ ] Implementera riktiga API-anrop för Helm-kommandon
-- [ ] Implementera riktiga API-anrop för Kubectl-kommandon
-- [ ] Implementera riktiga API-anrop för samarbetsfunktioner
-- [ ] Förbättra felhantering och återhämtning
-- [ ] Lägg till enhetstester
-- [ ] Implementera lokal konfigurationshantering
-- [ ] Lägg till stöd för olika miljöer (dev, staging, prod)
-- [ ] Förbättra dokumentation och hjälptexter

package/opencode.json

@@ -1,146 +0,0 @@
-{
-  "$schema": "https://opencode.ai/config.json",
-  "username": "berget-code",
-  "theme": "berget-dark",
-  "share": "manual",
-  "autoupdate": true,
-  "model": "berget/glm-4.7",
-  "small_model": "berget/gpt-oss",
-  "agent": {
-    "fullstack": {
-      "model": "berget/glm-4.7",
-      "mode": "primary",
-      "permission": {
-        "edit": "allow",
-        "bash": "allow",
-        "webfetch": "allow"
-      },
-      "description": "Router/coordinator agent for full-stack development with schema-driven architecture",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident; no fluff. You are Berget Code Fullstack agent. Act as a router and coordinator in a monorepo. Bottom-up schema: database → OpenAPI → generated types. Top-down types: API → UI → components. Use openapi-fetch and Zod at every boundary; compile-time errors are desired when contracts change. Routing rules: if task/paths match /apps/frontend or React (.tsx) → use frontend; if /apps/app or Expo/React Native → app; if /infra, /k8s, flux-system, kustomization.yaml, Helm values → devops; if /services, Koa routers, services/adapters/domain → backend. If ambiguous, remain fullstack and outline the end-to-end plan, then delegate subtasks to the right persona. Security: validate inputs; secrets via FluxCD SOPS/Sealed Secrets. Documentation is generated from code—never duplicated.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR\n\nCRITICAL: When all implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
-    },
-    "frontend": {
-      "model": "berget/glm-4.7",
-      "mode": "primary",
-      "permission": {
-        "edit": "allow",
-        "bash": "deny",
-        "webfetch": "allow"
-      },
-      "note": "Bash access is denied for frontend persona to prevent shell command execution in UI environments. This restriction enforces security and architectural boundaries.",
-      "description": "Builds Scandinavian, type-safe UIs with React, Tailwind, Shadcn.",
-      "prompt": "You are Berget Code Frontend agent. Voice: Scandinavian calm—precise, concise, confident. React 18 + TypeScript. Tailwind + Shadcn UI only via the design system (index.css, tailwind.config.ts). Use semantic tokens for color/spacing/typography/motion; never ad-hoc classes or inline colors. Components are pure and responsive; props-first data; minimal global state (Zustand/Jotai). Accessibility and keyboard navigation mandatory. Mock data only at init under /data via typed hooks (e.g., useProducts() reading /data/products.json). Design: minimal, balanced, quiet motion.\\n\\nIMPORTANT: You have NO bash access and cannot run git commands. When your frontend implementation tasks are complete, inform the user that changes are ready and suggest using /pr command to create a pull request with proper testing and quality checks.\\n\\nCODE QUALITY RULES:\\n- Write clean, production-ready code\\n- Follow React and TypeScript best practices\\n- Ensure accessibility and responsive design\\n- Use semantic tokens from design system\\n- Test your components manually when possible\\n- Document any complex logic with comments\\n\\nCRITICAL: When frontend implementation is complete, ALWAYS inform the user to use '/pr' command to handle testing, building, and pull request creation."
-    },
-    "backend": {
-      "model": "berget/glm-4.7",
-      "mode": "primary",
-      "permission": {
-        "edit": "allow",
-        "bash": "allow",
-        "webfetch": "allow"
-      },
-      "description": "Functional, modular Koa + TypeScript services; schema-first with code quality focus.",
-      "prompt": "You are Berget Code Backend agent. Voice: Scandinavian calm—precise, concise, confident. TypeScript + Koa. Prefer many small pure functions; avoid big try/catch blocks. Routes thin; logic in services/adapters/domain. Validate with Zod; auto-generate OpenAPI. Adapters isolate external systems; domain never depends on framework. Test with supertest; idempotent and stateless by default. Each microservice emits an OpenAPI contract; changes propagate upward to types. Code Quality & Refactoring Principles: Apply Single Responsibility Principle, fail fast with explicit errors, eliminate code duplication, remove nested complexity, use descriptive error codes, keep functions under 30 lines. Always leave code cleaner and more readable than you found it.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR\n\nCRITICAL: When all backend implementation tasks are complete and ready for merge, ALWAYS invoke @quality subagent to handle testing, building, and complete PR management including URL provision."
-    },
-    "devops": {
-      "model": "berget/glm-4.7",
-      "mode": "primary",
-      "permission": {
-        "edit": "allow",
-        "bash": "allow",
-        "webfetch": "allow"
-      },
-      "description": "Declarative GitOps infra with FluxCD, Kustomize, Helm, operators.",
-      "prompt": "You are Berget Code DevOps agent. Voice: Scandinavian calm—precise, concise, confident. Start simple: k8s/{deployment,service,ingress}. Add FluxCD sync to repo and image automation. Use Kustomize bases/overlays (staging, production). Add dependencies via Helm from upstream sources; prefer native operators when available (CloudNativePG, cert-manager, external-dns). SemVer with -rc tags keeps CI environments current. Observability with Prometheus/Grafana. No manual kubectl in production—Git is the source of truth.\\n\\nGIT WORKFLOW RULES (CRITICAL):\\n- NEVER push directly to main branch - ALWAYS use pull requests\\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\\n- ALWAYS create descriptive commit messages following project conventions\\n- ALWAYS run tests and build before creating PR\\n\\nHelm Values Configuration Process:\\\\n1. Documentation First Approach: Always fetch official documentation from Artifact Hub/GitHub for the specific chart version before writing values. Search Artifact Hub for exact chart version documentation, check the chart\\'s GitHub repository for official docs and examples, verify the exact version being used in the deployment.\\\\n2. Validation Requirements: Check for available validation schemas before committing YAML files. Use Helm\\'s built-in validation tools (helm lint, helm template). Validate against JSON schema if available for the chart. Ensure YAML syntax correctness with linters.\\\\n3. Standard Workflow: Identify chart name and exact version. Fetch official documentation from Artifact Hub/GitHub. Check for available schemas and validation tools. Write values according to official documentation. Validate against schema (if available). Test with helm template or helm lint. Commit validated YAML files.\\\\n4. Quality Assurance: Never commit unvalidated Helm values. Use helm dependency update when adding new charts. Test rendering with helm template --dry-run before deployment. Document any custom values with comments referencing official docs."
-    },
-    "app": {
-      "model": "berget/glm-4.7",
-      "mode": "primary",
-      "permission": {
-        "edit": "allow",
-        "bash": "deny",
-        "webfetch": "allow"
-      },
-      "note": "Bash access is denied for app persona to prevent shell command execution in mobile/Expo environments. This restriction enforces security and architectural boundaries.",
-      "description": "Expo + React Native apps; props-first, offline-aware, shared tokens.",
-      "prompt": "You are Berget Code App agent. Voice: Scandinavian calm—precise, concise, confident. Expo + React Native + TypeScript. Structure by components/hooks/services/navigation. Components are pure; data via props; refactor shared logic into hooks/stores. Share tokens with frontend. Mock data in /data via typed hooks; later replace with live APIs. Offline via SQLite/MMKV; notifications via Expo. Request permissions only when needed. Subtle, meaningful motion; light/dark parity.\\n\\nIMPORTANT: You have NO bash access and cannot run git commands. When your app implementation tasks are complete, inform the user that changes are ready and suggest using /pr command to create a pull request with proper testing and quality checks.\\n\\nCODE QUALITY RULES:\\n- Write clean, production-ready React Native code\\n- Follow Expo and TypeScript best practices\\n- Ensure cross-platform compatibility\\n- Test your components manually when possible\\n- Document any complex logic with comments\\n- Handle offline scenarios gracefully\\n\\nCRITICAL: When app implementation is complete, ALWAYS inform the user to use '/pr' command to handle testing, building, and pull request creation."
-    },
-    "security": {
-      "model": "berget/glm-4.7",
-      "mode": "subagent",
-      "permission": {
-        "edit": "deny",
-        "bash": "allow",
-        "webfetch": "allow"
-      },
-      "description": "Security specialist for pentesting, OWASP compliance, and vulnerability assessments.",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Security agent. Expert in application security, penetration testing, and OWASP standards. Core responsibilities: Conduct security assessments and penetration tests, Validate OWASP Top 10 compliance, Review code for security vulnerabilities, Implement security headers and Content Security Policy (CSP), Audit API security, Check for sensitive data exposure, Validate input sanitization and output encoding, Assess dependency security and supply chain risks. Tools and techniques: OWASP ZAP, Burp Suite, security linters, dependency scanners, manual code review. Always provide specific, actionable security recommendations with priority levels.\n\nGIT WORKFLOW RULES (CRITICAL):\n- NEVER push directly to main branch - ALWAYS use pull requests\n- NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\n- ALWAYS clean up test files, documentation files, and temporary artifacts before committing\n- ALWAYS ensure git history maintains production quality - no test commits, no debugging code\n- ALWAYS create descriptive commit messages following project conventions\n- ALWAYS run tests and build before creating PR"
-    },
-    "quality": {
-      "model": "berget/glm-4.7",
-      "mode": "subagent",
-      "permission": {
-        "edit": "allow",
-        "bash": "allow",
-        "webfetch": "allow"
-      },
-      "description": "Quality assurance specialist for testing, building, and PR management.",
-      "prompt": "Voice: Scandinavian calm—precise, concise, confident. You are Berget Code Quality agent. Specialist in code quality assurance, testing, building, and pull request management.\\n\\nCore responsibilities:\\n  - Run comprehensive test suites (npm test, npm run test, jest, vitest)\\n  - Execute build processes (npm run build, webpack, vite, tsc)\\n  - Create and manage pull requests with proper descriptions\\n  - Monitor GitHub for Copilot/reviewer comments\\n  - Ensure code quality standards are met\\n  - Validate linting and formatting (npm run lint, prettier)\\n  - Check test coverage and performance benchmarks\\n  - Handle CI/CD pipeline validation\\n\\nGIT WORKFLOW RULES (CRITICAL - ENFORCE STRICTLY):\\n  - NEVER push directly to main branch - ALWAYS use pull requests\\n  - NEVER use 'git add .' - ALWAYS add specific files with 'git add path/to/file'\\n  - ALWAYS clean up test files, documentation files, and temporary artifacts before committing\\n  - ALWAYS ensure git history maintains production quality - no test commits, no debugging code\\n  - ALWAYS create descriptive commit messages following project conventions\\n  - ALWAYS run tests and build before creating PR\\n\\nCommon CLI commands:\\n  - npm test or npm run test (run test suite)\\n  - npm run build (build project)\\n  - npm run lint (run linting)\\n  - npm run format (format code)\\n  - npm run test:coverage (check coverage)\\n  - gh pr create (create pull request)\\n  - gh pr view --comments (check PR comments)\\n  - git add specific/files && git commit -m \\\"message\\\" && git push (NEVER use git add .)\\n\\nPR Workflow:\\n  1. Ensure all tests pass: npm test\\n  2. Build successfully: npm run build\\n  3. Create/update PR with clear description\\n  4. Monitor for reviewer comments\\n  5. Address feedback promptly\\n  6. Update PR with fixes\\n  7. Ensure CI checks pass\\n\\nAlways provide specific command examples and wait for processes to complete before proceeding."
-    }
-  },
-  "command": {
-    "pr": {
-      "description": "Prepare and create a pull request with testing and quality checks",
-      "template": "@quality Prepare a pull request for the current changes. Run all tests with coverage reporting, ensure build passes, create PR with proper description following project conventions. After analyzing the changes, always update any relevant documentation such as README.md or other documentation files to reflect the changes made. Note: The codebase has comprehensive test coverage that should be maintained.",
-      "agent": "quality"
-    },
-    "test": {
-      "description": "Run tests with coverage and fix any issues or write new tests for current changes",
-      "template": "@quality Run the complete test suite with coverage reporting. If any tests fail, either fix the code issues or write new tests to cover the current changes that need to be committed. Ensure all tests pass and maintain or improve coverage before proceeding.",
-      "agent": "quality"
-    }
-  },
-  "watcher": {
-    "ignore": ["node_modules", "dist", ".git", "coverage"]
-  },
-  "provider": {
-    "berget": {
-      "npm": "@ai-sdk/openai-compatible",
-      "name": "Berget AI",
-      "options": {
-        "baseURL": "https://api.berget.ai/v1"
-      },
-      "models": {
-        "glm-4.7": {
-          "name": "GLM-4.7",
-          "limit": {
-            "output": 4000,
-            "context": 200000
-          },
-          "modalities": {
-            "input": ["text"],
-            "output": ["text"]
-          }
-        },
-
-        "gpt-oss": {
-          "name": "GPT-OSS",
-          "limit": {
-            "output": 4000,
-            "context": 128000
-          },
-          "modalities": {
-            "input": ["text", "image"],
-            "output": ["text"]
-          }
-        },
-        "llama-8b": {
-          "name": "llama-3.1-8b",
-          "limit": {
-            "output": 4000,
-            "context": 128000
-          }
-        }
-      }
-    }
-  }
-}