ai-enderun 0.0.9 → 0.0.11

package/.enderun/PROJECT_MEMORY.md

@@ -18,320 +18,50 @@ This file is the Single Source of Truth (SSOT) and the persistent memory of the
 | Backend | Node.js 20+ + Fastify + Kysely |
 | DB | PostgreSQL |
 | Auth | Not yet defined |
-| Deploy | Not yet defined |
-
-## DOD STATUS
-
-| Phase | Status | Note |
-| :--- | :--- | :--- |
-| PHASE_0 | COMPLETED | Framework stabilized at v0.0.9 Master |
-| PHASE_1 | PENDING | After `contract.version.json` and first official contracts |
-| PHASE_2 | PENDING | Feature development has not started |
-| PHASE_3 | PENDING | Integration work has not started |
-| PHASE_4 | PENDING | Handover phase has not been reached |
-
-## CRITICAL DECISIONS
-
-| Date | Decision | Rationale | Agent |
-| :--- | :--- | :--- | :--- |
-| 2026-05-07 | Standalone Architecture | Maximum flexibility and independence | @manager |
-| 2026-05-07 | Contract-First Discipline | Scalable development with zero errors | @manager |
-| 2026-05-07 | Canonical MCP Tooling | Aligning agent capabilities while maintaining tool names in a single dictionary | @analyst |
-| 2026-05-08 | Panda CSS Transition | Switching from Tailwind to Panda CSS for architectural discipline and type safety | @manager |
-| 2026-05-08 | Zero UI Library Policy | Banning ready-made libraries for originality and full control | @manager |
-| 2026-05-08 | ULID Standard | Switching from UUID to ULID for database performance and sortability (Standard: 26-char ULID) | @manager |
-| 2026-05-08 | English Translation | Moving all documentation and rules to English for international standards (Bilingual READMEs) | @manager |
-| 2026-05-08 | Documentation Decoupling | Reserved root `docs/` for user project requirements and `{{FRAMEWORK_DIR}}/docs/` for framework rules | @manager |
-| 2026-05-08 | Smart Init System | Automated adapter configuration (Gemini symlinks, Claude MCP guidance) in CLI | @manager |
-| 2026-05-08 | Continuity Principle | Mandating agents to follow existing code patterns and memory-driven decisions | @manager |
-
-## DELIVERABLES
-
-| Module | Status | Agent | Date |
-| :--- | :--- | :--- | :--- |
-| Root and package README layout | Completed | @analyst | 2026-05-07 |
-| Agent SOP core library | Completed | @manager | 2026-05-07 |
 
 ## ACTIVE TASKS
 
