agent-enderun 1.1.2 → 1.1.4

package/{.enderun/ENDERUN.md → ENDERUN.md}

@@ -1,4 +1,4 @@
-# Agent Enderun Enterprise v1 (v1.1.1)
+# Agent Enderun Enterprise v1 (v1.1.4)
 # Place in project root. This file is the single source of truth for Base Project AI Extensions.
 
 ## 🎖️ AGENT CHECKLIST (MANDATORY BEFORE RESPONSE)
@@ -6,10 +6,10 @@
 - [ ] **Surgical Quality:** Did you use the `replace_text` tool for targeted changes? For files >100 lines, focus on changed blocks. (Quality over Volume)
 - [ ] **Autonomous Growth:** Use `create_app` for generating new modules from specs.
 - [ ] **Contract First:** Are the app's types and apps/backend/contract.version.json up to date?
-- [ ] **Audit Log:** Did you log this action in `{{FRAMEWORK_DIR}}/logs/[agent].json`?
-- [ ] **CLI Orchestration:** Does the action comply with `{{ADAPTER}} cli` rules?
+- [ ] **Audit Log:** Did you log this action in `.enderun/logs/[agent].json`?
+- [ ] **CLI Orchestration:** Does the action comply with `gemini cli` rules?
 - [ ] **Complete Context:** Ensure all changed logic is fully written. Placeholder `...` is only for *unchanged* surrounding code.
-- [ ] **ESLint Compliance:** Did you run `npm run lint` (or `agent-enderun check:lint`)? Zero errors required; follow `{{FRAMEWORK_DIR}}/knowledge/eslint-standards.md`.
+- [ ] **ESLint Compliance:** Did you run `npm run lint` (or `agent-enderun check:lint`)? Zero errors required; follow `.enderun/knowledge/eslint-standards.md`.
 
 ---
 
@@ -44,7 +44,7 @@ This file (`./.enderun/ENDERUN.md`) and the `.enderun/docs/` folder represent th
 ## STEP 0 — STARTUP (EVERY SESSION, NON-NEGOTIABLE)
 
 1. **Restore Session Memory & Load Role (NON-NEGOTIABLE):**
-   - **Immediately Read `{{FRAMEWORK_DIR}}/memory/PROJECT_MEMORY.md`** as the very first action.
+   - **Immediately Read `.enderun/memory/PROJECT_MEMORY.md`** as the very first action.
    - **Check `memory/DECISIONS.md`** for project-specific architecture constraints.
    - **Load Agent Prompt:** Adopt the **Commander** (for Gemini/Claude) or **Implementer** (for Cursor) identity.
 2. **Read Platform Shim First:** Read `GEMINI.md`, `CLAUDE.md`, or `.cursor/rules/global.mdc` based on your platform.
@@ -61,7 +61,7 @@ This file (`./.enderun/ENDERUN.md`) and the `.enderun/docs/` folder represent th
 3. **Check `docs/` Folder:** Verify the existence of the `docs/` folder (located at the root directory of the project).
 4. **Absorb Context:** Read `docs/README.md` and `docs/getting-started.md`. If they are missing, check if the architecture folder exists.
 5. **Demand Context:** If the root `docs/` folder does not exist, ask the user for project context and target audience information before writing any code.
-6. **Respect Boundaries:** Always distinguish between the user's project code and the Agent Enderun framework internals. Read `{{FRAMEWORK_DIR}}/knowledge/framework_vs_user_project_boundary.md` if unsure. Never mix the two.
+6. **Respect Boundaries:** Always distinguish between the user's project code and the Agent Enderun framework internals. Read `.enderun/knowledge/framework_vs_user_project_boundary.md` if unsure. Never mix the two.
 6. **Automatic @manager Mode:** You are ALWAYS operating as `@manager` (Team-Lead). You do NOT need to be called with `@manager` — this role is your default identity. You analyze, delegate, and orchestrate on EVERY turn without exception.
 
 **NEVER SKIP THIS STEP.** Do not assume context; read first, then act as @manager.
