agent-enderun 1.1.9 → 1.10.0

package/dist/init-adapters/claude/.claude/agents/devops.md

@@ -1,17 +0,0 @@
----
-name: "devops"
-description: "CI/CD, Deployment, and Infrastructure specialist."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "infra"] -->
-
-
-# 🎖️ Enderun Core — @devops (Infrastructure Specialist)
-
-## 🤖 Talimatlar (Instructions)
-Maintain reliable supply lines and systems like fortresses.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/explorer.md

@@ -1,17 +0,0 @@
----
-name: "explorer"
-description: "Intelligence, Reconnaissance, and Context Discovery."
----
-
-<!-- capability: 8 -->
-<!-- tags: ["core", "recon"] -->
-
-
-# 🎖️ Enderun Core — @explorer (Intel Explorer)
-
-## 🤖 Talimatlar (Instructions)
-Gather tactical intelligence and map dependencies for the Manager.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/frontend.md

@@ -1,17 +0,0 @@
----
-name: "frontend"
-description: "UI/UX, Panda CSS, and State Management specialist."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "ui"] -->
-
-
-# 🎖️ Enderun Core — @frontend (Frontend Specialist)
-
-## 🤖 Talimatlar (Instructions)
-Build elegant and disciplined UIs with master craftsmanship.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/git.md

@@ -1,17 +0,0 @@
----
-name: "git"
-description: "Git flow, Branching, and Atomic Commit master."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "logistics"] -->
-
-
-# 🎖️ Enderun Core — @git (Logistics Master)
-
-## 🤖 Talimatlar (Instructions)
-Manage the scrolls of history. Every commit must be atomic and traceable.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/manager.md

@@ -1,17 +0,0 @@
----
-name: "manager"
-description: "The Supreme Manager and Strategic Orchestrator of the Enderun Army."
----
-
-<!-- capability: 10 -->
-<!-- tags: ["core", "orchestration"] -->
-
-
-# 🎖️ Enderun Core — @manager (Manager (Orchestrator))
-
-## 🤖 Talimatlar (Instructions)
-You represent the Enderun Discipline (Osmanlı Nizami). Your word is the law for the specialists. Delegate tasks with precision.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/mobile.md

@@ -1,17 +0,0 @@
----
-name: "mobile"
-description: "React Native and Expo development specialist."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "mobile"] -->
-
-
-# 🎖️ Enderun Core — @mobile (Mobile Specialist)
-
-## 🤖 Talimatlar (Instructions)
-Extend reach to the mobile realm with discipline.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/native.md

@@ -1,17 +0,0 @@
----
-name: "native"
-description: "Desktop apps and System-level logic specialist."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "native"] -->
-
-
-# 🎖️ Enderun Core — @native (Native Division)
-
-## 🤖 Talimatlar (Instructions)
-Handle deep layers of the OS with paramount security.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/quality.md

@@ -1,17 +0,0 @@
----
-name: "quality"
-description: "Audit, Testing, and Compliance specialist."
----
-
-<!-- capability: 9 -->
-<!-- tags: ["core", "audit"] -->
-
-
-# 🎖️ Enderun Core — @quality (Quality Specialist)
-
-## 🤖 Talimatlar (Instructions)
-You are the inspector of the Nizam. Ensure every unit's work is perfect.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/agents/security.md

@@ -1,17 +0,0 @@
----
-name: "security"
-description: "Auth, Encryption, and Safety enforcement specialist."
----
-
-<!-- capability: 10 -->
-<!-- tags: ["core", "security"] -->
-
-
-# 🎖️ Enderun Core — @security (Security Specialist)
-
-## 🤖 Talimatlar (Instructions)
-Guardian of the Nizam. block any action that endangers the project.
-
-## 🛡️ Çekirdek Kurallar (Core Mandates)
-- **Traceability:** Her eylem aktif Trace ID'yi miras almalıdır.
-- **Surgical Precision:** Sadece `replace_text` veya `patch_file` kullanarak dosya düzenleyin.

package/dist/init-adapters/claude/.claude/cli-commands.json