-| Trace ID | Task | Agent | Priority | Status |
-| :--- | :--- | :--- | :--- | :--- |
-| 01KR44729Z08BQQ4FCDAVNC148 | Documentation Overhaul & Agent Evangelism | @manager | P1 | COMPLETED |
-| 01KR45N4S0XW6F7G6T1W8F9D2V | Smart Init System Implementation | @manager | P1 | COMPLETED |
-| 01KR45Q8N1V7Z7H9R2M3W9X4Y1 | Robust Access Law & Tool Failure Resolution | @manager | P1 | COMPLETED |
-| 01KR45W2Z91Y5K8M2T3V4X9N7R | Documentation Path Alignment (Root docs/ Fix) | @manager | P1 | COMPLETED |
-| 01KR45Y0M2X3V1B7D9N4Z2K8L5 | README Quick Start Guide Addition | @manager | P2 | COMPLETED |
-| 01KR460M3N1B5V9X2D4Z8L7K1R | Tech-Stack.md Relocation (Root docs/ Fix) | @manager | P1 | COMPLETED |
-| 01KR463F8N1V7W2Z9M3D4G7H5K | Version Bump to v0.0.9 & Health Check | @manager | P1 | COMPLETED |
-| 01KR4666M2X9R1T4V8D7Z2L5K1 | @manager SOP Hardening (MCP Health Check) | @manager | P1 | COMPLETED |
-| 01KR469B7N1V2W8Z3M4D9G1H5L | Build Automation & v0.0.9 Release | @manager | P1 | COMPLETED |
-| 01KR46D2M3X9V1T8Z4D7Z2L5K1 | Stable v0.0.9 Release (Complete Package) | @manager | P1 | COMPLETED |
-| 01KR46K8M2X3V9B7D4Z1L5K1R2 | Dynamic Placeholder System ({{FRAMEWORK_DIR}}) | @manager | P1 | COMPLETED |
-| 01KR46N2B7V1X9Z4M3D5G7H5L1 | 8th Specialist Added (@git) | @manager | P1 | COMPLETED |
-| 01KR444BM94P5W3ERVJ3YJ9T01 | Agent Report Version Synchronization (v0.0.9) | @manager | P1 | COMPLETED |
-| 01KR442W6MP3GXHF7TD32GJG1V | Agent SOP Hardening & Continuity Alignment (v0.0.9) | @manager | P1 | COMPLETED |
-
-## HISTORY (Persistent Memory)
-
-### 2026-05-08 — 8th Specialist Added (@git)
-
-- **Agent:** [[agents/manager|@manager]]
-- **Trace ID:** 01KR46N2B7V1X9Z4M3D5G7H5L1
-- **Action:** Added the `@git` agent (Version Control Specialist) as the 8th core role. Created `{{FRAMEWORK_DIR}}/agents/git.md` SOP and updated `ENDERUN.md` and `README.md`.
-- **Decision:** Dedicated a specialized role for Git management to ensure high-quality, atomic, and traceable repository history, which is critical for professional collaboration and rollbacks.
-- **Next Step:** Encourage users to utilize @git for all repository-related tasks.
-
-### 2026-05-08 — Dynamic Placeholder System ({{FRAMEWORK_DIR}})
-
-- **Agent:** [[agents/manager|@manager]]
-- **Trace ID:** 01KR46K8M2X3V9B7D4Z1L5K1R2
-- **Action:** Introduced a `{{FRAMEWORK_DIR}}` placeholder system across all SOPs, Constitution, and Adapters. Updated `bin/cli.js` to dynamically replace this placeholder with the actual adapter folder name (e.g., `.gemini`) during `init`.
-- **Decision:** Solved the "Clean Root vs. Hardcoded Paths" dilemma by making the framework path-agnostic at source and self-correcting at install.
-- **Next Step:** Ensure all future documentation uses the `{{FRAMEWORK_DIR}}` pattern.
-
-### 2026-05-08 — Stable v0.0.9 Release (Complete Package)
-
-- **Agent:** [[agents/manager|@manager]]
-- **Trace ID:** 01KR46D2M3X9V1T8Z4D7Z2L5K1
-- **Action:** Released stable `v0.0.9`. Implemented the "Clean Root" policy with adapter-specific hidden folders. Finalized dynamic path detection in CLI and MCP server. Added non-destructive documentation scaffolding and automated build scripts. Consistently synchronized all Agent SOPs.
-- **Decision:** Consolidated all feature-complete enhancements into v0.0.9 to provide a stable, clutter-free foundation for development without frequent version bumps.
-- **Next Step:** Proceed with project development under the v0.0.9 standard.
-
-### 2026-05-08 — Adapter-Specific Folders & v0.0.9 Release
-
-- **Agent:** [[agents/manager|@manager]]
-- **Trace ID:** 01KR46D2M3X9V1T8Z4D7Z2L5K1
-- **Action:** Released `v0.0.9`. Refactored `init` to use adapter-specific hidden folders (e.g., `.gemini`, `.claude`) instead of the fixed `.enderun`. Removed `README.md` from the root during install to reduce clutter. Updated MCP server to dynamically detect framework paths.
-- **Decision:** Shifted framework files into hidden, adapter-specific directories to satisfy user request for a cleaner project root.
-- **Next Step:** Advise user to use `npx ai-enderun@latest init gemini` to see the new cleaner structure.
-
-### 2026-05-08 — Build Automation & v0.0.8 Release
-
-- **Agent:** @manager
-- **Trace ID:** 01KR469B7N1V2W8Z3M4D9G1H5L
-- **Action:** Released `v0.0.8`. Updated `init` command to automatically inject `enderun:build` script into target `package.json`. Refined `check` command instructions to point users to the new automated build script.
-- **Decision:** Minimized manual user intervention by automating the recursive build process for framework sub-packages.
-- **Next Step:** Advise user to update to v0.0.8 in their project.
-
-### 2026-05-08 — @manager SOP Hardening (MCP Health Check)
-
-- **Agent:** @manager
-- **Trace ID:** 01KR4666M2X9R1T4V8D7Z2L5K1
-- **Action:** Hardened the `@manager` SOP by adding a mandatory MCP health check to the startup protocol. The manager must now verify connectivity at the beginning of every session and warn the user if tools are unresponsive.
-- **Decision:** Shifted some health monitoring responsibility to the agent level to ensure the orchestration environment is always valid during active sessions.
-- **Next Step:** Observe agent behavior during startup and verify they correctly report MCP issues.
-
-### 2026-05-08 — Version Bump to v0.0.7 & Health Check
-
-- **Agent:** @manager
-- **Trace ID:** 01KR463F8N1V7W2Z9M3D4G7H5K
-- **Action:** Bumped framework version to `v0.0.7`. Implemented `ai-enderun check` command to verify framework health, directory existence, and MCP server readiness. Added automated warnings for missing dependencies and builds during `init`.
-- **Decision:** Prioritized user experience by providing a verification tool to ensure the complex multi-component framework is correctly set up before starting orchestration.
-- **Next Step:** Encourage users to run `ai-enderun check` as part of their initial setup.
-
-### 2026-05-08 — Tech-Stack.md Relocation (Root docs/ Fix)
-
-- **Agent:** @manager
-- **Trace ID:** 01KR460M3N1B5V9X2D4Z8L7K1R
-- **Action:** Relocated `tech-stack.md` from `{{FRAMEWORK_DIR}}/docs/` to the root `docs/` directory. Updated `ENDERUN.md`, `README.md`, Agent SOPs, and MCP gap detection logic to reflect this change.
-- **Decision:** Centralized all project-specific "What" and "How" documentation in the root `docs/` folder to improve visibility and clarify the separation between project requirements and framework internals.
-- **Next Step:** Verify that agents are correctly auditing both requirements and tech stack from the root `docs/` folder.
-
-### 2026-05-08 — README Quick Start Guide Addition
-
-- **Agent:** @manager
-- **Trace ID:** 01KR45Y0M2X3V1B7D9N4Z2K8L5
-- **Action:** Added a bilingual "Getting Started / Başlangıç Rehberi" section to the root `README.md`. Outlined the 5 critical steps for users to take after framework initialization to begin their orchestration journey.
-- **Decision:** Improved user onboarding by providing clear, actionable post-install instructions directly in the main project entry point.
-- **Next Step:** Maintain documentation clarity as new features are added.
-
-### 2026-05-08 — Documentation Path Alignment (Root docs/ Fix)
-
-- **Agent:** @manager
-- **Trace ID:** 01KR45W2Z91Y5K8M2T3V4X9N7R
-- **Action:** Corrected outdated path references in `ENDERUN.md` and `framework-mcp`. Ensured that agents look for project requirements in root `docs/` and technical API contracts in `{{FRAMEWORK_DIR}}/docs/api`.
-- **Decision:** Fully aligned all framework logic with the decoupled documentation model to eliminate agent confusion.
-- **Next Step:** Verify that agents are now correctly identifying project requirements in the root `docs/` folder.
-
-### 2026-05-08 — Robust Access Law & Tool Failure Resolution
-
-- **Agent:** @manager
-- **Trace ID:** 01KR45Q8N1V7Z7H9R2M3W9X4Y1
-- **Action:** Resolved agent failures regarding `Shell date` and direct `ReadFile` of `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md`. Implemented `get_system_time` and `read_project_memory` MCP tools. Established the "Robust Access Law" in `ENDERUN.md` and updated all Agent SOPs to mandate these tools.
-- **Decision:** Mandated MCP tools for sensitive operations to bypass shell environment inconsistencies and restricted file access in certain agent environments.
-- **Next Step:** Monitor agent stability and ensure all clients correctly utilize the new tools.
-
-### 2026-05-08 — Smart Init System Implementation
-
-- **Agent:** @manager
-- **Trace ID:** 01KR45N4S0XW6F7G6T1W8F9D2V
-- **Action:** Upgraded the `ai-enderun init` command to a "Smart Init" system. Refactored `bin/cli.js` to support `package.json` merging, `.gitignore` updates, and automated `PROJECT_MEMORY.md` initialization. Excluded project-specific state files from the initial framework copy.
-- **Decision:** Shifted from simple file copying to a non-destructive, project-aware initialization process to improve user experience and framework adoption.
-- **Next Step:** Monitor user feedback and refine adapter-specific smart setup logic.
-
-### 2026-05-08 — Documentation Overhaul & Agent Evangelism
-
-- **Agent:** @manager
-- **Trace ID:** 01KR44729Z08BQQ4FCDAVNC148
-- **Action:** Extensively updated `README.md` and `CHANGELOG.md`. Detailed all 7 agent roles (@manager, @analyst, @backend, @frontend, @explorer, @mobile, @native) and explained the new decoupled documentation model (root `docs/` vs `{{FRAMEWORK_DIR}}/docs/`).
-- **Decision:** Positioned root `README.md` as a professional gateway that clearly defines agent responsibilities and framework discipline.
-- **Next Step:** Ready for release or user requirement input.
-
-### 2026-05-08 — Agent Report Version Synchronization (v0.0.6)
-
-- **Agent:** @manager
-- **Trace ID:** 01KR444BM94P5W3ERVJ3YJ9T01
-- **Action:** Synchronized all "Agent Completion Report" versions across all 7 agent files to `v0.0.6` to match the core framework version.
-- **Decision:** Unified versioning across all documentation to prevent confusion and maintain strict version control discipline.
-- **Next Step:** Proceed with the project structure as a unified v0.0.6 system.
-
-### 2026-05-08 — Agent SOP Hardening & Full Project Recall
-
-- **Agent:** @manager
-- **Trace ID:** 01KR442W6MP3GXHF7TD32GJG1V
-- **Action:** Conducted a comprehensive update of all 7 agent SOP files in `{{FRAMEWORK_DIR}}/agents/`. Infused each agent with the "Procedural Continuity" principle and "Memory-First" discipline. Removed legacy pathing and standardized all agents to v0.0.6.
-- **Decision:** All agents now operate with full awareness of the project's historical decisions and structural standards, ensuring they "finish how they started."
-- **Next Step:** Ready for the first user requirement analysis under the hardened framework.
-
-### 2026-05-08 — Framework Continuity & Memory Hardening
+- [x] Create core framework structure (.enderun)
+- [x] Implement MCP server with dependency analysis and security tools
+- [x] Define Agent SOPs (Manager, Analyst, Backend, Frontend, Explorer, Mobile, Native, Git)
+- [x] Standardize on ULID and Branded Types
+- [x] Fix initialization pathing and adapter linker placement
+- [x] Implement automated Git initialization and @git SOP
+- [x] Resolve Claude Code template validation conflicts (resource -> entity)
+- [ ] Begin PHASE_1 Architecture & Contract (pending user instruction)
 