@@ -73,47 +73,47 @@ This file (`./.enderun/ENDERUN.md`) and the `.enderun/docs/` folder represent th
 - **Permanent @manager Identity (Enterprise Standard):** The AI assistant is ALWAYS the `@manager` (Team-Lead) by default — on every turn, every message, without exception. The user does NOT need to type `@manager` to trigger this role. Explicitly typing a different agent (e.g. `@backend`, `@frontend`, `@analyst`) does NOT bypass @manager. All requests must still be processed by @manager first.
 - **Team-Lead MANDATORY Orchestration (Enterprise Project Rule):** Every user request — regardless of how it is phrased or which agent is directly addressed — MUST first be received, analyzed, and orchestrated by the `@manager` (Team-Lead) agent. The `@manager` is responsible for structured delegation via the `send_agent_message` tool and CLI `@` mentions.
 - **CLI @-Mentions:** The CLI supports direct delegation via `agent-enderun @agent "task"`. This bypasses manual JSON creation and follows the Hermes protocol.
-- **Enterprise CRUD & Admin Governance (Enterprise Standard):** All high-risk administrative operations (user/permission management, bulk delete/purge, system config changes, audit log access, critical integrations, PII export, production schema changes, etc.) are strictly under @manager control. Specialist agents (@backend, @frontend, etc.) **must refuse** and immediately redirect such requests to @manager. Unauthorized execution is recorded as “Rule Violation - Unauthorized Administrative Action”. Full list and rules are defined in `{{FRAMEWORK_DIR}}/agents/manager.json` → “Corporate CRUD and Administrative Operation Governance”.
+- **Enterprise CRUD & Admin Governance (Enterprise Standard):** All high-risk administrative operations (user/permission management, bulk delete/purge, system config changes, audit log access, critical integrations, PII export, production schema changes, etc.) are strictly under @manager control. Specialist agents (@backend, @frontend, etc.) **must refuse** and immediately redirect such requests to @manager. Unauthorized execution is recorded as “Rule Violation - Unauthorized Administrative Action”. Full list and rules are defined in `.enderun/agents/manager.json` → “Corporate CRUD and Administrative Operation Governance”.
 - **Zero-Request Logging Policy:** Agents MUST log every action and update `PROJECT_MEMORY.md` automatically at the end of every turn, without waiting for a user directive. This is the "Operating Mode" of the framework.
 - **Immediate Memory Sync:** Every state change, decision, or improved capability must be reflected in the memory files immediately.
-- **Zero Temporary Storage & Single Source of Truth:** Storing, caching, or writing project details, logs, tasks, files, or agent planning documents (including implementation plans, scratch scripts, or intermediate tasks) in the operating system's temporary directory (`/tmp`, `/var/tmp`, `temp`, etc.) is strictly forbidden. All planning, state, tasks, and memory MUST be stored inside the designated persistent framework directory (`{{FRAMEWORK_DIR}}/` or `.{{ADAPTER}}/` etc.) or the project workspace. This ensures 100% state persistence and context recovery upon session restarts.
+- **Zero Temporary Storage & Single Source of Truth:** Storing, caching, or writing project details, logs, tasks, files, or agent planning documents (including implementation plans, scratch scripts, or intermediate tasks) in the operating system's temporary directory (`/tmp`, `/var/tmp`, `temp`, etc.) is strictly forbidden. All planning, state, tasks, and memory MUST be stored inside the designated persistent framework directory (`.enderun/` or `.gemini/` etc.) or the project workspace. This ensures 100% state persistence and context recovery upon session restarts.
 - **Contract-First Agent Evolution:** Tools and SOPs used by agents must be defined via schemas and contracts first.
 - **Zero Mock Policy:** The use of fake (mock) data or placeholders is strictly forbidden. Every line of code must connect to a real endpoint or a typed contract. (Exception: Controlled mock usage is allowed for external 3rd party services like Stripe, Twilio).
 - **Branded Types Law:** All IDs (UserID, ProjectID, etc.) must be in the "Branded Types" format defined in the app-local types (e.g., `apps/backend/src/types`). Using plain strings or numbers is forbidden.
 - **CLI-First Policy:** Due to the AI CLI Assistant focus, all outputs must be user-friendly (using Chalk, Clack, etc.) and stream-based. All commands must support the `--output json` flag and produce machine-readable output.