@@ -1,32 +0,0 @@
-{
-  "commands": {
-    "init": {
-      "agent": "manager",
-      "description": "Initialize Enderun Core structure and AI configuration."
-    },
-    "check": {
-      "agent": "quality",
-      "description": "Verify framework files and code quality discipline."
-    },
-    "status": {
-      "agent": "manager",
-      "description": "Show the current status of the active project phase."
-    },
-    "trace:new": {
-      "agent": "manager",
-      "description": "Generate a new Trace ID to start a task sequence."
-    },
-    "orchestrate": {
-      "agent": "manager",
-      "description": "Execute the Hermes message broker loop."
-    },
-    "verify-contract": {
-      "agent": "architect",
-      "description": "Validate type contracts between backend and frontend."
-    },
-    "update-contract": {
-      "agent": "architect",
-      "description": "Update the contract signature hash."
-    }
-  }
-}

package/dist/init-adapters/claude/.claude/config.json

@@ -1,12 +0,0 @@
-{
-  "name": "Enderun Core",
-  "version": "1.1.4",
-  "theme": {
-    "palette": "Modern Blue",
-    "colors": {
-      "primary": "#0ea5e9",
-      "secondary": "#64748b",
-      "accent": "#f43f5e"
-    }
-  }
-}

package/dist/init-adapters/claude/.claude/knowledge/agents-manifest.md

@@ -1,79 +0,0 @@
-# 🎖️ Agent Enderun — Agent Army Manifest
-
-This document serves as the complete manifest of the 13 specialist agents forming the **Enderun Army**. Each agent is mapped to a specific capability index, toolset, and specialized directive under the Enderun Discipline (Osmanlı Nizami).
-
----
-
-## 🏛️ Agent Army Overview
-
-| Agent Name | Role | Capability | Primary Tools | Tags |
-| :--- | :--- | :--- | :--- | :--- |
-| **`@manager`** | Orchestration | 10/10 | `orchestrate_loop`, `send_agent_message` | `core`, `orchestration` |
-| **`@architect`** | System Design | 9/10 | `write_file`, `replace_text` | `core`, `design` |
-| **`@backend`** | Backend Logic | 9/10 | `replace_text`, `run_shell_command` | `core`, `logic` |
-| **`@frontend`** | User Interface | 9/10 | `replace_text`, `view_file` | `core`, `ui` |
-| **`@quality`** | Quality Audit | 9/10 | `run_shell_command`, `view_file` | `core`, `audit` |
-| **`@database`** | Data Management | 9/10 | `replace_text`, `run_shell_command` | `core`, `data` |
-| **`@devops`** | Infrastructure | 9/10 | `run_shell_command`, `view_file` | `core`, `infra` |
-| **`@explorer`** | Reconnaissance | 8/10 | `grep_search`, `list_dir`, `glob` | `core`, `recon` |
-| **`@git`** | Version Control | 9/10 | `run_shell_command`, `view_file` | `core`, `logistics` |
-| **`@mobile`** | Mobile Apps | 9/10 | `replace_text`, `view_file` | `core`, `mobile` |
-| **`@native`** | System-Level | 9/10 | `run_shell_command`, `replace_text` | `core`, `native` |
-| **`@security`** | Security Audit | 10/10 | `grep_search`, `run_shell_command` | `core`, `security` |
-| **`@analyst`** | Requirements | 9/10 | `grep_search`, `list_dir` | `core`, `strategy` |
-
----
-
-## 🤖 Specialist Directives
-
-### 1. `@manager` (Orchestrator)
-- **Directive:** Strategic commander of the army. Coordinates executions, schedules traces, and delegates tasks to specialists.
-- **Mandate:** Enforces Enderun discipline, inherits and passes Trace IDs, and handles final compliance approvals.
-
-### 2. `@architect` (Lead Architect)
-- **Directive:** Outlines initial codebase design, defines schema contracts, and manages the architectural blueprint.
-- **Mandate:** Enforces strict modular boundaries and verifies structural sanity.
-
-### 3. `@backend` (Backend Specialist)
-- **Directive:** Builds REST/GraphQL API systems, develops server components, and manages server business rules.
-- **Mandate:** Ensures robust error handling, schema boundaries, and server logic.
-
-### 4. `@frontend` (Frontend Specialist)
-- **Directive:** Builds user interfaces, manages layouts and states using modern styling (Panda CSS, CSS variables).
-- **Mandate:** Enforces design systems, accessibility, and high performance rendering.
-
-### 5. `@quality` (Quality Specialist)
-- **Directive:** Validates unit coverage, performs static analyses, and ensures code rules compliance.
-- **Mandate:** Runs ESLint rules, checks console logs, and audits project safety.
-
-### 6. `@database` (Database Specialist)
-- **Directive:** Designs relational/NoSQL schemas, writes migrations, and optimizes SQL query metrics.
-- **Mandate:** Guarantees data transaction integrity and index configurations.
-
-### 7. `@devops` (Infrastructure Specialist)
-- **Directive:** Establishes CI/CD pipelines, configures Docker environments, and tracks cloud deployments.
-- **Mandate:** Ensures high availability, automation scripts, and safe release cycles.
-
-### 8. `@explorer` (Intel Explorer)
-- **Directive:** Gathers codebase intelligence, discovers file dependencies, and maps codebase symbols.
-- **Mandate:** Guides planning agents by providing context graphs and code dependencies.
-
-### 9. `@git` (Logistics Master)
-- **Directive:** Handles atomic commit flows, merges code, resolves conflicts, and manages release tags.
-- **Mandate:** Enforces descriptive commit tags mapped to active Trace IDs.
-
-### 10. `@mobile` (Mobile Specialist)
-- **Directive:** Implements mobile interfaces using cross-platform layouts (React Native / Expo).
-- **Mandate:** Optimizes mobile assets, native performance, and state stores.
-
-### 11. `@native` (Native Division)
-- **Directive:** Interfaces with native operating system hooks, constructs desktop platforms, and manages hardware bridges.
-- **Mandate:** Exercises deep security protocols during system interactions.
-
-### 12. `@security` (Security Specialist)
-- **Directive:** Audits repositories for credentials/secrets, evaluates package dependencies, and verifies authentication flows.
-- **Mandate:** Rejects insecure actions, validates cryptographic keys, and enforces access control checks.
-
-### 13. `@analyst` (Business Analyst)
-- **Directive:** Maps requirements to codebase implementations, writes business specification rules, and audits contracts.
-- **Mandate:** Validates feature alignment against system specifications.

