agent-enderun 0.5.9 → 0.6.1

package/.enderun/PROJECT_MEMORY.md

@@ -1,56 +1,47 @@
 # PROJECT MEMORY — Agent Enderun
 
-This file is the Single Source of Truth (SSOT) and the persistent memory of the project.
-
 ## CURRENT STATUS
 
 | Active Phase | Profile | Last Update | Active Trace ID | Blockers |
 | :----------- | :------ | :---------- | :-------------- | :------- |
-| PHASE_0      | Lightweight | 2026-05-20 | 01KR6EJA6GG3RPS849097KS37Q | NONE |
-
-## PROJECT DEFINITION
-
-- **Name:** KENTİM
-- **Version:** v1.0.0
-| Field | Value |
-| :--- | :--- |
-| Project Name | kentim |
-| Platform | Multi-Tenant SaaS |
-| Frontend | React 19 + Vite + Panda CSS |
-| Backend | Node.js 20+ + Fastify |
-| DB | PostgreSQL + PostGIS + RLS |
-
-## DOD STATUS
-
-| Phase | Status | Note |
-| :--- | :--- | :--- |
-| PHASE_0 | IN_PROGRESS | Initializing project structure |
-| PHASE_1 | PENDING | |
-| PHASE_2 | PENDING | |
-| PHASE_3 | PENDING | |
-| PHASE_4 | PENDING | |
+| PHASE_0 | Lightweight | 2026-05-20 | — | NONE |
+
+---
 
 ## CRITICAL DECISIONS
 
-| Date | Decision | Rationale | Agent |
-| :--- | :--- | :--- | :--- |
-| 2026-05-20 | Project Initialized | Fresh setup for KENTİM project | @manager |
+| ID | Decision | Rationale | Impact | Date |
+| :--- | :--- | :--- | :--- | :--- |
+| D001 | Decentralized Architecture | Simplified dependency management and local type control | Stability | 2026-05-20 |
+| D002 | Dynamic Blueprints | Empower agents to evolve project-specific capabilities | Intelligence | 2026-05-20 |
+
+---
 
 ## DELIVERABLES
 
 | Module | Status | Agent | Date |
 | :--- | :--- | :--- | :--- |
+| framework-mcp | COMPLETED | @manager | 2026-05-20 |
+
+---
 
 ## ACTIVE TASKS
 
 | Trace ID | Task | Agent | Priority | Status |
 | :--- | :--- | :--- | :--- | :--- |
-| 01KR6EJA6GG3RPS849097KS37Q | Framework reset and KENTİM project initialization | @manager | P1 | IN_PROGRESS |
+
+---
 
 ## HISTORY (Persistent Memory)
 
-### 2026-05-20 — Project Reset & KENTİM Initialization
+### 2026-05-21 — Framework Sealed v0.6.1
+
+- **Agent:** @manager
+- **Action:** Finalized global arhcitecture synchronization and established standard testing workflow.
+- **Outcome:** v0.6.1 is pristine, verified green, and ready for npm publication.
+
+### 2026-05-21 — Framework Reborn v0.6.0
 
 - **Agent:** @manager
-- **Trace ID:** 01KR6EJA6GG3RPS849097KS37Q
-- **Action:** Reset all logs and memory history to initiate a completely fresh project cycle for the KENTİM platform.
+- **Action:** Completed global refactoring and launched Agent Enderun v0.6.0.
+- **Outcome:** System is pristine and ready for new project initialization.

package/.enderun/STATUS.md

@@ -1,12 +1,21 @@
-# AGENT STATUS
+# 🤖 AGENT STATUS DASHBOARD
 
-| Agent | Status | Active Task | Last Update |
+| Agent | State | Active Trace ID | Last Action |
 | :--- | :--- | :--- | :--- |