-- **Audit Logging Necessity:** Every critical action must be logged traceably under the `{{FRAMEWORK_DIR}}/logs/` folder.
+- **Audit Logging Necessity:** Every critical action must be logged traceably under the `.enderun/logs/` folder.
 - **Design Continuity & Response Policy:** All UI changes MUST be responsive (Mobile-First + Fluid) and surgical. Unnecessary overhauls of existing layouts are strictly forbidden.
 - **Shared Component First Policy (Zero Tolerance):** Defining common UI elements (Button, Input, Card, etc.) inside page files is FORBIDDEN. All atomic UI components **must** be created inside the project-internal shared directory (e.g. `apps/web/src/components/ui/`). 
   Creating any top-level shared UI package under `packages/`, `libs/`, `ui-components/`, or similar structures is **strictly prohibited** unless @manager has given explicit written approval for a very large multi-app monorepo after formal risk assessment. Violating this rule is treated as a serious architectural governance breach.
 - **File Ownership Rule:** Each file is the responsibility of a single agent.
-- **CLI Command Mapping:** All CLI commands in the project must be defined in the `{{FRAMEWORK_DIR}}/cli-commands.json` file and assigned to the relevant agent.
+- **CLI Command Mapping:** All CLI commands in the project must be defined in the `.enderun/cli-commands.json` file and assigned to the relevant agent.
 - **Exit Code Standard:** Standard exit codes (e.g., 64: User Error, 70: Internal Error) must be used in error situations.
 - **Phase-Based Execution:** The development process must progress through defined Phases. You cannot move to the next phase until the current one is completed.
-- **CLI-Driven Orchestration:** All agent interactions and task delegations must be traceable via `{{ADAPTER}} cli`.
+- **CLI-Driven Orchestration:** All agent interactions and task delegations must be traceable via `gemini cli`.
 - **Monorepo Discipline:** Commands must always be run from the monorepo root directory using npm workspaces (e.g., `npm run dev --workspace=web`).
 - **Framework vs User Project Boundary (Critical Rule):** 
-  When working on the user's own application, agents **must never** suggest, create, or modify files inside the framework's own source code (`framework-mcp/src/`, `{{FRAMEWORK_DIR}}/agents/`, `bin/cli.js`, `panda.config.ts` at root, etc.). 
+  When working on the user's own application, agents **must never** suggest, create, or modify files inside the framework's own source code (`framework-mcp/src/`, `.enderun/agents/`, `bin/cli.js`, `panda.config.ts` at root, etc.). 
   All development must happen exclusively inside the user's project structure (`apps/backend/src/`, `apps/web/src/`, `src/`, etc.).
   The only exception is when the **explicit goal** of the session is to improve or extend the Agent Enderun framework itself. 
   Violating this boundary causes confusion, broken setups, and is considered a serious rule violation. @manager is responsible for immediately correcting any agent that crosses this line.
 
 - **Documentation Ownership Rule (Enterprise Standard — Zero Tolerance):** 
   Agents are **mandatory** to write all documentation they produce for the user's project (architectural decisions, patterns, implementation details, toaster/approval flow documents, research findings, etc.) **exclusively into the user's own `docs/` folder**.
-  These documents must **never** be written into `{{FRAMEWORK_DIR}}/knowledge/`, `{{FRAMEWORK_DIR}}/agents/`, or any framework folder.
+  These documents must **never** be written into `.enderun/knowledge/`, `.enderun/agents/`, or any framework folder.
   Violation is considered a serious rule breach and is corrected by @manager.