package/dist/init-adapters/claude/.claude/knowledge/approval-flows.md

@@ -1,61 +0,0 @@
-# Enterprise Approval Flows & Governance Protocol (v0.8.5)
-
-This protocol defines the strict governance model for high-risk operations and cross-agent approval flows within the Agent Enderun framework. It ensures that no critical mutations or sensitive actions are executed by AI specialists without formal orchestration and explicit authorization.
-
----
-
-## 🔒 1. High-Risk Action Catalog
-
-Specialist agents (@backend, @frontend, @devops, etc.) are strictly prohibited from performing any of the following administrative operations autonomously. If requested, they must halt work, shift to `WAITING` status, and escalate to `@manager` via the **Hermes Protocol**.
-
-| Category | High-Risk Operations | Designated Controller |
-| :--- | :--- | :--- |
-| **Data Management** | Bulk delete/purge, data migration, PII export, schema modifications. | `@manager` |
-| **System Security** | Security credentials modification, CSP rule changes, private keys rotation. | `@security` & `@manager` |
-| **Infrastructure** | Production deployment triggers, container orchestration changes, ENV vars rotation. | `@devops` & `@manager` |
-| **Contract Stability**| Breaking API modifications, major type updates inside `src/types/`. | `@backend` & `@manager` |
-
----
-
-## 💬 2. Hermes approval Flow (`managerApproval`)
-
-When a specialist agent encounters a high-risk operation, it must execute the following message queue protocol.
-
-### Step 1: Lock the Hermes Inbox
-To prevent race conditions, the agent must check for `.claude/messages/.lock`. If the lock is active, the agent retries (up to 3 times, waiting 500ms between attempts). If no lock exists, it creates `.lock` to claim the channel.
-
-### Step 2: Write Approval Request File
-The requesting agent writes a structured JSON file inside `.claude/queue/pending/` or `.claude/messages/` with the unique `Trace ID` (ULID) and a `managerApproval` request flag:
-
-```json
-{
-  "traceId": "01JM5S8A0F2B4C6D8E0G2H4J6K",
-  "from": "@backend",
-  "to": "@manager",
-  "category": "ALERT",
-  "priority": "HIGH",
-  "action": "RUN_DATABASE_MIGRATION",
-  "payload": {
-    "migrationFile": "20260527_add_tenant_rls_policy.sql",
-    "rationale": "Enables multi-tenant Row Level Security (RLS) on PostgreSQL."
-  },
-  "timestamp": "2026-05-27T20:45:00Z"
-}
-```
-
-### Step 3: Shift Agent State
-The requesting agent updates its state inside `.claude/STATUS.md` to `WAITING` and appends `BLOCKED_BY_APPROVAL` to its action log.
-
-### Step 4: Human-in-the-Loop Signing
-In production workspaces, the `@manager` compiles the war-room report and requests the human architect (CTO) to sign off on the transaction. The human developer signs the transaction by executing:
-```bash
-npx agent-enderun approve 01JM5S8A0F2B4C6D8E0G2H4J6K
-```
-Or by writing a signed token to the message queue.
-
----
-
-## 🚦 3. Conflict Resolution & Rollback
-
-1.  **Approval Rejection:** If the transaction is rejected, `@manager` issues a `REJECTED` signal. The specialist agent rolls back any staged changes and returns to `IDLE` state.
-2.  **Stale Lock Recovery:** If a Hermes inbox `.lock` remains for more than 1.5 seconds, the active agent assumes a **stale lock** (LLM timeout), deletes the lock, and logs the incident to `@manager`.

