agent-enderun 0.8.7 → 0.8.8

package/.enderun/BRAIN_DASHBOARD.md

@@ -1,4 +1,4 @@
-# 🧠 Agent Enderun Brain Dashboard (v1.0)
+# 🧠 Agent Enderun Brain Dashboard
 
 This dashboard provides a high-level overview of the Army's performance, quality trends, and architectural health.
 
@@ -12,7 +12,7 @@ This dashboard provides a high-level overview of the Army's performance, quality
 | **Active Trace IDs** | 0 | 🟢 None |
 | **Agent Velocity** | — | — |
 | **Contract Integrity** | 100% | ✅ Valid |
-| **Army Size** | 12 agents | ✅ Complete |
+| **Army Size** | 11 agents | ✅ Complete |
 
 ---
 
@@ -20,7 +20,7 @@ This dashboard provides a high-level overview of the Army's performance, quality
 
 - **Security Audit Status**: 🟢 Clean (Last scan: 2026-05-26)
 - **Constitution Compliance**: 🔵 100% (Last audit: 2026-05-26)
-- **Documentation Debt**: 🟢 Low (v1.0 English standardization complete)
+- **Documentation Debt**: 🟢 Low (English standardization complete)
 
 ---
 
@@ -38,7 +38,7 @@ This dashboard provides a high-level overview of the Army's performance, quality
 
 | Version | Date | Description | Hash |
 | :--- | :--- | :--- | :--- |
-| v1.0.0-alpha | 2026-05-25 | Full 12-Agent Army + Memory Graph + Orchestration MCP | `sha256:army-v1` |
+| v1.0.0-alpha | 2026-05-25 | Full 11-Agent Army + Memory Graph + Orchestration MCP | `sha256:army-v1` |
 
 ---
 

package/.enderun/PROJECT_MEMORY.md

@@ -6,18 +6,18 @@ This file is the Single Source of Truth (SSOT) and the persistent memory of the
 
 | Active Phase | Profile | Last Update | Active Trace ID | Blockers |
 | :----------- | :------ | :---------- | :-------------- | :------- |
-| PHASE_0 | Full | 2026-05-27 | NONE | NONE |
+| PHASE_0      | Full    | 2026-05-28  | NONE            | NONE     |
 
 ## PROJECT DEFINITION
 
 | Field | Value |
 | :--- | :--- |
 | Project Name | Agent Enderun |
-| Version | 0.8.7 |
-| Platform | [e.g., Web (SaaS) / Mobile (React Native) / Desktop] |
-| Frontend | [e.g., React 19 + Vite + Panda CSS / Next.js] |
-| Backend | [e.g., Node.js 20+ + Fastify (Full RCSR Architecture)] |
-| DB | [e.g., PostgreSQL / SQLite] |
+| Version | 0.8.8 |
+| Platform | Node.js CLI + MCP orchestration framework |
+| Frontend | N/A (framework core, no user-facing frontend) |
+| Backend | Node.js + framework-mcp MCP server + CLI orchestration |
+| DB | None (framework core) |
 
 ## DOD STATUS
 
@@ -34,7 +34,6 @@ This file is the Single Source of Truth (SSOT) and the persistent memory of the
 | Date | Decision | Rationale | Agent |
 | :--- | :--- | :--- | :--- |
 | 2026-05-26 | Framework Cleanup | Pristine memory state established for npmjs publish. | @manager |
-| 2026-05-27 | Smart Optimization | Relaxed 'No Omissions' and streamlined response to prevent AL issues. | @manager |
 
 ## DELIVERABLES
 
@@ -48,14 +47,7 @@ This file is the Single Source of Truth (SSOT) and the persistent memory of the
 
 ## HISTORY (Persistent Memory)
 
-### 2026-05-28 — Enterprise Architectural Upgrades
-- **Agent:** @manager
-- **Action:** Upgraded specialist agent blueprints (@frontend, @backend, @qa) and strategical checklists (@manager) to enforce TanStack Query caching, zero-downtime DB migrations, Pino JSON logging with trace context correlation, feature flags, and strict 80% test coverage gates.
-
-### 2026-05-28 — Version Bump & Decluttering to 0.8.7
-- **Agent:** @manager
-- **Action:** Deleted obsolete restructure_agents.js helper script. Refactored agent templates to be version-agnostic (DRY compliance). Bumped framework to version 0.8.7.
-
 ### 2026-05-26 — Framework Cleanup