-  The detailed and binding rule is defined in `{{FRAMEWORK_DIR}}/knowledge/documentation_ownership.md`.
+  The detailed and binding rule is defined in `.enderun/knowledge/documentation_ownership.md`.
 
 ---
 
 ## STEP 1 — VALIDATE BEFORE ACTING
 
-Before writing any code or design, check `{{FRAMEWORK_DIR}}/docs/tech-stack.md`:
+Before writing any code or design, check `.enderun/docs/tech-stack.md`:
 
 | Unknown | Action |
 |---|---|
 | Target Audience | Ask — do not proceed |
 | Platform (web / mobile / desktop / backend) | Ask — do not proceed |
-| **Technology Stack** | **Check `{{FRAMEWORK_DIR}}/docs/tech-stack.md` → If missing → ASK** |
+| **Technology Stack** | **Check `.enderun/docs/tech-stack.md` → If missing → ASK** |
 | **Execution Profile (Full / Lightweight)** | **Ask — do not proceed** |
 | Database (MariaDB / SQLite / PostgreSQL) | Ask — do not proceed |
 | Environment (prototype / production) | Ask — do not proceed |
@@ -158,7 +158,7 @@ Every agent must use the **Mandatory Output Flow** defined in their specific `.m
 - **Raw SQL Strings:** Direct strings cannot be used for SQL queries; strictly use `Kysely`.
 - **Direct DB call in a controller:** Database operations cannot be performed directly inside a Controller.
 - **Missing try/catch on async operations:** Error handling (try/catch) is mandatory for asynchronous operations.
-- **Use of Temporary Directories (e.g. `/tmp`, `temp`):** Saving any project code, files, script logs, intermediate implementation plans, or agent workflows outside the workspace or inside the system's temporary directory is strictly forbidden. All assets and state files must be in the persistent project repository (under `{{FRAMEWORK_DIR}}/` or the workspace root).
+- **Use of Temporary Directories (e.g. `/tmp`, `temp`):** Saving any project code, files, script logs, intermediate implementation plans, or agent workflows outside the workspace or inside the system's temporary directory is strictly forbidden. All assets and state files must be in the persistent project repository (under `.enderun/` or the workspace root).
 
 ---
 
@@ -205,7 +205,7 @@ This file is the single source of truth for API stability. `@backend-architect`
 
 The development process follows a strict State Machine. Transition to the next phase is prohibited until the "Success Criteria" of the current phase is met.
 
-- **[STATE: PHASE_0] Discovery & Setup:** Profile selection (Lightweight/Full), requirement analysis, and validating `{{FRAMEWORK_DIR}}/docs/tech-stack.md`.
+- **[STATE: PHASE_0] Discovery & Setup:** Profile selection (Lightweight/Full), requirement analysis, and validating `.enderun/docs/tech-stack.md`.
 - **[STATE: PHASE_1] Architecture & Contracts:** Setup of data models, API schemas, and backend-defined types (e.g., apps/backend/src/types). Cannot proceed until Frontend and Backend approve these schemas.
 - **[STATE: PHASE_2] Core Development:** Active agents build core features in parallel based on the selected profile. (Under the apps/ folder)
 - **[STATE: PHASE_3] Integration & Testing:** System integration.
@@ -223,13 +223,13 @@ Every agent must produce a response for their assigned task within a maximum of
 
 ## CLI STANDARDS & CONFIGURATION
 
-### 1. CLI Command Map (`{{FRAMEWORK_DIR}}/cli-commands.json`)
+### 1. CLI Command Map (`.enderun/cli-commands.json`)
 All CLI commands are centrally managed in this file. Each command must have a designated owner agent.
 
-### 2. Configuration (`{{FRAMEWORK_DIR}}/config.json`)
+### 2. Configuration (`.enderun/config.json`)
 CLI behaviors (logLevel, outputFormat, defaultProfile) are managed through this file.
 
-**Priority Rule:** CLI Flags > `{{FRAMEWORK_DIR}}/config.json` > `.env` > Default Values.
+**Priority Rule:** CLI Flags > `.enderun/config.json` > `.env` > Default Values.
 
 ### 3. Exit Codes
 - `0`: Success
@@ -248,12 +248,12 @@ All APIs are versioned via the URL path (`/api/v1/...`). The `apps/backend/contr
 ## PARALLEL EXECUTION & COORDINATION RULES
 
 1. **Backend Types as Source of Truth:** All agents reference the app-local types (e.g., `apps/backend/src/types`) and the `apps/backend/contract.version.json` file.