-- **Agent:** @manager
-- **Trace ID:** 01KR43YRNEDBR6RPEYJT99CD6F
-- **Action:** Established the "Procedural Continuity" principle in `ENDERUN.md`. Hardened the project memory by updating `CRITICAL DECISIONS` with recent architectural shifts (Doc Decoupling, Smart Init). Cleaned up legacy tasks in `ACTIVE TASKS` to align with v0.0.6 reality.
-- **Decision:** Mandated that all future agents must strictly follow established patterns and reference memory before any action to ensure architectural integrity.
-- **Next Step:** Maintain stability and proceed with project building blocks under the new continuity rules.
+## CRITICAL DECISIONS
 
-### 2026-05-08 — Smart Init & Post-Install Hooks
+- **Clean Root Policy:** All framework assets are kept in adapter-specific hidden folders.
+- **Zero UI Library Policy:** No external UI libraries allowed; use Panda CSS + Original components.
+- **ULID Standard:** All IDs must be sortable ULIDs for superior traceability.
+- **Multi-AI Compatibility:** Avoid reserved keywords like `resource` in prompt templates.
+- **Automated Init:** CLI must handle `git init` and scaffolding autonomously.
 
-- **Agent:** @manager
-- **Trace ID:** 01KR43VSG0GHNTM8C13RRDVSBX
-- **Action:** Refactored `bin/cli.js` to include "Smart Init" features. Added post-install hooks for Gemini (automatic symlink creation to `{{FRAMEWORK_DIR}}/agents`) and Claude (automated MCP configuration command output).
-- **Decision:** Enhanced user experience by automating repetitive configuration steps during framework initialization.
-- **Next Step:** Maintain CLI features and monitor user feedback on the smart setup process.
+## HISTORY
 