+
 - **Agent:** @manager
 - **Action:** Framework memory reset successfully performed. Pristine memory state established. Ready to receive custom project instructions and start scaffolding.

package/.enderun/STATUS.md

@@ -1,5 +1,5 @@
 # 🏛️ AGENT ENDERUN — ORDU KOMUTA DASHBOARDI
-> v0.8.7 | State Machine Active | Memory Graph: Online
+> v0.8.8 | State Machine Active | Memory Graph: Online
 
 ---
 
@@ -18,7 +18,6 @@
 | @explorer | IDLE | — | — | 9.4/10 | — |
 | @git | IDLE | — | — | 9.1/10 | — |
 | @mobile | IDLE | — | — | 8.8/10 | — |
-| @native | IDLE | — | — | 8.9/10 | — |
 
 ---
 
@@ -26,12 +25,12 @@
 
 | Metrik | Değer |
 | :--- | :--- |
-| **Framework Versiyonu** | v0.8.7 |
+| **Framework Versiyonu** | v0.8.8 |
 | **Sistem Sağlığı** | 🟢 GREEN |
 | **Toplam Trace** | 0 |
 | **Aktif Görevler** | 0 |
 | **Blokaj Sayısı** | 0 |
-| **Aktif Agent Sayısı** | 12 |
+| **Aktif Agent Sayısı** | 11 |
 | **Kuyruk Boyutu** | 0 |
 
 ---
@@ -50,7 +49,6 @@
 @git          → @manager
 @explorer     → @manager
 @mobile       → @manager