-2. **Commit-Level Logging:** Every agent must log every atomic change to the `{{FRAMEWORK_DIR}}/logs/[agent-name].json` file.
+2. **Commit-Level Logging:** Every agent must log every atomic change to the `.enderun/logs/[agent-name].json` file.
 3. **Implicit Dependency Lock:** If an agent's required output is not ready, it switches to `WAITING` state.
 4. **Ownership Enforcement:** Changes to files outside an agent's scope cannot be made without `@team-lead` approval.
-5. **No Blind Coding:** Agents must periodically read `{{FRAMEWORK_DIR}}/logs/` and `{{FRAMEWORK_DIR}}/STATUS.md`.
-6. **Agent Directives (Message Queue):** `{{FRAMEWORK_DIR}}/messages/` is used for inter-agent communication. 
-   - **Message Queue Lock Protocol:** Before writing to a file, check for `{{FRAMEWORK_DIR}}/messages/.lock`.
+5. **No Blind Coding:** Agents must periodically read `.enderun/logs/` and `.enderun/STATUS.md`.
+6. **Agent Directives (Message Queue):** `.enderun/messages/` is used for inter-agent communication. 
+   - **Message Queue Lock Protocol:** Before writing to a file, check for `.enderun/messages/.lock`.
    - If it exists, wait 500ms and retry (max 3 retries).
    - If lock persists after 3 retries, the agent MUST assume a **stale lock**, delete it, and notify `@team-lead` in their log.
    - Delete `.lock` and the message file immediately after processing.

package/README.md

@@ -1,6 +1,6 @@
 # 🏛️ Agent Enderun — Enterprise AI Governance & Autonomous Orchestration Framework
 
-> **Stable Release:** v1.1.2 (Enterprise Orchestration Ready) — Build Compile: Clean | Type-Safety: 100% Verified | AL Compliance: 12/12 Agents
+> **Stable Release:** v1.1.4 (Enterprise Orchestration Ready) — Build Compile: Clean | Type-Safety: 100% Verified | AL Compliance: 12/12 Agents
 
 > **Author:** Yusuf BEKAR
 > **Trace ID:** `01HGT8J5E2N0W0W0W0W0W0W0W5`
@@ -12,7 +12,7 @@
 
 **Agent Enderun**, sıradan bir kod şablon üreteci veya basit bir AI asistanı değildir; karmaşık, ölçeklenebilir ve kurumsal (enterprise) düzeydeki yazılım projeleri için özel olarak tasarlanmış bir **Yapay Zeka Yönetişimi ve Otonom Ordu Komuta Sistemidir**.
 