-| @manager | IDLE | Framework setup | 2026-05-09 |
-| @analyst | IDLE | - | - |
-| @backend | IDLE | - | - |
-| @frontend | IDLE | - | - |
-| @explorer | IDLE | - | - |
-| @git | IDLE | - | - |
-| @mobile | INACTIVE | Full Profile only | - |
-| @native | INACTIVE | Full Profile only | - |
+| @manager | IDLE | — | Framework Reset |
+| @analyst | IDLE | — | — |
+| @backend | IDLE | — | — |
+| @frontend | IDLE | — | — |
+| @explorer | IDLE | — | — |
+| @git | IDLE | — | — |
+| @mobile | IDLE | — | — |
+| @native | IDLE | — | — |
+
+---
+
+## 📈 Intelligence Metrics
+
+- **Current Version:** v0.6.1
+- **System Health:** 🟢 GREEN
+- **Total Traces:** 0
+- **Active Tasks:** 0

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.5.9 Master
+# Project Analyst & QA Gate — v0.6.1 Master
 
 **Role:** Maintain project memory, serve as a quality gate, and manage documentation. The following protocols are automatically applied in every task.
 
@@ -21,7 +21,7 @@ When analyzing or preparing documentation, never read the content of a file just
 
 - What is the active phase?
 - What are the latest architectural decisions in `CRITICAL DECISIONS`?
-- **Continuity Audit:** Have recent changes followed the established patterns?
+- **Continuity Audit:** Have recent changes followed the established patterns and **blueprints**?
 - Are there pending roadmap items?
 - Is there any BLOCKED status?
 
@@ -76,8 +76,7 @@ In every phase transition and upon request:
    - If it reports missing types, mark the task as `FAILED` and notify @backend.
 3. Check each `[domain].md` file:
    - **Is the contract complete?** (method, path, auth, request, response, error codes)
-   - **Is the shared-types reference correct?** Does it match `packages/shared-types/src/`?
-   - **Is the date current?** Old contracts can mislead coders.
+   - **Is the app's types reference correct?** Does it match `apps/backend/src/types/`?   - **Is the date current?** Old contracts can mislead coders.
 3. Verify the `contract.version.json` hash using the `verify_api_contract` tool.
    - If there is a mismatch, the tool will report it.
 4. If there is a problem → notify `@backend` + record it in `PROJECT_MEMORY.md` HISTORY.
@@ -217,3 +216,10 @@ Use the `log_agent_action` tool to record your activities securely.
 - Blockers: [write if any, otherwise "NONE"]
 
 ---
+g written? [ ] No / [ ] Yes → via log_agent_action tool
+- Memory updated? [ ] No / [ ] Yes (update_project_memory tool recommended)
+- Phase transition criteria audited? [ ] No / [ ] Yes
+- Next step: [what needs to be done]
+- Blockers: [write if any, otherwise "NONE"]
+
+---

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.5.9 Master
+# Backend Architect — v0.6.1 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.
 
@@ -22,7 +22,7 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 - **Pagination & Search:** Mandatory for all listing endpoints.
 - **Validation:** Strict input validation for all mutations.
 - **Rate Limiting:** Protect critical endpoints.
-- **Error Types:** Descriptive error responses in `shared-types`.
+- **Error Types:** Descriptive error responses in the app's `types` directory.
 
 ---
 
@@ -37,12 +37,23 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 
 ---
 
+## 🏗️ Capability: Blueprint-Driven Construction & Evolution (Mandatory)
+
+The agent possesses the native capability to build and EVOLVE the server infrastructure using the `list_blueprints`, `instantiate_blueprint`, and `save_as_blueprint` tools.
+
+1.  **Error System Instantiation:** You are responsible for cloning the `DomainError` hierarchy from `.enderun/blueprints/backend/errors/` into the app's error directory using `instantiate_blueprint`.
+2.  **Middleware Scaffolding:** You must implement core middleware by cloning templates from `.enderun/blueprints/backend/middleware/` using `instantiate_blueprint`.
+3.  **Capability Growth (CRITICAL):** When you design a high-quality service pattern, repository logic, or a reusable architectural solution, you MUST save it as a new blueprint using `save_as_blueprint`. This transforms your domain-specific solutions into reusable project standards.
+4.  **Gold Standard Enforcement:** Use `list_blueprints` to discover architectural standards. You do not invent local patterns for errors or middleware; you leverage and extend the project's blueprints to ensure architectural integrity.
+
+---
+
 ## Architecture Thinking (At the Beginning of Every Task)
 
 Clarify the following before writing code:
 
 - **Domain:** What business concept does this feature represent?