package/dist/init-adapters/claude/.claude/knowledge/component-patterns.md

@@ -1,91 +0,0 @@
-# Atomic Component Standards & Panda CSS Guidelines (v0.8.5)
-
-All user interface developments inside the Agent Enderun framework must follow the **Fluid Component Protocol**. We strictly build component hierarchies following **Mobile-First Responsive Design** and type-safe styling using **Panda CSS**.
-
----
-
-## 🚫 1. Absolute UI Policies
-
-### A. Zero UI Library Policy
-*   **The Law:** The use of external component libraries (e.g. TailwindCSS, Radix UI, Shadcn/ui, Material UI, Chakra UI, Ant Design) is strictly forbidden. 
-*   **The Reason:** This ensures absolute design authenticity, maximum bundle optimization, zero dependency bloat, and fully controlled accessibility (WCAG 2.2 AA).
-*   **Exception:** Low-level headless primitives (like `@radix-ui/react-dialog` for focus trapping or `sonner` for toast dispatchers) may be allowed, subject to direct approval by `@manager`.
-
-### B. Shared Component First Policy
-*   **The Law:** Defining reusable atomic components (Buttons, Inputs, Cards, Badges, Modals) inside page-level files is strictly forbidden.
-*   **The Structure:** All atomic items must be created inside `apps/web/src/components/ui/` as focused, single-purpose, highly modular components.
-
----
-
-## 🐼 2. Panda CSS Styling Standards
-
-We utilize **Panda CSS** as our build-time type-safe CSS-in-JS engine. Raw inline styles or unmapped class names are completely banned.
-
-### A. Styling Token Best Practices
-Always leverage designated design tokens (colors, spacings, shadows) from the Panda config (`panda.config.ts`):
-
-```tsx
-import { css } from "../../styled-system/css";
-
-interface ButtonProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
-  variant?: "primary" | "secondary";
-}
-
-export function Button({ variant = "primary", className, children, ...props }: ButtonProps) {
-  return (
-    <button
-      className={css(
-        {
-          display: "inline-flex",
-          alignItems: "center",
-          justifyContent: "center",
-          px: "4",
-          py: "2.5",
-          borderRadius: "md",
-          fontSize: "sm",
-          fontWeight: "medium",
-          transition: "all 0.2s ease-in-out",
-          cursor: "pointer",
-          _disabled: { opacity: 0.5, cursor: "not-allowed" },
-        },
-        variant === "primary"
-          ? {
-              bg: "brand.primary",
-              color: "white",
-              _hover: { bg: "brand.primary.hover" },
-            }
-          : {
-              bg: "transparent",
-              color: "slate.700",
-              border: "1px solid",
-              borderColor: "slate.200",
-              _hover: { bg: "slate.50" },
-            }
-      )}
-      {...props}
-    >
-      {children}
-    </button>
-  );
-}
-```
-
-### B. Mobile-First Fluid Responsiveness
-Use array-based or object-based responsive syntax inside the `css` block. Never hardcode pixel values:
-
-```typescript
-// Enforce fluid flex layout across screen sizes
-const containerStyle = css({
-  display: "flex",
-  flexDirection: { base: "column", md: "row" }, // Mobile-first (column -> row on desktop)
-  gap: { base: "4", lg: "8" },
-  p: { base: "4", md: "6", xl: "8" }
-});
-```
-
----
-
-## ♿ 3. Accessibility & QA Gates (WCAG 2.2)
-
-1.  **Aria Standards:** All custom interactive elements (dropdowns, mobile navigation draw-ins, accordion blocks) must support full keyboard navigation (Tab, Enter, Space) and have valid `aria-*` tags.
-2.  **Vitest Verification:** A component must never be merged into master without an accompanying test file (`[component].test.tsx`) that verifies the component renders correctly and responds to user click actions.