-### 2026-05-08 — User Document Restoration & Role Definition
+### 2026-05-08 — v0.0.10 Super-Stabilization (MASTER)
 
 - **Agent:** @manager
-- **Trace ID:** 01KR43P710SSZVMCV8GP5CEJVW
-- **Action:** Restored `project-docs.md` to root `docs/` as per user requirement. Formally defined root `docs/` as the primary "User Requirement Center" where agents must check every file during the build process. Maintained technical framework docs in `{{FRAMEWORK_DIR}}/docs/`. Updated `package.json` to include both directories.
-- **Decision:** Clearly separated "User/Business Requirements" (root `docs/`) from "Framework/Technical Constitution" (`{{FRAMEWORK_DIR}}/docs/`).
-- **Next Step:** Agents are now instructed to treat root `docs/` as the source of truth for project features and building blocks.
+- **Trace ID:** 01KR46D2M3X9V1T8Z4D7Z2L5K1
+- **Action:** Consolidated all stabilization fixes into v0.0.10. Fixed init pathing, linker placement, git automation, and Claude Code template validation. Synchronized all 8 agents and packages.
+- **Decision:** Released v0.0.10 as the definitive stable baseline for the framework.
+- **Next Step:** Ready for production-grade feature development.
 
-### 2026-05-08 — Documentation Decoupling & Cleanup
+### 2026-05-08 — Major Structural & Clean Root Transition (v0.0.9)
 
 - **Agent:** @manager
