atabey 0.0.5 → 0.0.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "atabey",
-  "version": "0.0.5",
+  "version": "0.0.7",
   "description": "The Supreme AI Governance & Autonomous Orchestration Framework for Enterprise Development. Supports Polyglot Backends (Go, Java, Python, .NET, Node.js) and Multi-Language Communication (TR/EN).",
   "author": "Yusuf BEKAR",
   "license": "MIT",
@@ -34,9 +34,7 @@
   "files": [
     "bin",
     "dist",
-    "src",
     "templates",
-    "framework-mcp",
     "README.md",
     "LICENSE",
     "mcp.json",
@@ -46,7 +44,8 @@
     "node": ">=18.0.0"
   },
   "scripts": {
-    "build": "tsc && npm run build --prefix framework-mcp",
+    "build": "tsc && npm run build --prefix framework-mcp && npm run build:ui",
+    "build:ui": "npm run build --prefix src/dashboard",
     "atabey:build": "npm run build --prefix framework-mcp",
     "atabey:test": "vitest run",
     "atabey:test:watch": "vitest",
@@ -65,6 +64,7 @@
     "access": "public"
   },
   "dependencies": {
+    "better-sqlite3": "^12.10.1",
     "chalk": "^5.6.2",
     "js-yaml": "^4.2.0",
     "typescript": "^5.9.3",
@@ -74,6 +74,7 @@
     "@eslint/js": "^10.0.1",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "@pandacss/dev": "^1.11.1",
+    "@types/better-sqlite3": "^7.6.13",
     "@types/node": "^25.9.1",
     "eslint": "^10.4.0",
     "globals": "^17.6.0",

package/templates/prompts/contract-design-recipe.md

@@ -16,6 +16,6 @@ This recipe governs the @architect agent's protocol for creating type-safe agree
 2.  **Commitment:** Run `atabey update-contract` to generate new SHA-256 signatures for the updated types.
 3.  **Audit:** Verify that `contract.version.json` accurately reflects the new architecture.
 
-## 📡 Phase 4: Synchronization
+## [SIGNAL] Phase 4: Synchronization
 1.  **Distribution:** Ensure the updated `src/types` directory is correctly linked or copied to both Frontend and Backend projects.
 2.  **Verification:** Trigger @backend and @frontend agents to read the new contract and plan their implementations.

package/templates/prompts/db-management-recipe.md

@@ -1,4 +1,4 @@
-# 🗄️ Engineering Recipe: Database Management & Migrations
+# [DB] Engineering Recipe: Database Management & Migrations
 
 This recipe governs the @database agent's protocol for schema creation, table modifications, and data integrity.
 
@@ -6,7 +6,7 @@ This recipe governs the @database agent's protocol for schema creation, table mo
 1.  **Type Mapping:** Define the new table or column in `src/types/models.ts` using Branded Types for IDs.
 2.  **Validation:** Ensure the interface extends `BaseEntity` (id, createdAt, updatedAt).
 
-## 🚀 Phase 2: Migration Generation
+## [START] Phase 2: Migration Generation
 1.  **Scripting:** Write a reversible migration (up/down) using the project's migration tool (e.g., Kysely or SQL).
 2.  **Atomic Changes:** One migration per logical feature. Never bundle unrelated schema changes.
 3.  **Naming:** Use timestamp-prefixed naming (e.g., `20240101_add_customers_table.ts`).
@@ -19,7 +19,7 @@ This recipe governs the @database agent's protocol for schema creation, table mo
 1.  **Repo Layer:** Create or update the Repository class to include the new query logic.
 2.  **Strict Mode:** Ensure no raw SQL is used; leverage the query builder exclusively.
 
-## ✅ Phase 5: Verification & Zero-Downtime Audit
+## [OK] Phase 5: Verification & Zero-Downtime Audit
 1.  **Dry Run:** If supported, dry-run the migration to check for locking issues.
 2.  **Validation:** Run `atabey verify-contract` to ensure code and schema are synced.
 3.  **Handoff:** Update `PROJECT_MEMORY.md` with the new schema version.

package/templates/prompts/deployment-recipe.md

@@ -1,4 +1,4 @@
-# 🚀 Engineering Recipe: Infrastructure Deployment
+# [START] Engineering Recipe: Infrastructure Deployment
 
 This recipe governs the @devops agent's protocol for safe, traceable, and reversible system rollouts.
 
@@ -12,12 +12,12 @@ This recipe governs the @devops agent's protocol for safe, traceable, and revers
 2.  **Contract Verify:** Run `atabey verify-contract` to ensure FE/BE synchronization.
 3.  **Test Suite:** Execute the full test battery. Failure in a single test blocks deployment.
 
-## 📡 Phase 3: Controlled Rollout
+## [SIGNAL] Phase 3: Controlled Rollout
 1.  **Atomic Swap:** Deploy the new bundle/service using the project's orchestration scripts.
 2.  **Database Sync:** If migrations are pending, follow the `db-management-recipe.md` first.
 3.  **Log Monitoring:** Tail `logs/manager.json` for immediate post-deploy spikes in errors.
 
-## ✅ Phase 4: Post-Deploy & Rollback Readiness
+## [OK] Phase 4: Post-Deploy & Rollback Readiness
 1.  **Observability:** Verify system metrics stabilize within 5 minutes.
 2.  **Traceability:** Record the deployment Trace ID and commit hash in `PROJECT_MEMORY.md`.
 3.  **Rollback Check:** Ensure the previous stable version is tagged and reachable in Git.

package/templates/prompts/performance-optimization-recipe.md

@@ -2,12 +2,12 @@
 
 This recipe governs the protocol for identifying and resolving system bottlenecks (Frontend, Backend, or Database).
 
-## 📊 Phase 1: Profiling & Bottleneck Identification
+## [DATA] Phase 1: Profiling & Bottleneck Identification
 1.  **Metric Collection:** Read `observability/metrics.json` or run `get_system_health`.
 2.  **Log Audit:** Scan `logs/manager.json` for slow actions or timeouts.
 3.  **Trace Analysis:** Use `TraceID` to follow a slow request through all layers.
 
-## 🧠 Phase 2: Root Cause Analysis
+## [MEMORY] Phase 2: Root Cause Analysis
 1.  **SQL Audit:** Check for N+1 query patterns or missing indexes in `repository/` files.
 2.  **Algorithm Audit:** Scan for O(n²) loops or heavy synchronous operations.
 3.  **Frontend Audit:** Check for unnecessary re-renders or massive bundle sizes.
@@ -17,7 +17,7 @@ This recipe governs the protocol for identifying and resolving system bottleneck
 2.  **Logic Level:** Implement caching (e.g., Redis or in-memory) for frequent read operations.
 3.  **UI Level:** Apply memoization, virtualization (FlashList), or code-splitting.
 
-## ✅ Phase 4: Validation & Comparison
+## [OK] Phase 4: Validation & Comparison
 1.  **Benchmarking:** Re-run the action and compare new metrics with the baseline.
 2.  **Regression Check:** Run `atabey check` and existing tests to ensure logic is intact.
 3.  **Knowledge Update:** Record the optimization strategy in `knowledge/performance-history.md`.

package/templates/prompts/pull-request-template.md

@@ -7,14 +7,14 @@
 - **Trace ID:** [Link to Trace/Task or ID]
 - **Issue:** [Link to issue if applicable]
 
-## 🛡️ Governance & Compliance Checklist
+## [SECURITY] Governance & Compliance Checklist
 - [ ] Code passes `npm run atabey:test`.
 - [ ] Code passes `npm run atabey:check` (Compliance Scanner).
 - [ ] No `any` type usage added.
 - [ ] No secrets or hardcoded API keys.
 - [ ] New functionality is registered in `src/modules/agents/definitions.ts` (if applicable).
 
-## 🧪 Testing Notes
+## [SKILL] Testing Notes
 <!-- How did you verify the fix? -->
 
 ## 🛠️ Risk Assessment

package/templates/prompts/security-audit-recipe.md

@@ -1,4 +1,4 @@
-# 🛡️ Engineering Recipe: Advanced Security Audit
+# [SECURITY] Engineering Recipe: Advanced Security Audit
 
 This recipe governs the @security agent's protocol for identifying and mitigating vulnerabilities within the Agent Atabey framework.
 
@@ -7,7 +7,7 @@ This recipe governs the @security agent's protocol for identifying and mitigatin
 2.  **SQL Injection Audit:** Scan for `raw SQL` or template literals bypassing the query builder.
 3.  **Auth Check:** Verify that all sensitive routes have active `auth` guards and Role-Based Access Control (RBAC).
 
-## 🧠 Phase 2: Contextual Analysis
+## [MEMORY] Phase 2: Contextual Analysis
 1.  **Impact Mapping:** For every identified risk, read the surrounding code to determine if it's exposed to the public internet.
 2.  **Configuration Check:** Verify `.env.example` contains all required keys and no real secrets are committed to Git.
 
@@ -15,6 +15,6 @@ This recipe governs the @security agent's protocol for identifying and mitigatin
 1.  **Fix:** Use `replace_text` to move hardcoded secrets to `.env` or refactor raw SQL to Kysely.
 2.  **Sanitization:** Apply input validation using Zod schemas for all external data.
 
-## ✅ Phase 4: Verification & Logging
+## [OK] Phase 4: Verification & Logging
 1.  **Discipline Check:** Run `atabey check` to ensure no new violations were introduced.
 2.  **Action Log:** Execute `log_agent_action` with a summary of found vs. fixed vulnerabilities.

package/templates/standards/crud-governance.md

@@ -1,4 +1,4 @@
-# 🏛️ Corporate CRUD and Governance Standards
+# [GOV] Corporate CRUD and Governance Standards
 
 This document defines the strict rules applicable to data mutation and administrative operations in projects managed by the Agent Atabey army.
 

package/templates/standards/deployment-standards.md

@@ -1,4 +1,4 @@
-# 🚀 Deployment and Release Standards
+# [START] Deployment and Release Standards
 
 This document outlines the protocols for deploying, updating, and rolling back services managed by Agent Atabey.
 

package/templates/standards/governance-standards.md

@@ -1,4 +1,4 @@
-# 🎖️ Agent Atabey — Governance & Nizam Standards
+# [ATABEY] Agent Atabey — Governance & Nizam Standards
 
 This document defines the supreme governance mandates of the Agent Atabey framework.
 All agents **must** internalize these rules before executing any task.

package/templates/standards/llm-governance.md

@@ -1,4 +1,4 @@
-# 🤖 LLM Governance and Data Protection
+# [AI] LLM Governance and Data Protection
 
 This document outlines the security, safety, and discipline rules for interacting with Large Language Models within Atabey-managed projects. It aligns with the spirit of the EU AI Act, NIST AI RMF, and OWASP Top 10 for LLMs.
 

package/templates/standards/nextjs-standards.md

@@ -0,0 +1,13 @@
+# ⚛️ Corporate Next.js Standards
+
+This document defines the architectural and coding standards for Next.js (App Router) applications.
+
+## 1. Architecture Standards
+- **App Router First:** Use the App Router (`app/` directory) exclusively. Page router is deprecated.
+- **Server Component Default:** All components are React Server Components (RSC) by default. Add `"use client"` only when client-side interactivity, state, or effects are strictly required.
+- **Route Handlers:** Place API routes under `app/api/` and follow route handler signatures (`GET`, `POST`, etc.).
+
+## 2. Performance & SEO
+- **Metadata API:** Use the static or dynamic Metadata API for title/SEO tag definition.
+- **Image Optimization:** Always use next/image `<Image>` with explicit width/height or fluid placeholders.
+- **Layouts & Suspense:** Implement structured layouts and wrap slower fetching components in `<Suspense>` with skeleton UI fallbacks.

package/templates/standards/observability-standards.md

@@ -1,4 +1,4 @@
-# 📊 Observability and Monitoring Standards
+# [DATA] Observability and Monitoring Standards
 
 This document defines the requirements for logging, tracing, metrics, and alerting within Atabey-managed projects, following the "three pillars" model (logs, metrics, traces).
 

package/templates/standards/security-audit-standards.md

@@ -1,4 +1,4 @@
-# 🛡️ Security Audit Standards
+# [SECURITY] Security Audit Standards
 
 This document defines the security audit procedures required for all Agent Atabey-managed projects to ensure a "Defense-in-Depth" posture, aligned with OWASP ASVS and the OWASP Top 10.
 

package/templates/standards/security-standards.md

@@ -1,4 +1,4 @@
-# 🛡️ Corporate Security and Data Protection Standards
+# [SECURITY] Corporate Security and Data Protection Standards
 
 This document defines the security protocols and data protection standards for projects managed by Agent Atabey.
 

package/templates/standards/testing-standards.md

@@ -1,4 +1,4 @@
-# 🧪 Corporate Testing Standards
+# [SKILL] Corporate Testing Standards
 
 This document defines the testing discipline and scope rules for projects managed by Agent Atabey. Code quality must be ensured with automated tests.
 

package/templates/standards/vite-standards.md

@@ -0,0 +1,13 @@
+# ⚡ Corporate Vite Standards
+
+This document defines the configuration and development standards for Vite-based frontend applications.
+
+## 1. Core Config Rules
+- **TypeScript Integration:** Always use `vite-tsconfig-paths` to resolve TS path aliases automatically.
+- **Port Discipline:** Keep development ports standardized. Default frontend port is `5173`.
+- **Environment Variables:** Environment variables must be prefixed with `VITE_` and fully typed in `vite-env.d.ts`.
+
+## 2. Dev & Build Optimizations
+- **Build Target:** Target modern browsers (`esnext` or minimum `es2022`).
+- **Code Splitting:** Implement splitChunks (manualChunks) for vendor libraries (e.g. react, react-dom, react-router-dom) to keep bundle sizes under control.
+- **Minification:** Use `esbuild` for maximum build speeds.

package/framework-mcp/dist/constants.js

@@ -1,64 +0,0 @@
-import path from "path";
-/**
- * Agent Atabey — Single Source of Truth for framework constants.
- * Import from here instead of hardcoding paths, phases, or directory names.
- */
-// ─── Framework identity ───────────────────────────────────────────────────
-export const FRAMEWORK = {
-    NAME: "Agent Atabey",
-    CORE_DIR: ".atabey",
-    // This is the hub for unified adapter layouts (e.g. .agents/gemini, .agents/claude)
-    UNIFIED_HUB_DIR: ".agents",
-    // This is the default directory to scaffold new apps into
-    APPS_DIR: "apps",
-    // This is where all skills are stored
-    SKILLS_DIR: "skills",
-};
-export const FRAMEWORK_SUBDIRS = {
-    AGENTS: "agents",
-    SKILLS: "skills",
-    KNOWLEDGE: "knowledge",
-    MESSAGES: "messages",
-    MEMORY: "memory",
-    MEMORY_GRAPH: "memory-graph",
-    LOGS: "logs",
-    CONFIG: "config",
-};
-export const ROOT_CONFIG_FILES = {
-    MCP: "mcp.json",
-    NATIVE_MODULES: "native-modules.json",
-    TSCONFIG: "tsconfig.json",
-    ESLINT: "eslint.config.js",
-};
-export const MCP = {
-    // Environment variable used by MCP to identify project root
-    PROJECT_ROOT_ENV: "ATABEY_PROJECT_ROOT",
-    // Environment variable for test mode
-    TEST_DIR_ENV: "ATABEY_TEST_DIR",
-};
-export const MEMORY_FILES = {
-    STATE: "state.json",
-    SHARED_FACTS: "shared_facts.json",
-};
-export const NATIVE_AGENT_PATHS = {
-    gemini: ".gemini/agents",
-    claude: ".claude/agents",
-    cursor: ".cursor/rules",
-    codex: ".agents/instructions",
-    grok: ".grok",
-    "antigravity-cli": ".antigravity/agents",
-};
-// ─── Backward-compatible aliases ──────────────────────────────────────────
-export const CORE_FRAMEWORK_DIR = FRAMEWORK.CORE_DIR;
-export const UNIFIED_HUB_DIR = FRAMEWORK.UNIFIED_HUB_DIR;
-export const SKILLS_HUB_PATH = pathJoin(UNIFIED_HUB_DIR, FRAMEWORK_SUBDIRS.SKILLS);
-// ─── Path Helpers ─────────────────────────────────────────────────────────
-function pathJoin(...args) {
-    return path.join(...args);
-}
-function corePath(subdir, filename) {
-    return pathJoin(FRAMEWORK.CORE_DIR, subdir, filename);
-}
-export function knowledgePath(filename) {
-    return corePath(FRAMEWORK_SUBDIRS.KNOWLEDGE, filename);
-}

package/framework-mcp/dist/index.js

@@ -1,119 +0,0 @@
-import fs from "fs";
-import path from "path";
-import { fileURLToPath } from "url";
-import { Server } from "@modelcontextprotocol/sdk/server/index.js";
-import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
-import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
-import { TOOLS, toolHandlers } from "./tools/index.js";
-// ─── Server Setup ─────────────────────────────────────────────────
-const __dirname = path.dirname(fileURLToPath(import.meta.url));
-// Robustly find package.json by walking up from __dirname
-function findPackageJson(startDir) {
-    let currentDir = startDir;
-    while (currentDir !== path.parse(currentDir).root) {
-        const pkgPath = path.join(currentDir, "package.json");
-        if (fs.existsSync(pkgPath))
-            return pkgPath;
-        currentDir = path.dirname(currentDir);
-    }
-    throw new Error("Could not find package.json for atabey-mcp");
-}
-const pkgPath = findPackageJson(__dirname);
-const pkg = JSON.parse(fs.readFileSync(pkgPath, "utf8"));
-const serverVersion = pkg.version;
-const server = new Server({
-    name: "atabey-mcp",
-    version: serverVersion,
-}, {
-    capabilities: {
-        tools: {},
-    },
-});
-// Basic Schema Validator for Required Fields
-function validateArgs(toolName, args) {
-    const definition = TOOLS.find(t => t.name === toolName);
-    if (!definition)
-        return `Unknown tool: ${toolName}`;
-    const required = definition.inputSchema.required || [];
-    for (const field of required) {
-        if (args[field] === undefined || args[field] === null || args[field] === "") {
-            return `Missing required argument: '${field}' for tool '${toolName}'`;
-        }
-    }
-    return null;
-}
-server.setRequestHandler(ListToolsRequestSchema, async (request) => {
-    // 2026 Stateless Spec: Log client info from metadata if available
-    const meta = request._meta;
-    if (meta) {
-        process.stderr.write(`[MCP] Stateless ListTools from ${meta.client?.name || "unknown"} v${meta.client?.version || "?.?"}\n`);
-    }
-    return { tools: TOOLS };
-});
-server.setRequestHandler(CallToolRequestSchema, async (request) => {
-    const req = request;
-    const { name, arguments: args } = req.params;
-    const meta = request._meta;
-    // 2026 Stateless Spec: Prioritize metadata-driven context
-    if (meta) {
-        process.stderr.write(`[MCP] Stateless CallTool: ${name} (Client: ${meta.client?.name || "unknown"})\n`);
-    }
-    const projectRoot = process.env.ATABEY_PROJECT_ROOT || process.cwd();
-    try {
-        const handler = toolHandlers[name];
-        if (!handler) {
-            return {
-                isError: true,
-                content: [{ type: "text", text: `❌ Unknown tool: ${name}` }],
-            };
-        }
-        // 🛡️ Runtime Validation
-        const validationError = validateArgs(name, args || {});
-        if (validationError) {
-            return {
-                isError: true,
-                content: [{ type: "text", text: `❌ Validation Error: ${validationError}` }],
-            };
-        }
-        return await handler(projectRoot, args || {});
-    }
-    catch (error) {
-        const message = error instanceof Error ? error.message : "Unknown error occurred";
-        return {
-            isError: true,
-            content: [{ type: "text", text: `❌ Execution failed: ${message}` }],
-        };
-    }
-});
-// ─── Graceful Startup & Shutdown ──────────────────────────────────
-async function run() {
-    const transport = new StdioServerTransport();
-    // Prevent unhandled errors from crashing the MCP stream
-    process.on("uncaughtException", (error) => {
-        process.stderr.write(`[atabey-mcp] Uncaught exception: ${error.message}
-`);
-    });
-    process.on("unhandledRejection", (reason) => {
-        const message = reason instanceof Error ? reason.message : String(reason);
-        process.stderr.write(`[atabey-mcp] Unhandled rejection: ${message}
-`);
-    });
-    // Graceful shutdown on SIGINT/SIGTERM
-    const shutdown = async () => {
-        try {
-            await server.close();
-        }
-        catch {
-            // Already closed or failed — safe to ignore
-        }
-        process.exit(0);
-    };
-    process.on("SIGINT", shutdown);
-    process.on("SIGTERM", shutdown);
-    await server.connect(transport);
-}
-run().catch((error) => {
-    process.stderr.write(`[atabey-mcp] Fatal startup error: ${error.message}
-`);
-    process.exit(1);
-});

package/framework-mcp/dist/tools/control_plane/locking.js

@@ -1,82 +0,0 @@
-import fs from "fs";
-import path from "path";
-import { resolveFrameworkDir } from "../../utils/security.js";
-/**
- * Handles acquiring a stateful lock on a resource.
- */
-export async function handleAcquireLock(projectRoot, args) {
-    const { resource, agent, ttl = 60 } = args;
-    const frameworkDir = resolveFrameworkDir(projectRoot);
-    const lockDir = path.join(projectRoot, frameworkDir, "locks");
-    const lockPath = path.join(lockDir, `${resource}.lock`);
-    try {
-        if (!fs.existsSync(lockDir))
-            fs.mkdirSync(lockDir, { recursive: true });
-        // Check for stale lock first
-        if (fs.existsSync(lockPath)) {
-            const stat = fs.statSync(lockPath);
-            const now = new Date().getTime();
-            const age = (now - stat.mtimeMs) / 1000;
-            if (age < ttl) {
-                return {
-                    isError: true,
-                    content: [{ type: "text", text: `Resource '${resource}' is currently locked by another agent.` }]
-                };
-            }
-            // Lock expired, safe to override by renaming first (POSIX atomic operation)
-            const tempLockPath = `${lockPath}.${Math.random().toString(36).substring(2)}.old`;
-            try {
-                fs.renameSync(lockPath, tempLockPath);
-                fs.unlinkSync(tempLockPath);
-            }
-            catch {
-                // If rename failed, it means another agent already evicting/deleting it.
-                // Do not delete anything else; proceed and let writeFileSync (wx flag) fail if a new lock exists.
-            }
-        }
-        // Use 'wx' flag for atomic file creation
-        const lockData = JSON.stringify({ agent, timestamp: new Date().toISOString() });
-        fs.writeFileSync(lockPath, lockData, { flag: "wx" });
-        return {
-            content: [{ type: "text", text: `✅ Lock acquired for resource '${resource}' by ${agent}.` }]
-        };
-    }
-    catch (e) {
-        const error = e;
-        if (error.code === "EEXIST") {
-            return {
-                isError: true,
-                content: [{ type: "text", text: `Resource '${resource}' was just acquired by another agent.` }]
-            };
-        }
-        return {
-            isError: true,
-            content: [{ type: "text", text: `Failed to acquire lock: ${String(e)}` }]
-        };
-    }
-}
-/**
- * Handles releasing a lock.
- */
-export async function handleReleaseLock(projectRoot, args) {
-    const { resource, agent } = args;
-    const frameworkDir = resolveFrameworkDir(projectRoot);
-    const lockPath = path.join(projectRoot, frameworkDir, "locks", `${resource}.lock`);
-    try {
-        if (!fs.existsSync(lockPath)) {
-            return { content: [{ type: "text", text: `ℹ️ No lock found for resource '${resource}'.` }] };
-        }
-        const lockData = JSON.parse(fs.readFileSync(lockPath, "utf8"));
-        if (lockData.agent !== agent) {
-            return {
-                isError: true,
-                content: [{ type: "text", text: `❌ Denied: You do not own the lock for '${resource}'. Owned by ${lockData.agent}.` }]
-            };
-        }
-        fs.unlinkSync(lockPath);
-        return { content: [{ type: "text", text: `✅ Lock released for resource '${resource}' by ${agent}.` }] };
-    }
-    catch (e) {
-        return { isError: true, content: [{ type: "text", text: `Failed to release lock: ${String(e)}` }] };
-    }
-}

package/framework-mcp/dist/tools/control_plane/registry.js

@@ -1,34 +0,0 @@
-import fs from "fs";
-import path from "path";
-import { resolveFrameworkDir } from "../../utils/security.js";
-/**
- * Handles agent registration with the Control Plane.
- * This can be used to validate permissions and active status.
- */
-export async function handleRegisterAgent(projectRoot, args) {
-    const { agent, role, capability = 5 } = args;
-    const frameworkDir = resolveFrameworkDir(projectRoot);
-    const registryDir = path.join(projectRoot, frameworkDir, "registry");
-    const agentFile = path.join(registryDir, `${agent.replace("@", "")}_active.json`);
-    try {
-        if (!fs.existsSync(registryDir))
-            fs.mkdirSync(registryDir, { recursive: true });
-        const agentData = {
-            agent,
-            role,
-            capability,
-            last_seen: new Date().toISOString(),
-            status: "ACTIVE"
-        };
-        fs.writeFileSync(agentFile, JSON.stringify(agentData, null, 2));
-        return {
-            content: [{ type: "text", text: `🎖️ Agent ${agent} (${role}) registered successfully in the Atabey Control Plane.` }]
-        };
-    }
-    catch (e) {
-        return {
-            isError: true,
-            content: [{ type: "text", text: `Failed to register agent: ${String(e)}` }]
-        };
-    }
-}