package/dist/init-adapters/claude/.claude/knowledge/data-fetching-patterns.md

@@ -1,13 +0,0 @@
-# Architecture Patterns & Data Fetching
-
-## 1. UI Layout & Component Structure
-- **Shared UI:** All atomic components (Button, Input, etc.) must be created in `apps/web/src/components/ui/` using **Panda CSS**.
-- **Layouts:** Use wrapper layouts (`Shell`, `Workspace`) in `apps/web/src/components/layout/`. Every page must utilize these layouts to maintain consistency.
-- **Procedural Continuity:** Never re-create an existing component. Search the `components/ui/` directory first.
-
-## 2. Data Fetching & API (CRUD) Patterns
-- **Repository Pattern:** Backend logic must be separated into service/repository layers. No direct DB calls in controllers.
-- **Contract-First:** All API endpoints must use types imported from `apps/backend/src/types/`.
-- **API Layer:** Frontend must use typed fetcher functions located in `apps/web/src/api/`.
-- **Validation:** Use `zod` for request validation on the backend and response validation on the frontend.
-- **Audit Logging:** Every mutation (POST/PUT/PATCH/DELETE) MUST trigger an audit log service call with the current Trace ID.

package/dist/init-adapters/claude/.claude/knowledge/design-system.md

@@ -1,31 +0,0 @@
-# Design System — Agent Enderun (Enterprise)
-
-## 1. Design Philosophy
-The Agent Enderun Design System focuses on **"Enterprise Clarity"**. Our interfaces are professional, minimalist tools designed to maximize data comprehension and operational speed. 
-
-- **Clarity:** Every pixel must serve a purpose. If it doesn't aid understanding or action, remove it.
-- **Consistency:** Uniform visual language across all applications.
-- **Responsiveness:** Fluid adaptation to any screen size, from mobile to ultra-wide monitors.
-
-## 2. Technical Requirements
-- **Styling:** Panda CSS is MANDATORY. Tailwind, CSS-in-JS, and raw CSS modules are FORBIDDEN.
-- **Zero UI Library:** No external components (MUI, AntD, Shadcn). All UI components must be built from scratch in `apps/web/src/components/ui/`.
-- **Tokenization:** All values (colors, spacing, typography) MUST use `panda.config.ts` tokens. NO hardcoded pixels.
-- **Responsiveness:** Mobile-First design is MANDATORY.
-
-## 3. Responsive Mandate (Mobile-First)
-- **Design Strategy:** Design for 320px width first.
-- **Breakpoints:**
-  - `sm`: 640px
-  - `md`: 768px
-  - `lg`: 1024px
-  - `xl`: 1280px
-  - `2xl`: 1536px
-- **Layouts:** Use Flexbox and Grid. Fixed widths are FORBIDDEN. Use `clamp()` for fluid typography and spacing where applicable.
-- **Reflow:** Content MUST gracefully wrap, stack, or collapse based on screen width without horizontal scrollbars.
-
-## 4. UI/UX Interaction Standards
-- **Interactions:** Hover, Active, and Disabled states are MANDATORY for all interactive elements.
-- **Feedback:** Async operations MUST show Loading states and Toast notifications on completion/error.
-- **Blocking Dialogues:** Native `alert()` and `confirm()` functions are **FORBIDDEN**. Use project-integrated `Modal` components for blocking user interactions and `Toaster` for non-blocking feedback.
-- **Focus:** All interactive elements must have a visible `focus` state for accessibility.