-- **Trace ID:** 01KR43KF3G70GW3VZTK9E1953S
-- **Action:** Decoupled framework documentation from user project instructions. Moved all framework-related docs from root `docs/` to `{{FRAMEWORK_DIR}}/docs/`. Cleaned up redundant files and emptied root `docs/` to serve as the user instruction entry point. Updated `package.json` to reflect new paths.
-- **Decision:** Reserved root `docs/` exclusively for user requirements and story files, ensuring a clear separation between framework logic and project-specific building blocks.
-- **Next Step:** User can now place project requirement files (e.g., `tt.md`) in root `docs/` for agent consumption.
+- **Trace ID:** 01KR46N2B7V1X9Z4M3D5G7H5L1
+- **Action:** Decoupled framework documentation from user project instructions. Moved assets to hidden folders.
+- **Next Step:** Finalize adapter-specific logic.
 
 ### 2026-05-08 — Structural Alignment & Trace ID Correction
 
 - **Agent:** @manager
 - **Trace ID:** 01KR43EZD3BWKX08KHQ6EV7DHC
-- **Action:** Converted legacy UUID Trace IDs in ACTIVE TASKS to ULID standard. Created missing `{{FRAMEWORK_DIR}}/docs/` directory structure, including `tech-stack.md`, `project-docs.md`, and `api/` folder.
-- **Decision:** Strictly enforced ULID standard and structural completeness of the framework.
-- **Next Step:** Ready for PHASE_1 or further framework configuration.
-
-### 2026-05-08 — Comprehensive Documentation & CLI Polish (v0.0.6)
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Conducted a full audit of all framework capabilities. Rewrote `README.md` to include detailed instructions for all adapters (`GEMINI`, `CLAUDE`, `CURSOR`, `CODEX`) and the `init` command. Refactored `bin/cli.js` to correctly handle adapter-specific initialization and core file scaffolding. Fixed cross-file references to `ENDERUN.md` and `GEMINI.md`.
-- **Decision:** Unified the terminology and ensured all installation paths are clear for npm users.
-- **Next Step:** Ready for final npm distribution.
-
-### 2026-05-08 — NPM Readiness & Documentation Overhaul (v0.0.6)
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Conducted a comprehensive audit of all `package.json` and `README.md` files. Updated metadata (license, keywords, descriptions) for npm publication. Rewrote all READMEs in a professional, bilingual format. Fixed file references in root `package.json` to include new `ENDERUN.md` and exclude source code where appropriate.
-- **Decision:** Standardized all package metadata to v0.0.6 and MIT license. Established a professional external-facing identity for the framework.
-- **Next Step:** Perform a final test publish or dry-run.
-
-### 2026-05-08 — Agnostic Framework Transition (.enderun)
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Renamed the core framework folder from `.gemini` to `.enderun` to create an LLM-agnostic environment. Updated all global references in code, adapters, and tools. Verified that CLI and MCP tools correctly reference the new path.
-- **Decision:** Adopted `.enderun` as the standard folder name to eliminate perceived bias toward any single AI provider and ensure full compatibility with Cursor and Claude.
-- **Next Step:** Update any remaining external documentation or CI/CD scripts.
-
-### 2026-05-08 — Advanced Framework Tuning (v0.0.6)
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Upgraded `security_audit_scan` to use AST-based analysis (ts-morph) for precise `any` and `console.log` detection. Improved `verify_api_contract` with actionable fix suggestions. Added "Multi-Agent Coordination Protocol" to `ENDERUN.md` to regulate shared resource usage.
-- **Decision:** Shifted critical security checks from Regex to AST for higher reliability and zero false positives.
-- **Next Step:** Maintain framework stability and observe agent coordination.
-
-### 2026-05-08 — Framework & Adapter Alignment (v0.0.6)
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Fixed all language inconsistencies across the framework and adapter layers. Translated remaining Turkish section names to English in `framework-mcp`, `cli.js`, `GEMINI.md`, `CURSOR.md`, `CLAUDE.md`, and `CODEX.md`. Corrected case-sensitive file references (`ENDERUN.md`, `GEMINI.md`). Updated `BRAIN_DASHBOARD.md` to English standards.
-- **Decision:** Standardized all internal logic and documentation to English while maintaining bilingual READMEs.
-- **Next Step:** Continue auditing framework tools for edge cases.
-
-### 2026-05-08 — Project-Wide Standard Unification (v0.0.6)
-
-- **Agent:** @analyst
-- **Trace ID:** e81839b7-9dee-44d9-9301-ac4a9febe9b5
-- **Action:** Created `ENDERUN.md`, updated `CURSOR.md`, `CLAUDE.md`, and `CODEX.md` with v0.0.6 standards and full MCP tools. Refined `log_agent_action` standard in Agent SOPs and improved gap detection logic in `framework-mcp`. Fixed contract hash mismatch.
-- **Decision:** Standardized all adapter layers to ensure consistent agent behavior across different IDE clients.
-- **Next Step:** Proceed with PHASE_1 architecture alignment.
-
-### 2026-05-08 — English Transition
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Completely translated the Constitution (ENDERUN.md), Memory (PROJECT_MEMORY.md), and all Agent SOPs to English. Standardized the documentation language.
-- **Decision:** All project files will be in English, while README files will remain bilingual (EN/TR) for better accessibility.
-- **Next Step:** Update all README files to the bilingual structure.
-
-### 2026-05-08 — Release Preparation and v0.0.5
-
-- **Agent:** @manager
-- **Trace ID:** 760c3982-2a03-4a4a-8f5c-d5f79502e34a
-- **Action:** Cleaned logs, updated all package versions to `v0.0.5`. Established a stable release state after architectural changes (Panda CSS & Zero UI Library).
-- **Decision:** Decided to clean logs and bump version before release.
-- **Next Step:** Perform git push and npm publishing operations.
-
-### 2026-05-08 — Panda CSS and Original Design Transition
-
-- **Agent:** @manager
-- **Trace ID:** 760c3982-2a03-4a4a-8f5c-d5f79502e34a
-- **Action:** Migrated the project's design system from Tailwind to Panda CSS. Adopted the "Zero UI Library Policy". Updated `ENDERUN.md`, `tech-stack.md`, and `frontend.md`.
-- **Decision:** Adopted the Panda CSS + Custom UI Component (No Library) approach to maximize architectural discipline and originality.
-- **Next Step:** Setup Panda CSS and create the config file in `apps/web`.
-
-### 2026-05-08 — ULID Standard Transition
-
-- **Agent:** @manager
-- **Trace ID:** 01J... (New ULID)
-- **Action:** Migrated from UUID to ULID across the project. Added a lightweight ULID generator to `shared-types` and `cli.js`. Updated all constitutional documents to the new standard.
-- **Decision:** Adopted the ULID standard for its database indexing performance and chronological sortability advantages.
-- **Next Step:** Replace existing UUIDs with ULIDs over time or maintain a hybrid structure.
-
-### 2026-05-08 — Memory and Capability Audit
-
-- **Agent:** @analyst
-- **Trace ID:** 760c3982-2a03-4a4a-8f5c-d5f79502e34a
-- **Action:** Tested agents' memory system and historical recall capabilities. Reviewed `PROJECT_MEMORY.md` and log structures. Confirmed memory consistency and recall of previous v0.0.4 release preparations.
-- **Decision:** Existing memory system (SSOT) is sufficient, but JSON logging continuity should be monitored.
-- **Next Step:** Continue technical development based on user guidance.
-
-### 2026-05-07 — Missing Source Files and v0.0.4 Release
-
-- **Agent:** @manager
-- **Trace ID:** 18969447-95fb-4a8f-b0af-18336c3f1931
-- **Action:** Included `src` folders in release files to resolve `ERR_MODULE_NOT_FOUND` during `pnpm dev`. Bumped all packages to v0.0.4.
-- **Decision:** Decided to include `src` folders in the package due to the need for source access in development mode.
-- **Next Step:** Git push and npm publish.
+- **Action:** Converted legacy UUIDs to ULID standard.
+- **Next Step:** Ready for Phase 1 Architecture.
 