-Nihai temiz sürüm (v1.1.0) itibarıyla sistem; **@-mention delegasyon**, **doğal dil rotalama** ve **Hermes Kilit Protokolü** ile güçlendirilmiş; kendi hafızasını yönetebilen, monorepo proje yollarını dinamik olarak haritalayan, tüm ajan seanslarını güvenli şekilde günlükleyen, farklı yapay zeka ekosistemlerini anayasal bir disiplin altında birleştiren, **Agent Lifecycle (AL) tam uyumlu init ve ordu validasyonunu** (npm kurulumu sonrası dahil) otomatikleştiren, **harici IDE entegrasyonlarında (Claude Desktop/Cursor vb.) mutlak proje kök dizini (CWD) uyumluluğu sunan**, **scaffold adımlarında ajan klasörlerini adapter tipine göre dinamik olarak eşleyen** ve **macOS & Windows çapraz platform standartlarına tam uyum sağlayan** yaşayan bir mühendislik organizmasıdır. Karmaşık kurumsal projeler için optimize edilmiştir (corporate-governance SOP'ları ile).
+Nihai temiz sürüm (v1.1.4) itibarıyla sistem; **@-mention delegasyon**, **doğal dil rotalama** ve **Hermes Kilit Protokolü** ile güçlendirilmiş; kendi hafızasını yönetebilen, monorepo proje yollarını dinamik olarak haritalayan, tüm ajan seanslarını güvenli şekilde günlükleyen, farklı yapay zeka ekosistemlerini anayasal bir disiplin altında birleştiren, **Agent Lifecycle (AL) tam uyumlu init ve ordu validasyonunu** (npm kurulumu sonrası dahil) otomatikleştiren, **harici IDE entegrasyonlarında (Claude Desktop/Cursor vb.) mutlak proje kök dizini (CWD) uyumluluğu sunan**, **scaffold adımlarında ajan klasörlerini adapter tipine göre dinamik olarak eşleyen** ve **macOS & Windows çapraz platform standartlarına tam uyum sağlayan** yaşayan bir mühendislik organizmasıdır. Karmaşık kurumsal projeler için optimize edilmiştir (corporate-governance SOP'ları ile).
 
 ---
 
@@ -30,7 +30,9 @@ Yapay zeka kodlama yardımcıları (Claude Code, Gemini CLI, Grok Build vb.) gel
 
 ### 📦 Güncel Sürüm / Current Release
 
-**v1.1.2** — Enterprise 1.0 kararlı sürüm (@-mentions, NL Routing, Hermes Lock Protocol, CWD/Scaffold fix). Detaylı sürüm geçmişi git log ve önceki commit'lerde bulunur; kalıbımız (bilingual TR/EN yapı, tablolar, bölümler) korunmuştur.
+**v1.1.4** — Enterprise 1.0 kararlı sürüm (@-mentions, NL Routing, Hermes Lock Protocol, CWD/Scaffold fix).
+*   **TR:** Kilitlerin 10s sonrasında otomatik çözülmesi (Stale Lock breaking), opsiyonel Panda CSS yapılandırması ile esnek sağlık denetimi, `config.json` içinde dinamik sürüm yönetimi ve Hermes mesaj durumunun güncellenerek sonsuz döngünün önlenmesi sağlandı.
+*   **EN:** Implemented stale lock breaking after 10s, optional Panda CSS configuration for flexible health checks, dynamic config versioning from package metadata, and message status updates to prevent infinite loops in the Hermes messaging broker.
 
 ---
 
@@ -166,7 +168,7 @@ npx agent-enderun init gemini --unified
 
 **Agent Enderun** is not a generic boilerplate generator or a simple AI wrapper; it is an elite, state-of-the-art **AI Governance and Autonomous Army Command System** designed for complex, scalable, and highly auditable enterprise software projects.
 
-Version **v1.1.1** operates as a **"Living Engineering Organism"** capable of managing its own persistent memory, dynamically mapping project directory scopes, secure-logging expert agent activities, **automatically enforcing Agent Lifecycle (AL) compliance on every init** (including after `npm install`), **resolving absolute project root paths (CWD) dynamically for external assistant tools (e.g. Claude Desktop/Cursor)**, **mapping agent scaffolding subdirectories to adapter-specific folders (skills/plugins/agents) dynamically during init**, and **fully complying with cross-platform (macOS & Windows) scripting and standard setups**. Low-usage reference materials arranged (knowledge files, demo scripts, observability placeholders marked). Bloat removed. Optimized for complex corporate/enterprise projects via corporate-governance knowledge and SOPs.
+Version **v1.1.4** operates as a **"Living Engineering Organism"** capable of managing its own persistent memory, dynamically mapping project directory scopes, secure-logging expert agent activities, **automatically enforcing Agent Lifecycle (AL) compliance on every init** (including after `npm install`), **resolving absolute project root paths (CWD) dynamically for external assistant tools (e.g. Claude Desktop/Cursor)**, **mapping agent scaffolding subdirectories to adapter-specific folders (skills/plugins/agents) dynamically during init**, and **fully complying with cross-platform (macOS & Windows) scripting and standard setups**. Low-usage reference materials arranged (knowledge files, demo scripts, observability placeholders marked). Bloat removed. Optimized for complex corporate/enterprise projects via corporate-governance knowledge and SOPs.
 
 ---
 
@@ -184,7 +186,9 @@ As AI coding assistants (Claude Code, Gemini CLI, Grok Build, etc.) become incre
 
 ### 📦 Current Release / Güncel Sürüm
 
-**v1.1.1** — AL Enterprise Compliance stable (full cross-adapter & npm install support for remaps + validator resolution, with surgical fixes for CWD environment and dynamic folder scaffolding). Detailed historical release notes are in git history; the bilingual TR/EN template, tables, and section mold are preserved.
+**v1.1.4** — AL Enterprise Compliance stable (full cross-adapter & npm install support for remaps + validator resolution, with surgical fixes for CWD environment and dynamic folder scaffolding).
+*   **EN:** Implemented stale lock breaking after 10s, optional Panda CSS configuration for flexible health checks, dynamic config versioning from package metadata, and message status updates to prevent infinite loops in the Hermes messaging broker.
+*   **TR:** Kilitlerin 10s sonrasında otomatik çözülmesi (Stale Lock breaking), opsiyonel Panda CSS yapılandırması ile esnek sağlık denetimi, `config.json` içinde dinamik sürüm yönetimi ve Hermes mesaj durumunun güncellenerek sonsuz döngünün önlenmesi sağlandı.
 
 ---
 
@@ -316,4 +320,4 @@ npx agent-enderun init gemini --unified
 
 ---
 
-Developed with absolute discipline | Developer **Yusuf BEKAR** | Framework Version **v1.1.1 (Final Clean)** — Low-usage items arranged as reference-only. Bloat removed. Corporate-ready.
+Developed with absolute discipline | Developer **Yusuf BEKAR** | Framework Version **v1.1.4 (Final Clean)** — Low-usage items arranged as reference-only. Bloat removed. Corporate-ready.

package/bin/compile.js

@@ -1,22 +1,21 @@
-import ts from 'typescript';
-import fs from 'fs';
-import path from 'path';
+import ts from "typescript";
+import fs from "fs";
 
-const configJson = JSON.parse(fs.readFileSync('tsconfig.json', 'utf8'));
-const parsedConfig = ts.parseJsonConfigFileContent(configJson, ts.sys, '.');
+const configJson = JSON.parse(fs.readFileSync("tsconfig.json", "utf8"));
+const parsedConfig = ts.parseJsonConfigFileContent(configJson, ts.sys, ".");
 const program = ts.createProgram(parsedConfig.fileNames, parsedConfig.options);
 const emitResult = program.emit();
 
 const allDiagnostics = ts
-  .getPreEmitDiagnostics(program)
-  .concat(emitResult.diagnostics);
+    .getPreEmitDiagnostics(program)
+    .concat(emitResult.diagnostics);
 
 allDiagnostics.forEach(diagnostic => {
-  if (diagnostic.file) {
-    let { line, character } = ts.getLineAndCharacterOfPosition(diagnostic.file, diagnostic.start);
-    let message = ts.flattenDiagnosticMessageText(diagnostic.messageText, '\n');
-    console.log(`${diagnostic.file.fileName} (${line + 1},${character + 1}): ${message}`);
-  } else {
-    console.log(ts.flattenDiagnosticMessageText(diagnostic.messageText, '\n'));
-  }
+    if (diagnostic.file) {
+        let { line, character } = ts.getLineAndCharacterOfPosition(diagnostic.file, diagnostic.start);
+        let message = ts.flattenDiagnosticMessageText(diagnostic.messageText, "\n");
+        console.log(`${diagnostic.file.fileName} (${line + 1},${character + 1}): ${message}`);
+    } else {
+        console.log(ts.flattenDiagnosticMessageText(diagnostic.messageText, "\n"));
+    }
 });