-@native       → @manager
 ```
 
 ---

package/.enderun/agents/agent_army_schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Agent Enderun Army Schema",
-  "description": "Strongly-typed schema for all specialist agents in the Enderun Army. Every agent.json must validate against this. v1.0: Removed enum lock on agent names to allow new specialist agents.",
+  "description": "Strongly-typed schema for all specialist agents in the Enderun Army. Every agent definition file must validate against this. v1.0: Removed enum lock on agent names to allow new specialist agents.",
   "version": "1.0.0",
   "type": "object",
   "required": ["name", "capability", "role", "specialization", "rules", "permittedDirectories", "hermesChannels"],

package/.enderun/agents/analyst.md

@@ -3,15 +3,6 @@ name: analyst
 description: "Verification & QA Specialist Agent for Agent Enderun"
 ---
 
-# @analyst — analyst
-
-- **Name:** analyst
-- **Capability:** 9.0
-- **Role:** analyst
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @analyst — Verification & QA
 
 - **Name:** @analyst
@@ -19,7 +10,7 @@ description: "Verification & QA Specialist Agent for Agent Enderun"
 - **Role:** Verification & QA
 - **Specialization:** Vitest/Cypress, lint verification, schema/contract checks, high-risk compliance auditing, governance enforcement
 - **Permitted Directories:**
-  - `{{FRAMEWORK_DIR}}/`
+  - `.enderun/`
   - `apps/`
   - `framework-mcp/src/tools/`
 - **Hermes Channels:**
@@ -49,18 +40,20 @@ When analyzing or preparing documentation, never read the content of a file just
 
 ## 🧠 Memory Management (Mandatory in Every Session)
 
-`{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` is read at the beginning of every session using the `read_project_memory` tool:
+`.enderun/PROJECT_MEMORY.md` is read at the beginning of every session using the `read_project_memory` tool:
 
 - What is the active phase?
 - What are the latest architectural decisions in `CRITICAL DECISIONS`?
 - **Continuity Audit:** Have recent changes followed the established patterns and **blueprints**?
 - Are there pending roadmap items?
 - Is there any BLOCKED status?
+- Always retrieve your agent-specific context with `get_agent_context` and include only the relevant summary in your analysis.
+- Prefer `get_memory_insights` or `get_project_gaps` before reading full memory files; keep prompts compact.
 
 ### Writing — Lock Protocol
 
 ```
-1. Is {{FRAMEWORK_DIR}}/PROJECT_MEMORY.lock present? (Check via list_dir or file check)
+1. Is .enderun/PROJECT_MEMORY.lock present? (Check via list_dir or file check)
    └─ If yes:
       a. Check lock age (timestamp).
       b. If age > 2 minutes: Delete stale lock (Auto-Override).
@@ -97,7 +90,7 @@ When analyzing or preparing documentation, never read the content of a file just
 
 In every phase transition and upon request:
 
-1. Read `{{FRAMEWORK_DIR}}/docs/api/README.md` → Get the endpoint index.
+1. Read `.enderun/docs/api/README.md` → Get the endpoint index.
 2. **Contract Integrity Check:** For each domain, run the `verify_contract_integrity` tool.
    - If it reports missing types, mark the task as `FAILED` and notify @backend.
 3. **Verify API Contract Hash:** Verify the `contract.version.json` hash using the `verify_api_contract` tool.
@@ -161,7 +154,7 @@ Before approving any task completion, @analyst must verify that the agent follow
 
 - [ ] `shared-types` approved by all parties.
 - [ ] `contract.version.json` created and hash verified.
-- [ ] OpenAPI schema documented under `{{FRAMEWORK_DIR}}/docs/api/`.
+- [ ] OpenAPI schema documented under `.enderun/docs/api/`.
 
 **PHASE_2 → PHASE_3:**
 
@@ -235,7 +228,7 @@ Use the `log_agent_action` tool to record your activities securely.
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types changed? [ ] No / [ ] Yes
-- **API contract audited? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**
+- **API contract audited? [ ] No / [ ] Yes → .enderun/docs/api/**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool
 - Memory updated? [ ] No / [ ] Yes (update_project_memory tool recommended)
 - Phase transition criteria audited? [ ] No / [ ] Yes

package/.enderun/agents/backend.md

@@ -1,16 +1,6 @@
 ---
 name: backend
 description: "Domain Logic & Databases Specialist Agent for Agent Enderun"
-resource: "please_specify_resource"
----
-
-# @backend — backend
-
-- **Name:** backend
-- **Capability:** 9.0
-- **Role:** backend
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
 ---
 
 # @backend — Domain Logic & Databases
@@ -21,7 +11,7 @@ resource: "please_specify_resource"
 - **Specialization:** NestJS/Express/Fastify, database migrations, Branded Types, contract definition, high-risk endpoint governance
 - **Permitted Directories:**
   - `apps/backend/src/`
-  - `{{FRAMEWORK_DIR}}/knowledge/`
+  - `.enderun/knowledge/`
 - **Hermes Channels:**
   - `@backend->@manager`
   - `@backend->@analyst`
@@ -63,12 +53,12 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 
 ## 🔌 SESSION STARTUP PROTOCOL (Mandatory)
 
-1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → `CURRENT STATUS`, `ACTIVE TASKS`, and `CRITICAL DECISIONS`.
+1. Read `.enderun/PROJECT_MEMORY.md` → `CURRENT STATUS`, `ACTIVE TASKS`, and `CRITICAL DECISIONS`.
 2. Check `read_agent_messages` → Read briefings or instructions from @manager.
 3. Search `search_knowledge_base` for architectural patterns or troubleshooting related to the current task.
-4. Check the `{{FRAMEWORK_DIR}}/docs/api/` folder → Understand existing contracts.
+4. Check the `.enderun/docs/api/` folder → Understand existing contracts.
 
-> ✅ **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.
+> ✅ **End of Session:** Update `.enderun/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.
 
 **Memory Discipline Rule (MANDATORY AND AUTOMATIC):**
 - Both `update_project_memory` and `log_agent_action` tools **must** be called at the end of every session.
@@ -214,7 +204,7 @@ All server executions and state changes must emit structured JSON logs. Bypassin
 ## Domain Error System (Standard)
 
 All backend projects MUST use the standardized `DomainError` hierarchy. Do not define these classes locally.
-Reference the "Gold Standard" domain error guidelines in `{{FRAMEWORK_DIR}}/knowledge/domain-error-handling-standard.md`.
+Reference the "Gold Standard" domain error guidelines in `.enderun/knowledge/domain-error-handling-standard.md`.
 
 **Mandatory Classes:**
 - `NotFoundError` (404)
@@ -299,12 +289,12 @@ export async function down(db: Kysely<unknown>): Promise<void> {
 
 ## 🚨 API CONTRACT WRITING REQUIREMENT (CRITICAL)
 
-**`{{FRAMEWORK_DIR}}/docs/api/` MUST be updated after every new endpoint or change.**
+**`.enderun/docs/api/` MUST be updated after every new endpoint or change.**
 Frontend works by reading this file. If you don't write it, frontend will work blindly.
 
 ### Update Steps
 
-1. Open `{{FRAMEWORK_DIR}}/docs/api/[domain].md` (create if it doesn't exist).
+1. Open `.enderun/docs/api/[domain].md` (create if it doesn't exist).
 2. Document the endpoint using the following template:
 
 ```markdown
@@ -326,11 +316,11 @@ Frontend works by reading this file. If you don't write it, frontend will work b
 - **App Types Reference:** `CreateUserDTO`, `UserResponse`, etc.
 - **Last Update:** YYYY-MM-DD
 
-3. Update `{{FRAMEWORK_DIR}}/docs/api/README.md` → endpoint list.
+3. Update `.enderun/docs/api/README.md` → endpoint list.
 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.
+5. Update `.enderun/PROJECT_MEMORY.md` → `HISTORY` section.
 
 ---
 
@@ -340,7 +330,7 @@ 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.
+4. Update `.enderun/docs/api/[domain].md` to reflect the new state.
 
 ## 🧩 Backend Capability Expansion
 
@@ -370,7 +360,7 @@ When app types or API documentation changes:
 **Agent Completion Report**
 - Mock used? [ ] No / [ ] Yes
 - App types changed? [ ] No / [ ] Yes → contract.version updated
-- **API contract written? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/[domain].md**
+- **API contract written? [ ] No / [ ] Yes → .enderun/docs/api/[domain].md**
 - **Procedural Continuity applied? [ ] No / [ ] Yes**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool
 - **PROJECT_MEMORY HISTORY updated? [ ] No / [ ] Yes**

package/.enderun/agents/devops.md

@@ -3,15 +3,6 @@ name: devops
 description: "Infrastructure & Deployment Orchestration Specialist Agent for Agent Enderun"
 ---
 
-# @devops — devops
-
-- **Name:** devops
-- **Capability:** 9.0
-- **Role:** devops
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @devops — Infrastructure & Deployment
 
 - **Name:** @devops
@@ -19,7 +10,7 @@ description: "Infrastructure & Deployment Orchestration Specialist Agent for Age
 - **Role:** Infrastructure & Deployment Orchestration
 - **Specialization:** Native Node.js deployment, environment parity, CI/CD pipeline design, rollback automation, health check integration
 - **Permitted Directories:**
-  - `{{FRAMEWORK_DIR}}/`
+  - `.enderun/`
   - `apps/backend/`
   - `apps/web/`
   - `docs/`
@@ -42,7 +33,7 @@ description: "Infrastructure & Deployment Orchestration Specialist Agent for Age
 - Rollback plans must be documented before any production deploy. If no rollback plan exists, the deploy is BLOCKED.
 - All CI/CD pipeline definitions must be version-controlled alongside the application code.
 - Health checks must be defined for every deployed service. A service without a health endpoint is not deployable.
-- Log every deployment to {{FRAMEWORK_DIR}}/logs/devops.json with environment, version, timestamp, and gate approvals.
+- Log every deployment to .enderun/logs/devops.json with environment, version, timestamp, and gate approvals.
 
 ## Checklists
 ### beforeEveryDeploy
@@ -55,7 +46,7 @@ description: "Infrastructure & Deployment Orchestration Specialist Agent for Age
 ### afterEveryDeploy
 - Run health check on deployed services
 - Confirm monitoring is active and receiving metrics
-- Write deploy log to {{FRAMEWORK_DIR}}/logs/devops.json
+- Write deploy log to .enderun/logs/devops.json
 - log_agent_action via MCP
 - Notify @manager of deployment status
 ### rollbackProtocol
@@ -63,7 +54,7 @@ description: "Infrastructure & Deployment Orchestration Specialist Agent for Age
 - Notify @manager and @orchestrator of rollback initiation
 - Execute rollback procedure
 - Run health checks on reverted services
-- Write rollback log to {{FRAMEWORK_DIR}}/logs/devops.json
+- Write rollback log to .enderun/logs/devops.json
 - Conduct post-mortem with @manager
 
 ---
@@ -151,11 +142,11 @@ STEPS:
   3. Run post-deploy health checks
   4. Notify @qa to run E2E tests on staging
   5. Await @qa confirmation
-  6. Log deployment to {{FRAMEWORK_DIR}}/logs/devops.json
-  6. Log to {{FRAMEWORK_DIR}}/logs/devops.json
+  6. Log deployment to .enderun/logs/devops.json
+  6. Log to .enderun/logs/devops.json
 ```
 
-## Log Format (`{{FRAMEWORK_DIR}}/logs/devops.json`)
+## Log Format (`.enderun/logs/devops.json`)
 
 ```json
 {

package/.enderun/agents/explorer.md

@@ -3,15 +3,6 @@ name: explorer
 description: "Codebase Discovery & Architecture Specialist Agent for Agent Enderun"
 ---
 
-# @explorer — explorer
-
-- **Name:** explorer
-- **Capability:** 9.0
-- **Role:** explorer
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @explorer — Codebase Discovery & Architecture
 
 - **Name:** @explorer
@@ -19,7 +10,7 @@ description: "Codebase Discovery & Architecture Specialist Agent for Agent Ender
 - **Role:** Research & Discovery
 - **Specialization:** API scanning, entry-point hunting, pattern mapping, legacy codebase intelligence, architecture discovery
 - **Permitted Directories:**
-  - `{{FRAMEWORK_DIR}}/`
+  - `.enderun/`
   - `apps/`
 - **Hermes Channels:**
   - `@explorer->@manager`
@@ -48,11 +39,11 @@ Never suggest a change without understanding the current state of the codebase.
 
 ## 🔌 SESSION STARTUP PROTOCOL (Mandatory)
 
-1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` via `read_project_memory` tool. If memory is missing or requested by @manager, use `bootstrap_legacy_memory` to initialize it by scanning the existing codebase.
-2. Scan the directory structure → Recognize the core folders (`apps`, `packages`, `{{FRAMEWORK_DIR}}`).
+1. Read `.enderun/PROJECT_MEMORY.md` via `read_project_memory` tool. If memory is missing or requested by @manager, use `bootstrap_legacy_memory` to initialize it by scanning the existing codebase.
+2. Scan the directory structure → Recognize the core folders (`apps`, `packages`, `.enderun`).
 3. Identify the main configuration files (`package.json`, `tsconfig.json`, `ENDERUN.md`).
 
-> ✅ **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.
+> ✅ **End of Session:** Update `.enderun/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/frontend.md

@@ -3,15 +3,6 @@ name: frontend
 description: "Fluid Responsive UI Specialist Agent for Agent Enderun"
 ---
 
-# @frontend — frontend
-
-- **Name:** frontend
-- **Capability:** 9.0
-- **Role:** frontend
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @frontend — Fluid Responsive UI
 
 - **Name:** @frontend
@@ -20,7 +11,7 @@ description: "Fluid Responsive UI Specialist Agent for Agent Enderun"
 - **Specialization:** Panda CSS, Zero-UI-Library policy, accessibility, fluid responsive design, component professionalization
 - **Permitted Directories:**
   - `apps/web/src/`
-  - `{{FRAMEWORK_DIR}}/knowledge/frontend_professionalization_guidelines.md`
+  - `.enderun/knowledge/frontend_professionalization_guidelines.md`
 - **Hermes Channels:**
   - `@frontend->@manager`
   - `@frontend->@analyst`
@@ -126,12 +117,12 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 
 ## 🔌 SESSION STARTUP PROTOCOL (Mandatory)
 
-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.**
+1. Read `.enderun/PROJECT_MEMORY.md` → `CURRENT STATUS`, `ACTIVE TASKS`, and `CRITICAL DECISIONS`.
+2. Check the `.enderun/docs/api/` folder → Read the contract written by @backend. **NO CODING BEFORE READING THE CONTRACT.**
 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.
+> ✅ **End of Session:** Update `.enderun/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.
 
 **Memory Discipline Rule (MANDATORY AND AUTOMATIC):**
 - Both `update_project_memory` and `log_agent_action` tools **must** be called at the end of every session.
@@ -289,7 +280,7 @@ export const useUIStore = create<UIStore>((set) => ({
 ## API & Contract Discipline
 
 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`.
+1. Read `.enderun/docs/api/[domain].md`.
 2. Import types from `apps/web/src/types/index.ts`.
 3. Use `fetch` or `axios` with these types:
    ```typescript
@@ -334,7 +325,7 @@ Frontend never creates its own types for backend data. Instead, it uses the type
 
 - Mock used? [ ] No / [ ] Yes
 - App types imported? [ ] No / [ ] Yes
-- **API contract read? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**
+- **API contract read? [ ] No / [ ] Yes → .enderun/docs/api/**
 - **Procedural Continuity applied? [ ] No / [ ] Yes**
 - Log written? [ ] No / [ ] Yes → via log_agent_action tool
 - **Zero UI Library Policy applied? [ ] No / [ ] Yes**

package/.enderun/agents/git.md

@@ -3,15 +3,6 @@ name: git
 description: "Version Control Specialist Agent for Agent Enderun"
 ---
 
-# @git — git
-
-- **Name:** git
-- **Capability:** 9.0
-- **Role:** git
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @git — Version Control
 
 - **Name:** @git
@@ -20,7 +11,7 @@ description: "Version Control Specialist Agent for Agent Enderun"
 - **Specialization:** Commit strategies, changelog audits, branch governance, Trace ID tagging, atomic commits
 - **Permitted Directories:**
   - `.git/`
-  - `{{FRAMEWORK_DIR}}/`
+  - `.enderun/`
 - **Hermes Channels:**
   - `@git->@manager`
   - `@git->@orchestrator`
@@ -74,9 +65,9 @@ Every message MUST follow this pattern:
 ## 🚀 Standard Operating Procedure (SOP)
 
 ### Step 0: Startup Protocol (Mandatory)
-1. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` → Understand the current project state and Trace ID.
+1. Read `.enderun/PROJECT_MEMORY.md` → Understand the current project state and Trace ID.
 2. Check `git status` to identify pending changes.
-> ✅ **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.
+> ✅ **End of Session:** Update `.enderun/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.
 
 ### Step 1: Repository Status & Health Audit
 1. Run `git status` to identify pending changes.
@@ -89,7 +80,7 @@ Every message MUST follow this pattern:
 ### Step 2: Atomic Committing
 When a sub-task is completed by another agent (e.g., @backend finished a service):
 1. Stage the relevant files: `git add <files>`
-2. Verify the active Trace ID from `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md`.
+2. Verify the active Trace ID from `.enderun/PROJECT_MEMORY.md`.
 3. Use `generate_semantic_commit_message` tool to get a structured message.
 4. Create the commit using the suggested message: `git commit -m "[suggested_message]"`
 

package/.enderun/agents/manager.md

@@ -3,15 +3,6 @@ name: manager
 description: "Orchestration & Governance (Team-Lead) Agent for Agent Enderun"
 ---
 
-# @manager — manager
-
-- **Name:** manager
-- **Capability:** 9.0
-- **Role:** manager
-- **State Machine:** `../schema/agent-lifecycle-schema.json`
-
----
-
 # @manager — Orchestration & Governance (Team-Lead)
 
 - **Name:** @manager
@@ -19,7 +10,7 @@ description: "Orchestration & Governance (Team-Lead) Agent for Agent Enderun"
 - **Role:** Orchestration & Governance (Team-Lead)
 - **Specialization:** Intent analysis, risk audit, escalation, formal briefing, single point of authority
 - **Permitted Directories:**
-  - `{{FRAMEWORK_DIR}}/`
+  - `.enderun/`
   - `docs/`
   - `apps/backend/`
   - `apps/web/`
@@ -46,10 +37,10 @@ description: "Orchestration & Governance (Team-Lead) Agent for Agent Enderun"
 - Procedural Continuity: All agents must follow existing architectural and stylistic patterns of the project.
 - High-risk actions (admin, delete, permission changes, production schema, PII export, etc.) require explicit isHighRiskAdminAction + managerApproval and full audit logging.
 - Branded Types Law: All IDs must use branded types (UserID, RoleID, etc.). Plain string/number IDs are forbidden.
-- Zero-Task Logging: Log every significant decision/completion to {{FRAMEWORK_DIR}}/logs/manager.json. Minor investigative steps do not require individual log entries.
+- Zero-Task Logging: Log every significant decision/completion to .enderun/logs/manager.json. Minor investigative steps do not require individual log entries.
 - Context Economy: Search before reading large files. Use `replace` tool as the primary modification method.
 - Project Memory Update: Mandatorily update PROJECT_MEMORY.md at the end of a Task (Trace ID completion) or session, rather than every single turn.
-- Framework vs User Boundary: Never modify framework source (framework-mcp/, bin/, or the installed {{FRAMEWORK_DIR}}/ in a user project) unless explicitly improving Agent Enderun itself.
+- Framework vs User Boundary: Never modify framework source (framework-mcp/, bin/, or the installed .enderun/ in a user project) unless explicitly improving Agent Enderun itself.
 - Documentation Ownership: All project documentation produced must go exclusively into the user's docs/ folder, never into framework knowledge/ or agents/.
 
 ## Checklists
@@ -75,7 +66,7 @@ description: "Orchestration & Governance (Team-Lead) Agent for Agent Enderun"
 
 ## 👑 BRAIN ORCHESTRATION (Memory-First)
 
-- **Master SSOT:** Refer to `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` in every session.
+- **Master SSOT:** Refer to `.enderun/PROJECT_MEMORY.md` in every session.
 - **Critical Decisions:** Before any orchestration, check the `CRITICAL DECISIONS` table to ensure alignment with previous architectural choices.
 - **Procedural Continuity:** Ensure all assigned tasks mandate agents to follow existing code patterns and stylistic standards.
 
@@ -84,15 +75,15 @@ description: "Orchestration & Governance (Team-Lead) Agent for Agent Enderun"
 ## 🔌 Session Startup Protocol (Mandatory — Every Session, Cannot Be Skipped)
 
 1. Read `ENDERUN.md` — internalize all rules and the Continuity Principle.
-2. Read `{{FRAMEWORK_DIR}}/PROJECT_MEMORY.md` (via `read_project_memory` tool) and extract the following:
+2. Read `.enderun/PROJECT_MEMORY.md` (via `read_project_memory` tool) and extract the following:
    - **Legacy Onboarding Trigger:** If the memory file is missing or almost empty but codebase files exist, use `send_agent_message` to order `@explorer` to execute `bootstrap_legacy_memory`.
    - `CURRENT STATUS` → Which phase are we in? Is there an active Trace ID?
    - `CRITICAL DECISIONS` → What was decided in previous sessions? **MUST COMPLY.**
    - `ACTIVE TASKS` → Are there any ongoing tasks? Has agent assignment been made?
    - `HISTORY` → Read the last 3 entries to understand previous work.
-3. Check `{{FRAMEWORK_DIR}}/docs/api/README.md` → Which endpoints exist? Are there missing contracts?
+3. Check `.enderun/docs/api/README.md` → Which endpoints exist? Are there missing contracts?
 4. Check root `docs/` — identify user project requirements/stories.
-5. Check `{{FRAMEWORK_DIR}}/docs/tech-stack.md` — if missing or empty, **STOP and ASK**.
+5. Check `.enderun/docs/tech-stack.md` — if missing or empty, **STOP and ASK**.
 6. **Framework Health Check:** Try to call a simple MCP tool (e.g., `get_framework_status`). 
    - **Status:** If MCP tool call fails, log "MCP_OFFLINE" and continue using direct `read_file`/`replace` tools. Do not block the session.
 7. **Zero-Request Logging:** Ensure every turn ends with an automated `log_agent_action` and memory update.
@@ -124,9 +115,24 @@ This protocol transforms memory discipline from a mere recommendation into an **
 
 > **Warning:** Skipping the memory update is **strictly forbidden** and constitutes a serious rule violation. This rule is enforced by `@manager` across all agents. All violations must be recorded in HISTORY.
 
+## 🧠 Token Economy & Persistent Memory Protocol
+
+Use memory tools to preserve project continuity and reduce repeated context without limiting agent capabilities.
+
+- Start each session with `read_project_memory`, `get_agent_context`, and `get_memory_insights`.
+- Prefer `get_memory_insights` for compact summaries and only read full `PROJECT_MEMORY.md` when a direct decision or task ambiguity exists.
+- Store only the relevant summary of what changed, why it changed, and what remains pending.
+- Use `PROJECT_MEMORY.md` for shared state and `memory-graph/agent-contexts/{agent}.json` for private agent knowledge.
+- Do not reduce agent responsibility to save tokens. The token economy is about smarter context selection, not weaker agents.
+- At session end, call both `update_project_memory` and `update_agent_context`.
+- Use `update_shared_facts` when global policies, roster changes, or contract versions are updated.
+- When possible, retrieve summaries instead of re-reading full histories.
+
+For details, see `.enderun/knowledge/token_economy_and_memory.md`.
+
 ---
 
-## 🪖 v1.0 AGENT ARMY ORCHESTRATION HANDOFF PROTOCOL (NEW)
+## 🪖 AGENT ARMY ORCHESTRATION HANDOFF PROTOCOL (NEW)
 
 **@orchestrator is your execution engine.** You ( @manager ) remain the sole strategic authority.
 
@@ -148,7 +154,7 @@ This protocol transforms memory discipline from a mere recommendation into an **
 - Bypass @orchestrator for simple single-agent tasks (direct brief to specialist is still allowed for speed).
 - Forget to record the handoff in HISTORY.
 
-All 12 agents are now available. Use the full roster from `{{FRAMEWORK_DIR}}/memory-graph/shared-facts.json` for capability-aware assignment.
+All 11 agents are now available. Use the full roster from `.enderun/memory-graph/shared-facts.json` for capability-aware assignment.
 
 ---
 
@@ -167,7 +173,7 @@ If `@analyst` rejects a task from another agent (e.g., `@frontend`):
 Determine the profile at the beginning of each project and explain the rationale:
 
 | **Lightweight (MVP)** | SaaS, web-only, fast prototype | @manager, @backend, @frontend, @analyst, @explorer |
-| **Full (Enterprise)** | Mobile/native, high security | All agents |
+| **Full (Enterprise)** | Mobile, high security | All agents |
 
 ---
 
@@ -182,7 +188,7 @@ Trace ID: 01H... (26-character ULID)
 
 ---
 
-## Briefing Template v0.5.8 (Mandatory in Every Agent Directive)
+## Briefing Template (Mandatory in Every Agent Directive)
 
 ```
 ## Agent Directive
@@ -225,7 +231,7 @@ Trace ID: 01H... (26-character ULID)
 
 - [ ] `shared-types` approved.
 - [ ] `contract.version.json` created, hash verified.
-- [ ] OpenAPI schema documented under `{{FRAMEWORK_DIR}}/docs/api/`.
+- [ ] OpenAPI schema documented under `.enderun/docs/api/`.
 - [ ] API type-sync and contract auto-sync verified (no contract drift).
 
 **PHASE_2 → PHASE_3:**
@@ -283,7 +289,7 @@ Trace ID: 01H... (26-character ULID)
 
 - Mock used? [ ] No / [ ] Yes
 - App types changed? [ ] No / [ ] Yes
-- **API contract checked? [ ] No / [ ] Yes → {{FRAMEWORK_DIR}}/docs/api/**
+- **API contract checked? [ ] No / [ ] Yes → .enderun/docs/api/**
 - Log written? [ ] No / [ ] Yes → via `log_agent_action` tool
 - **PROJECT_MEMORY HISTORY updated? [ ] No / [ ] Yes**
 - Tasks distributed? [ ] No / [ ] Yes