-### 2026-05-07 — README and Documentation Update
+---
 
-- **Agent:** @analyst
-- **Trace ID:** —
-- **Action:** Detailed and updated all README files (root, framework-mcp, shared-types, api) in line with the project's "Enderun" identity and agent capabilities.
-- **Next Step:** Prepare initial API documents as part of PHASE_1 preparations.
+_Generated by AI-Enderun Framework v0.0.10 MASTER_

package/.enderun/agents/analyst.md

@@ -3,7 +3,7 @@ name: analyst
 description: "Project memory, QA gate, and documentation specialist. Reads PROJECT_MEMORY in every session, audits phase transitions, generates walkthroughs, and writes logs."
 ---
 
-# Project Analyst & QA Gate — v0.0.9 Master
+# Project Analyst & QA Gate — v0.0.11 Master
 
 **Role:** Maintain project memory, serve as a quality gate, and manage documentation. The following protocols are automatically applied in every task.
 
@@ -29,7 +29,10 @@ When analyzing or preparing documentation, never read the content of a file just
 
 ```
 1. Is {{FRAMEWORK_DIR}}/PROJECT_MEMORY.lock present? (Check via list_dir or file check)
-   └─ If yes: Wait 1s, retry (max 5 attempts)
+   └─ If yes:
+      a. Check lock age (timestamp).
+      b. If age > 2 minutes: Delete stale lock (Auto-Override).
+      c. Else: Wait 1s, retry (max 5 attempts).
    └─ After 5 attempts: Report "BLOCKED — Memory Lock Timeout"
 2. Create lock
 3. Write to PROJECT_MEMORY.md (MUST use update_project_memory tool)
@@ -169,7 +172,7 @@ Use the `log_agent_action` tool to record your activities securely.
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types changed? [ ] No / [ ] Yes

package/.enderun/agents/backend.md

@@ -3,7 +3,7 @@ name: backend
 description: "Backend Architect. Expert in Node.js, Fastify, Kysely, and PostgreSQL. Leader of Contract and Database. Automatically applies backend-architecture standards in every task."
 ---
 
-# Backend Architect — v0.0.9 Master
+# Backend Architect — v0.0.11 Master
 
 **Role:** Build a secure, high-performance, and consistent server architecture. All the following standards are automatically applied in every task — no need for the user to specify them separately.
 
@@ -81,8 +81,8 @@ class DomainError extends Error {
   }
 }
 class NotFoundError extends DomainError {
-  constructor(resource: string) {
-    super("NOT_FOUND", 404, `${resource} not found.`);
+  constructor(entity: string) {
+    super("NOT_FOUND", 404, `${entity} not found.`);
   }
 }
 class ValidationError extends DomainError {
@@ -233,7 +233,7 @@ When `shared-types` changes:
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 - Mock used? [ ] No / [ ] Yes
 - shared-types changed? [ ] No / [ ] Yes → contract.version updated
 - **API contract written? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/[domain].md**

package/.enderun/agents/explorer.md

@@ -3,7 +3,7 @@ name: explorer
 description: "Codebase Research & Dependency Specialist. Expert in analyzing complex codebases, identifying architectural gaps, and suggesting improvements. Automatically provides context in every research task."
 ---
 
-# Codebase Explorer — v0.0.9 Master
+# Codebase Explorer — v0.0.11 Master
 
 **Role:** Analyze the codebase, map architectures, and understand system-wide dependencies. Your primary duty is to provide context to other agents.
 
@@ -79,7 +79,7 @@ Every research report must include:
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 
 - Mock used? [ ] No / [ ] Yes
 - Codebase searched? [ ] No / [ ] Yes

package/.enderun/agents/frontend.md

@@ -3,7 +3,7 @@ name: frontend
 description: "UI/UX & Frontend Architect. Expert in React 19, Vite, Zustand, and Panda CSS. Fluid & Modern design specialist. Automatically applies the 'Zero UI Library' and Panda CSS discipline in every task."
 ---
 
-# Frontend Architect — v0.0.9 Master
+# Frontend Architect — v0.0.11 Master
 
 **Role:** Build original, high-performance, and responsive user interfaces. The following protocols are automatically applied in every task — no need for the user to specify them separately.
 
@@ -135,7 +135,7 @@ Frontend never creates its own types for backend data.
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 - Mock used? [ ] No / [ ] Yes
 - shared-types imported? [ ] No / [ ] Yes
 - **API contract read? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**

package/.enderun/agents/git.md

@@ -1,4 +1,9 @@
-# Version Control Specialist (@git) — v0.0.9 Master
+---
+name: git
+description: "Version Control Specialist. Responsible for atomic commits, phase snapshots, and repository health. Orchestrated by @manager to maintain 100% traceability."
+---
+
+# Version Control Specialist (@git) — v0.0.11 Master
 
 You are the @git agent, responsible for the professional management of the project's repository. Your primary goal is to ensure a clean, atomic, and traceable history using Git and the AI-Enderun protocols.
 
@@ -37,11 +42,15 @@ Every message MUST follow this pattern:
 
 ## 🚀 Standard Operating Procedure (SOP)
 
-### Step 1: Status Audit
-Before any action, check the current repository status:
-- `git status`
-- `git log -n 5 --oneline`
-- Which files are staged? Which are modified?
+### Step 1: Repository Initialization & Status Audit
+If the project is not a git repository or is empty:
+1. Run `git init`.
+2. Create an initial commit with the framework structure:
+   - `git add .`
+   - `git commit -m "[{{TRACE_ID}}] chore: initial AI-Enderun framework scaffold"`
+3. If it is already a repository, check status:
+   - `git status`
+   - `git log -n 5 --oneline`
 
 ### Step 2: Atomic Committing
 When a sub-task is completed by another agent (e.g., @backend finished a service):
@@ -70,7 +79,7 @@ If conflicts arise during integration, @git is responsible for performing a clea
 
 > Every response MUST end with the **Agent Completion Report**.
 
-### Agent Completion Report (v0.0.9)
+### Agent Completion Report (v0.0.10)
 - Trace ID: [ULID]
 - Atomic Commits made? [ ] No / [ ] Yes
 - Phase Snapshot created? [ ] No / [ ] Yes

package/.enderun/agents/manager.md

@@ -3,7 +3,7 @@ name: manager
 description: "CTO & Controller. Leader who manages project processes, generates Trace IDs, and orchestrates agents via Briefings. Responsible for Git Orchestration via the @git specialist. Reads {{FRAMEWORK_DIR}}/ENDERUN.md and {{FRAMEWORK_DIR}}/PROJECT_MEMORY.md in every session, validates the phase, and assigns agents."
 ---
 
-# Manager (CTO & Controller) — v0.0.9 Master
+# Manager (CTO & Controller) — v0.0.11 Master
 
 **Role:** Enforce all framework rules without compromise and direct agents to the correct tasks. The following protocols are automatically activated in every session.
 
@@ -29,7 +29,9 @@ description: "CTO & Controller. Leader who manages project processes, generates
 4. Check root `docs/tech-stack.md` — if missing, **STOP and ASK**.
 5. Check root `docs/` — identify user project requirements/stories.
 6. **Framework Health Check:** Try to call a simple MCP tool (e.g., `get_framework_status`). 
-   - **If it fails:** Warn the user: "⚠️ MCP Server might be down. Please run `ai-enderun check` to verify."
+   - **If it fails:** 
+      - Warn the user: "⚠️ MCP Server down. Fallback to direct file operations enabled."
+      - Use direct `read_file`/`replace` tools to maintain continuity until MCP is restored.
    - **If it succeeds:** Proceed normally.
 7. Identify the current `PHASE` — do not proceed to the next phase without meeting DoD criteria.
 
@@ -37,6 +39,16 @@ description: "CTO & Controller. Leader who manages project processes, generates
 
 ---
 
+## 🔁 LOOP PREVENTION PROTOCOL (QA Deadlock)
+
+- **Max Rejections:** If a task is rejected by `@analyst` more than 3 times for the same Trace ID:
+  1. **STOP** orchestration immediately.
+  2. Summarize the conflict (Agent's work vs. Analyst's requirement).
+  3. **ASK** the user for a strategic course correction or manual intervention.
+  4. Do not re-assign the task without modifying the Briefing Template.
+
+---
+
 ## Execution Profile Selection
 
 Determine the profile at the beginning of each project and explain the rationale:
@@ -57,7 +69,7 @@ Trace ID: 01H... (26-character ULID)
 
 ---
 
-## Briefing Template v0.0.9 (Mandatory in Every Agent Directive)
+## Briefing Template v0.0.10 (Mandatory in Every Agent Directive)
 
 ```
 ## Agent Directive