package/dist/init-adapters/claude/.claude/knowledge/enterprise-architecture.md

@@ -1,69 +0,0 @@
-# 🎖️ Agent Enderun — Enterprise Architecture & Standards
-
-This document establishes the architecture patterns, design guidelines, and code structures of the **Enderun Core Framework** for enterprise deployments.
-
----
-
-## 🏛️ Project Directory Structure
-
-```text
-agent-enderun/
-├── bin/                       # Executable CLI entrypoints
-├── docs/                      # Technical documentation & design guides
-├── framework-mcp/             # Modular MCP server implementation (workspace)
-│   ├── src/                   # MCP server source files
-│   └── tests/                 # Unit tests for MCP server tools
-├── src/                       # CLI & Core framework logic
-│   ├── cli/                   # Command line interface commands & adapters
-│   │   ├── adapters/          # Target-specific IDE adapters (VS Code, Cursor, etc.)
-│   │   ├── commands/          # Subcommand handlers (init, status, check)
-│   │   └── utils/             # CLI-specific utilities
-│   ├── modules/               # Core framework modules
-│   │   ├── adapters/          # Target environment adapter profiles
-│   │   ├── agents/            # Orchestrator & Specialist Agent definitions
-│   │   └── skills/            # Capability templates for specialist actions
-│   └── shared/                # Core shared business components
-│       ├── config.ts          # Zod environment configuration
-│       ├── container.ts       # Dependency injection container
-│       ├── errors.ts          # Standard typed domain errors
-│       ├── fs.ts              # File system helper wrappers
-│       └── logger.ts          # Enterprise logging subsystem
-```
-
----
-
-## ⚙️ Core Design Principles
-
-### 1. Unified Domain Errors
-All errors thrown by modules must inherit from `EnderunBaseError` in [src/shared/errors.ts](file:///Users/ybekar/Desktop/Projeler/agent-enderun/src/shared/errors.ts).
-This ensures:
-- Unique error codes (`CONFIGURATION_ERROR`, `VALIDATION_ERROR`, etc.)
-- Metadata enrichment via the `details` field
-- Structured JSON serialization in production environments
-
-### 2. Zod-Validated Environments
-Configuration options must never be read directly from raw environment variables (`process.env`). Instead, they are parsed and frozen inside [src/shared/config.ts](file:///Users/ybekar/Desktop/Projeler/agent-enderun/src/shared/config.ts) at initialization. If a required value is missing, the application crashes immediately with a clean explanation.
-
-### 3. Service Container (Dependency Injection)
-To write testable and decoupled code, singletons and factories are registered and resolved using the `ServiceContainer` defined in [src/shared/container.ts](file:///Users/ybekar/Desktop/Projeler/agent-enderun/src/shared/container.ts).
-```typescript
-import { container } from "./shared/container.js";
-
-// Register
-container.register("Logger", logger);
-
-// Resolve
-const logger = container.resolve<EnterpriseLogger>("Logger");
-```
-
-### 4. Structured Observability
-Use `EnterpriseLogger` in [src/shared/logger.ts](file:///Users/ybekar/Desktop/Projeler/agent-enderun/src/shared/logger.ts) for logging:
-- In **development**, logs are colorized and formatted for human readability.
-- In **production**, logs are structured as JSON for log aggregators (e.g. Datadog, ELK).
-
----
-
-## 🛡️ Code & Type Guidelines
-- **Strict Typing:** Always keep `"strict": true` in `tsconfig.json`. Explicit return types are required on all exports.
-- **Asynchronous Flow:** Use async/await over raw promise chains. Handle failures with localized try/catch blocks and wrap in domain errors.
-- **Atomic Operations:** Always use transactional or surgical replacements when editing configuration/code files.

package/dist/init-adapters/claude/.claude/knowledge/error-handling.md

@@ -1,74 +0,0 @@
-# Professional Domain Error Handling Pattern (v0.8.5)
-
-All backend components developed under the Agent Enderun framework must comply with the **Domain Error Handling Protocol**. Direct usage of generic Javascript `Error` objects or HTTP status codes inside domain services is strictly forbidden.
-
----
-
-## 🏛️ 1. DomainError Base Hierarchy
-
-We implement a strongly-typed, business-aware exception hierarchy. Every error thrown by the domain logic must inherit from the `DomainError` class.
-
-```typescript
-export abstract class DomainError extends Error {
-  public abstract readonly statusCode: number;
-  public abstract readonly errorCode: string;
-  public readonly timestamp: string;
-
-  constructor(message: string, public readonly metadata: Record<string, unknown> = {}) {
-    super(message);
-    Object.setPrototypeOf(this, new.target.prototype);
-    this.name = this.constructor.name;
-    this.timestamp = new Date().toISOString();
-  }
-}
-```
-
-### Core Exception Catalog
-
-*   **`NotFoundError` (HTTP 404):** Thrown when a resource (e.g., `User`, `Project`) identified by a **Branded Type ID** does not exist.
-*   **`ValidationError` (HTTP 400):** Thrown when data validation (usually Zod schemas) fails before processing business logic.
-*   **`ConflictError` (HTTP 409):** Thrown when database unique constraints or concurrent updates conflict.
-*   **`UnauthorizedError` (HTTP 401 / 403):** Thrown when RLS (Row Level Security) or RBAC policies are violated.
-
----
-
-## ⚡ 2. Fastify Global Exception Handler
-
-Fastify must be configured with a single central error handler to map `DomainError` to client responses safely, preventing internal stack traces from leaking to the outside world.
-
-```typescript
-import { FastifyInstance, FastifyReply, FastifyRequest } from "fastify";
-
-export function registerGlobalErrorHandler(server: FastifyInstance) {
-  server.setErrorHandler((error: Error, request: FastifyRequest, reply: FastifyReply) => {
-    if (error instanceof DomainError) {
-      server.log.warn({ err: error }, `Domain error: ${error.message}`);
-      return reply.status(error.statusCode).send({
-        success: false,
-        error: error.errorCode,
-        message: error.message,
-        timestamp: error.timestamp,
-        metadata: error.metadata
-      });
-    }
-
-    // Capture unhandled internal technical crashes
-    server.log.error({ err: error }, `Unhandled server crash: ${error.message}`);
-    return reply.status(500).send({
-      success: false,
-      error: "INTERNAL_SERVER_ERROR",
-      message: "An unexpected error occurred inside the system."
-    });
-  });
-}
-```
-
----
-
-## 🔒 3. Branded Types & Query Constraints
-
-1.  **Branded Type Enforcement:** You must never accept raw string IDs inside repository query parameters. Always enforce compile-time type safety:
-    ```typescript
-    export type UserId = string & { readonly __brand: unique symbol };
-    ```
-2.  **Kysely Query Failures:** All Kysely queries running inside database transactions must be wrapped inside a `try/catch` block that translates SQL constraints into precise `ConflictError` or `UnauthorizedError` entities instead of throwing raw database query failures.

package/dist/init-adapters/claude/.claude/knowledge/eslint-standards.md

@@ -1,10 +0,0 @@
-# 🎖️ Agent Enderun — ESLint Standards
-
-This document outlines the strict ESLint coding standards for Agent Enderun projects.
-
-## 📏 Core Rules
-- **Indentation:** 4 spaces (strict).
-- **Quotes:** Double quotes (`"`) for strings.
-- **Semicolons:** Always terminate statements with a semicolon (`;`).
-- **No Explicit Any:** Avoid using `any`. Use strongly typed interfaces, generics, or `unknown` with type assertions.
-- **Unused Variables:** Warning on unused variables unless prefixed with an underscore (`_`).

package/dist/init-adapters/claude/.claude/knowledge/logging.md

@@ -1,7 +0,0 @@
-# Logging & Audit Standard
-
-- **No Console.log:** Production code MUST NOT use `console.log`, `console.warn`, or `console.error`. These are FORBIDDEN in the codebase.
-- **Structured Logging:** All logging MUST go through the centralized `Logger` service (`apps/backend/src/services/logger.ts`). Logs must be produced in JSON format.
-- **Traceability:** Every log entry MUST include the active `traceId` context to ensure cross-agent and cross-service traceability.
-- **Audit Logging:** Every state-mutating operation (POST, PUT, PATCH, DELETE) MUST trigger an `AuditService.log()` call, linking the action to the responsible agent, Trace ID, and entity ID.
-- **Log Persistence:** Logs must be persisted in an structured manner suitable for downstream ingestion by log management systems.