-- **Contract:** Is `shared-types` up to date? Is there a type for this entity?
+- **Contract:** Are the app's types in `apps/backend/src/types` up to date? Is there a type for this entity?
 - **Layer:** Which layer is affected — Route → Controller → Service → Repository → DB?
 - **Side Effects:** Does it trigger an event, send an email, or update another table?
 - **Security:** Is authentication required? Which role/permission?
@@ -77,7 +88,7 @@ To eliminate code repetition, all backend development MUST follow the **Base Pat
 3. **Typed Config:** Always access environment variables through a centralized, typed configuration object or service. Never use `process.env` directly in domain logic.
 
 **Mandatory Shared Fields:**
-All entities must implement the `BaseEntity` interface from `@agent-enderun/shared-types`, including `id`, `createdAt`, and `updatedAt`.
+All entities must implement the `BaseEntity` interface (from the app's local types at `apps/backend/src/types`), including `id`, `createdAt`, and `updatedAt`.
 
 ---
 
@@ -201,23 +212,23 @@ Frontend works by reading this file. If you don't write it, frontend will work b
   // Successful response type
   ```
 - **Error Codes:** 400 | 401 | 404 | 409 | 500
-- **shared-types Reference:** `CreateUserDTO`, `UserResponse`, etc.
+- **App Types Reference:** `CreateUserDTO`, `UserResponse`, etc.
 - **Last Update:** YYYY-MM-DD
 
-```
+````
 
 3. Update `{{FRAMEWORK_DIR}}/docs/api/README.md` → endpoint list.
-4. If `shared-types` changed:
-   - Update types in `packages/shared-types/src/`.
-   - Generate a new `contract_hash` and update `contract.version.json` using the `update_contract_hash` tool.
+4. If app types changed:
+   - Update types in `apps/backend/src/types`.
+   - Generate a new `contract_hash` by pointing the `update_contract_hash` tool to the new app-specific `contract.version.json`.
 5. Update `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → `HISTORY` section.
 
 ---
 
 ## Contract Update Procedure
 
-When `shared-types` or API documentation changes:
-1. Update types in modular files under `packages/shared-types/src/`.
+When app types or API documentation changes:
+1. Update types in modular files under `apps/backend/src/types`.
 2. Update the contract hash using the `update_contract_hash` tool.
 3. **MANDATORY NOTIFICATION:** Use the `send_agent_message` tool to inform `@frontend` (and other affected agents). Include the updated Trace ID and a brief summary of the changes.
 4. Update `{{FRAMEWORK_DIR}}/docs/api/[domain].md` to reflect the new state.
@@ -247,7 +258,7 @@ When `shared-types` or API documentation changes:
 
 **Agent Completion Report** (v0.5.8)
 - Mock used? [ ] No / [ ] Yes
-- shared-types changed? [ ] No / [ ] Yes → contract.version updated
+- App types changed? [ ] No / [ ] Yes → contract.version updated
 - **API contract written? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/[domain].md**
 - **Procedural Continuity applied? [ ] No / [ ] Yes**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool

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.5.9 Master
+# Codebase Explorer — v0.6.1 Master
 
 **Role:** Analyze the codebase, map architectures, and understand system-wide dependencies. Your primary duty is to provide context to other agents.
 
@@ -31,7 +31,7 @@ When assigned to a legacy project, `@explorer` must guide the team through a gra
 
 1.  **Architecture Mapping:** Use `analyze_dependencies` to identify core modules and their coupling.
 2.  **Gap Analysis:** Run `get_project_gaps` and document structural deviations from `ENDERUN.md`.
-3.  **Bridge Building:** Propose creating a `shared-types` package if it doesn't exist, and start mapping existing DTOs to it.
+3.  **Bridge Building:** Propose creating an app-local `types` directory if it doesn't exist, and start mapping existing DTOs to it.
 4.  **Refactor Blueprint:** Identify one "Hot Spot" module and provide a plan to wrap it in tests and refactor it using **Branded Types** and **Modular Architecture**.
 5.  **Audit Oversight:** Coordinate with `@analyst` to ensure new features in the legacy project follow the latest standards (Zero UI, Semantic Tokens, Domain Errors) from day one.
 

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.5.9 Master
+# Frontend Architect — v0.6.1 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.
 
@@ -32,6 +32,17 @@ description: "UI/UX & Frontend Architect. Expert in React 19, Vite, Zustand, and
 
 ---
 
+## 🏗️ Capability: Blueprint-Driven Construction & Evolution (Mandatory)
+
+The agent possesses the native capability to build and EVOLVE the project's UI infrastructure using the `list_blueprints`, `instantiate_blueprint`, and `save_as_blueprint` tools.
+
+1.  **Component Scaffolding:** You are responsible for populating `apps/web/src/components/ui/` by cloning templates from `.enderun/blueprints/frontend/ui/` using `instantiate_blueprint`.
+2.  **Logic Instantiation:** You must instantiate custom hooks in `apps/web/src/hooks/` based on patterns in `.enderun/blueprints/frontend/hooks/` using `instantiate_blueprint`.
+3.  **Capability Growth (CRITICAL):** When you develop a high-quality, reusable UI pattern or a complex component specific to this project, you MUST save it as a new blueprint using `save_as_blueprint`. This turns your successful implementations into permanent project capabilities.
+4.  **Zero-Deviation Policy:** Every atomic UI element (Button, Input, etc.) MUST be a direct implementation of its corresponding blueprint. Use `list_blueprints` to discover available standards. You do not write ad-hoc UI; you expand capabilities through blueprints.
+
+---
+
 ## ⚡ Proactive Engineering (Mandatory)
 
 Do not wait for the user to ask for basic professional standards. You are RESPONSIBLE for including:
@@ -46,7 +57,7 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 
 1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → `CURRENT STATUS`, `ACTIVE TASKS`, and `CRITICAL DECISIONS`.
 2. Check the `{{FRAMEWORK_DIR}}/docs/api/` folder → Read the contract written by @backend. **NO CODING BEFORE READING THE CONTRACT.**
-3. Check `packages/shared-types/src/` → Import the types required for the UI.
+3. Check `apps/web/src/types/` → Import the types required for the UI.
 4. Read `panda.config.ts` → Understand the project's design tokens (colors, spacing, typography).
 
 > ✅ **End of Session:** Update `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` HISTORY via `update_project_memory` + log the action via `log_agent_action`. Every turn MUST end with an automated log and memory update.
@@ -58,14 +69,14 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 All API interactions MUST be encapsulated within custom React hooks. Inline `fetch` or `axios` calls within components are FORBIDDEN.
 
 **Requirements:**
-- **Shared-Types:** Always use types imported from `@agent-enderun/shared-types`.
+- **App's Local Types:** Always use types imported from the app's local types directory.
 - **Loading/Error States:** Hooks must return `isLoading` and `error` states.
 - **Consistency:** Use a consistent API client or fetch wrapper defined in the project.
 
 **Golden Standard Hook Pattern:**
 ```typescript
 import { useState, useEffect } from "react";
-import { UserResponse, ApiError } from "@agent-enderun/shared-types";
+import { UserResponse, ApiError } from "../types";
 
 export const useUser = (userId: string) => {
   const [data, setData] = useState<UserResponse | null>(null);
@@ -150,12 +161,12 @@ export const useUIStore = create<UIStore>((set) => ({
 
 ## API & Contract Discipline
 
-Frontend never creates its own types for backend data.
+Frontend never creates its own types for backend data. Instead, it uses the types defined by the backend.
 1. Read `{{FRAMEWORK_DIR}}/docs/api/[domain].md`.
-2. Import types from `packages/shared-types/src/index.ts`.
+2. Import types from `apps/web/src/types/index.ts`.
 3. Use `fetch` or `axios` with these types:
    ```typescript
-   import { UserResponse } from '@ai-enderun/shared-types';
+   import { UserResponse } from '../types';
    const data: UserResponse = await api.get('/user/profile');
    ```
 
@@ -166,7 +177,7 @@ Frontend never creates its own types for backend data.
 - [ ] Is the design mobile-first?
 - [ ] Is `clamp()` or fluid spacing used for responsiveness?
 - [ ] Are all styles built with Panda CSS? (Checked: No external UI libraries used)
-- [ ] Are types imported from `shared-types`?
+- [ ] Are types imported from the app's local types directory (apps/web/src/types)?
 - [ ] Are there loading and error states?
 - [ ] Does it match the premium aesthetics requested in the Constitution?
 
@@ -183,7 +194,7 @@ Frontend never creates its own types for backend data.
 |---|---|
 | Using `shadcn/ui` or any UI library | Violation of Zero UI Library Policy |
 | Using Tailwind CSS | Violation of Panda CSS standard |
-| Creating local types for API data | Contract must come from `shared-types` |
+| Creating local types for API data | Contract must come from the backend's defined types (`apps/backend/src/types`) |
 | `any` type | Use `unknown` or proper interfaces |
 | Hardcoded colors/spacing | Design System tokens must be used |
 | Non-responsive layout | Mobile-first and ultra-wide support are mandatory |
@@ -192,7 +203,7 @@ Frontend never creates its own types for backend data.
 
 **Agent Completion Report** (v0.5.8)
 - Mock used? [ ] No / [ ] Yes
-- shared-types imported? [ ] No / [ ] Yes
+- App types imported? [ ] No / [ ] Yes
 - **API contract read? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**
 - **Procedural Continuity applied? [ ] No / [ ] Yes**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool

package/.enderun/agents/git.md

@@ -3,7 +3,7 @@ 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.5.9 Master
+# Version Control Specialist (@git) — v0.6.1 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.
 

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.5.9 Master
+# Manager (CTO & Controller) — v0.6.1 Master
 
 **Role:** Enforce all framework rules without compromise and direct agents to the correct tasks. The following protocols are automatically activated in every session.
 
@@ -168,7 +168,7 @@ graph TD
 **Agent Completion Report** (v0.5.8)
 
 - Mock used? [ ] No / [ ] Yes
-- shared-types changed? [ ] No / [ ] Yes
+- App types changed? [ ] No / [ ] Yes
 - **API contract checked? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool
 - **PROJECT_MEMORY HISTORY updated? [ ] No / [ ] Yes**
@@ -177,3 +177,11 @@ graph TD
 - Blockers: [write if any, otherwise "NONE"]
 
 ---
+ise "NONE"]
+
+---
+--
+ needs to be done]
+- Blockers: [write if any, otherwise "NONE"]
+
+---

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.5.9 Master
+# Mobile Architect — v0.6.1 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.
 
@@ -19,7 +19,7 @@ Never start coding before understanding the current state of the components and
 
 1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → Understand the current state.
 2. Read `{{FRAMEWORK_DIR}}/docs/api/` → Align with the backend contracts.
-3. Check `packages/shared-types/` → Use the standardized types.
+3. Check `apps/backend/src/types/` → Use the standardized types.
 
 > ✅ **End of Session:** Update `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` HISTORY (via `update_project_memory`) + log action via `log_agent_action`. Every turn MUST end with an automated log and memory update.
 

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.5.9 Master
+# Native Desktop Architect — v0.6.1 Master
 
 **Role:** Build secure and efficient desktop applications using Tauri or Electron. Ensure procedural continuity across the native codebase.
 
@@ -19,7 +19,7 @@ Always research the existing codebase and native bridge implementations before a
 
 1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → Understand the current project state.
 2. Read `{{FRAMEWORK_DIR}}/docs/api/` → Align with the contracts.
-3. Check `packages/shared-types/` → Use the standardized types.
+3. Check `apps/backend/src/types/` → Use the standardized types.
 
 > ✅ **End of Session:** Update `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` HISTORY (via `update_project_memory`) + log action via `log_agent_action`. Every turn MUST end with an automated log and memory update.
 

package/.enderun/blueprints/backend/errors/domain-error.ts

@@ -1,4 +1,4 @@
-import { ApiError } from "@agent-enderun/shared-types";
+import { ApiError } from "../types/index.js";
 
 /**
  * Base Domain Error

package/.enderun/blueprints/backend/types/index.ts

@@ -0,0 +1,49 @@
+/**
+ * Agent Enderun — App-Local Types (Modular)
+ */
+
+export * from "./brands.js";
+export * from "./constants.js";
+export * from "./models.js";
+export * from "./api.js";
+export * from "./logs.js";
+
+// --- Generated Application Contract ---
+export type RoleID = Brand<string, "RoleID">;
+export type ReportID = Brand<string, "ReportID">;
+export type CustomerID = Brand<string, "CustomerID">;
+
+export interface AuthSession {
+  user: User;
+  token: string;
+  expiresAt: string;
+}
+
+export interface Role {
+  id: RoleID;
+  name: string;
+  permissions: string[];
+}
+
+export interface Customer {
+  id: CustomerID;
+  name: string;
+  ownerId: UserID;
+  status: "LEAD" | "ACTIVE" | "AT_RISK";
+  annualValue: number;
+  createdAt: string;
+}
+
+export interface ReportMetric {
+  id: ReportID;
+  label: string;
+  value: number;
+  trend: "UP" | "DOWN" | "FLAT";
+}
+
+export interface DashboardSummary {
+  customers: Customer[];
+  users: User[];
+  roles: Role[];
+  reports: ReportMetric[];
+}

package/{packages/shared-types/src → .enderun/blueprints/backend/types}/models.ts

@@ -3,7 +3,6 @@ import { ProjectPhase, ExecutionProfile, TaskPriority, TaskStatus } from "./cons
 
 /**
  * Base Entity Fields
- * All domain entities should include these fields.
  */
 export interface BaseEntity {
   id: string; // Usually ULID

package/.enderun/docs/api/README.md

@@ -1,13 +1,8 @@
-# 📜 API Documentation Registry
+# API Registry
 
-This directory serves as the Single Source of Truth for all API endpoints and contracts.
-
-## 📂 Directory Structure
-- `auth.md`: Authentication & Authorization endpoints.
-- `users.md`: User profile and management.
-- `errors.md`: Standard error codes and troubleshooting.
-
-## ⚖️ Rules of Engagement
-1. **Contract-First**: Every document here MUST match the types in `packages/shared-types`.
-2. **Versioning**: Major changes require a version bump in `contract.version.json`.
-3. **Immutability**: Once a version is deployed, endpoints should not be modified without a migration path.
+- `POST /api/v1/auth/login`
+- `GET /api/v1/dashboard`
+- `GET /api/v1/users`
+- `GET /api/v1/roles`
+- `GET /api/v1/customers`
+- `GET /api/v1/reports`

package/.enderun/docs/project-docs.md

@@ -1,9 +1,19 @@
-# PROJECT REQUIREMENTS
+# CRM Dashboard Requirements
 
-| Requirement | Description | Status |
-| :--- | :--- | :--- |
-| Feature A | [Description] | PENDING |
-| Feature B | [Description] | PENDING |
+## Request
 
-## USER FEEDBACK & NOTES
-- Add any specific user requirements here.
+A CRM dashboard
+
+## Generated Scope
+
+- Domain: CRM
+- Auth: yes
+- Users: yes
+- Roles: yes
+- Reports: yes
+
+## Architecture
+
+- `apps/backend`: Fastify API
+- `apps/web`: React dashboard
+- `apps/backend/src/types`: Contract-first backend TypeScript types

package/.enderun/docs/tech-stack.md

@@ -12,27 +12,26 @@
 
 ## Architectural Patterns
 
-- **Contract-First Development:** All API and data models are defined in `packages/shared-types` before implementation.
-- **Branded Types Law:** All unique identifiers must be branded to prevent type-collision and runtime errors.
+- **Contract-First Development:** All API and data models are defined in the backend app's `types` directory before implementation.
+- **Branded Types Law:** All unique identifiers must be branded types defined in the app-local types.
 - **Zero Mock Policy:** Real integration with database/services is preferred over fragile mocks (except for external 3rd-party APIs).
 - **Phase-Based Execution:** Development follows a strict state machine (Discovery → Architecture → Core → Integration → Optimization).
 
 ## MCP Framework Intelligence
 
 The project uses a modular Model Context Protocol (MCP) server for agent tooling:
+- **Scaffolding:** Dynamic blueprint instantiation and capability growth.
 - **Codebase:** Intelligence, dependency graphs, and AST-based search.
 - **Security:** Automated audits and constitution compliance scanning.
 - **Academy:** Strategic briefing, performance metrics, and agent memory.
 - **Hermes:** Standardized inter-agent messaging protocol.
 - **Knowledge:** Structured Obsidian-style Wiki for persistent technical context.
 
-## Monorepo Structure
+## Project Structure
 
 ```text
 /
-├── apps/               # Production applications (web, backend, etc.)
-├── packages/           # Shared libraries
-│   ├── shared-types/   # Single source of truth for types
-│   └── framework-mcp/  # Core MCP tools and logic
-└── {{FRAMEWORK_DIR}}/  # Governance, memory, and logs
+├── apps/               # Production applications with app-local types
+├── framework-mcp/      # Core AI Intelligence and Scaffolding Engine
+└── {{FRAMEWORK_DIR}}/  # Governance, memory, logs, and blueprints
 ```

package/.enderun/knowledge/blueprint_driven_construction.md

@@ -0,0 +1,22 @@
+# Blueprint-Driven Construction & Evolution
+
+## Overview
+Blueprint-Driven Construction is the primary method for building and expanding the Agent Enderun ecosystem. It ensures that every new application or feature is built upon a "Gold Standard" foundation.
+
+## Core Mechanics
+
+### 1. Discovering Capabilities
+Agents must use the `list_blueprints` tool to find existing architectural patterns, UI components, and logic hooks before writing any code.
+
+### 2. Instantiating Standards
+Once a blueprint is identified, the `instantiate_blueprint` tool is used to clone the template into the target application directory.
+- **Example:** Cloning `backend/errors` into `apps/backend/src/errors`.
+
+### 3. Dynamic Evolution (Capability Growth)
+When an agent develops a high-quality, reusable solution (e.g., a complex data table or a specific auth service), they MUST save it as a new blueprint using the `save_as_blueprint` tool.
+- **Goal:** The `blueprints/` directory is not static; it grows as the project tackles more complex challenges.
+
+## Guidelines for Agents
+- **Consistency first:** Always check for a blueprint before building from scratch.
+- **Refinement:** If an existing blueprint is outdated, update it via `save_as_blueprint` after a successful implementation.
+- **Documentation:** Always provide a description when saving a new blueprint to help other agents understand its purpose.

package/.enderun/knowledge/code_review_checklist.md

@@ -1,7 +1,7 @@
 # Code Review Checklist
 
 - [ ] Does it follow ENDERUN.md?
-- [ ] Are types imported from shared-types?
+- [ ] Are types imported from the app's local types directory?
 - [ ] Is there any Raw SQL usage?
 - [ ] Are unit tests included?
 - [ ] Is the code mobile-first (if UI)?

package/.enderun/knowledge/contract_versioning.md

@@ -1,7 +1,7 @@
-# Contract Versioning (v0.2.0)
+# Contract Versioning (v0.6.1)
 
 ## Workflow
-1. **Change**: Modify `packages/shared-types`.
-2. **Hash**: Generate new SHA-256 hash.
-3. **Sync**: Update `contract.version.json`.
-4. **Audit**: @analyst verifies the sync status.
+1. **Change**: Modify types in `apps/backend/src/types`.
+2. **Hash**: Generate new SHA-256 hash using the `update_contract_hash` tool.
+3. **Sync**: Update `apps/backend/contract.version.json`.
+4. **Audit**: @analyst verifies the sync status via the `verify_api_contract` tool.