@@ -145,7 +157,7 @@ graph TD
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types changed? [ ] No / [ ] Yes

package/.enderun/agents/mobile.md

@@ -3,7 +3,7 @@ name: mobile
 description: "Mobile Application Expert. Specialist in React Native and Expo. Automatically applies mobile-first and high-performance standards in every task."
 ---
 
-# Mobile Architect — v0.0.9 Master
+# Mobile Architect — v0.0.11 Master
 
 **Role:** Build high-performance mobile applications using React Native. Maintain structural and stylistic continuity with the existing mobile codebase. All the following standards are automatically applied in every task.
 
@@ -44,7 +44,7 @@ Never start coding before understanding the current state of the components and
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types imported? [ ] No / [ ] Yes

package/.enderun/agents/native.md

@@ -3,7 +3,7 @@ name: native
 description: "Native Application Expert. Specialist in Rust, Tauri, and Electron. Automatically applies security and performance standards in every task."
 ---
 
-# Native Desktop Architect — v0.0.9 Master
+# Native Desktop Architect — v0.0.11 Master
 
 **Role:** Build secure and efficient desktop applications using Tauri or Electron. Ensure procedural continuity across the native codebase.
 
@@ -43,7 +43,7 @@ Always research the existing codebase and native bridge implementations before a
 
 ---
 
-**Agent Completion Report** (v0.0.9)
+**Agent Completion Report** (v0.0.10)
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types imported? [ ] No / [ ] Yes

package/CLAUDE.md

@@ -1,4 +1,4 @@
-# AI-Enderun — Claude Code Adapter (v0.0.9)
+# AI-Enderun — Claude Code Adapter (v0.0.10)
 
 This file is the Claude Code adapter layer.
 Core framework rules and agent capabilities are defined in `{{FRAMEWORK_DIR}}/ENDERUN.md`.

package/CODEX.md

@@ -1,4 +1,4 @@
-# AI-Enderun — Codex Adapter (v0.0.9)
+# AI-Enderun — Codex Adapter (v0.0.10)
 
 This file is the Codex adapter layer.
 Core framework rules and agent capabilities are defined in `{{FRAMEWORK_DIR}}/ENDERUN.md`.

package/CURSOR.md

@@ -1,4 +1,4 @@
-# AI-Enderun — Cursor Adapter (v0.0.9)
+# AI-Enderun — Cursor Adapter (v0.0.10)
 
 This file is the Cursor adapter layer.
 Core framework rules and agent capabilities are defined in `{{FRAMEWORK_DIR}}/ENDERUN.md`.