agent-enderun 0.8.8 → 0.9.0

package/.enderun/BRAIN_DASHBOARD.md

@@ -1,4 +1,4 @@
-# 🧠 Agent Enderun Brain Dashboard
+# 🧠 Agent Enderun Brain Dashboard (v1.0)
 
 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** | 11 agents | ✅ Complete |
+| **Army Size** | 12 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 (English standardization complete)
+- **Documentation Debt**: 🟢 Low (v1.0 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 11-Agent Army + Memory Graph + Orchestration MCP | `sha256:army-v1` |
+| v1.0.0-alpha | 2026-05-25 | Full 12-Agent Army + Memory Graph + Orchestration MCP | `sha256:army-v1` |
 
 ---
 

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

@@ -3,11 +3,13 @@
 
 ## 🎖️ AGENT CHECKLIST (MANDATORY BEFORE RESPONSE)
 > Check this list at the end of every response:
-- [ ] **Surgical Quality:** Did you use the `replace` tool for targeted changes? For files >100 lines, focus on changed blocks and use `...` for untouched sections to preserve token limit. (Quality over Volume)
+- [ ] **Surgical Quality:** Did you use the `replace_text` tool for targeted changes? For files >100 lines, focus on changed blocks. (Quality over Volume)
+- [ ] **Autonomous Growth:** Use `create_app` for generating new modules from specs.
 - [ ] **Contract First:** Are the app's types and apps/backend/contract.version.json up to date?
 - [ ] **Audit Log:** Did you log this action in `{{FRAMEWORK_DIR}}/logs/[agent].json`?
 - [ ] **CLI Orchestration:** Does the action comply with `{{ADAPTER}} cli` rules?
 - [ ] **Complete Context:** Ensure all changed logic is fully written. Placeholder `...` is only for *unchanged* surrounding code.
+- [ ] **ESLint Compliance:** Did you run `npm run lint` (or `agent-enderun check:lint`)? Zero errors required; follow `{{FRAMEWORK_DIR}}/knowledge/eslint-standards.md`.
 
 ---
 
@@ -35,7 +37,7 @@ To minimize AI costs and maximize speed, all agents must adhere to the **Token E
 ---
 
 ## Constitution Status
-This file (`./{{ADAPTER}}.md`) and the `{{FRAMEWORK_DIR}}/docs/` folder represent the "Supreme Law" of the project. All agents must read this file first in every session and strictly comply with its rules 100%. All framework-specific documentation is stored within `{{FRAMEWORK_DIR}}/docs/`.
+This file (`./.enderun/ENDERUN.md`) and the `.enderun/docs/` folder represent the "Supreme Law" of the project. All agents must read this file first in every session and strictly comply with its rules 100%. All framework-specific documentation is stored within `.enderun/docs/`.
 
 ---
 

package/.enderun/PROJECT_MEMORY.md

@@ -1,53 +1,20 @@
-# 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      | Full    | 2026-05-28  | NONE            | NONE     |
-
-## PROJECT DEFINITION
-
-| Field | Value |
-| :--- | :--- |
-| Project Name | Agent Enderun |
-| 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
-
-| Phase | Status | Note |
-| :--- | :--- | :--- |
-| PHASE_0 | PENDING | Discovery & Setup |
-| PHASE_1 | PENDING | Architecture & Contracts |
-| PHASE_2 | PENDING | Core Development |
-| PHASE_3 | PENDING | Integration & Testing |
-| PHASE_4 | PENDING | Optimization & Deployment |
-
-## CRITICAL DECISIONS
-
-| Date | Decision | Rationale | Agent |
-| :--- | :--- | :--- | :--- |
-| 2026-05-26 | Framework Cleanup | Pristine memory state established for npmjs publish. | @manager |
-
-## DELIVERABLES
-
-| Module | Status | Agent | Date |
-| :--- | :--- | :--- | :--- |
+- Phase: PHASE_0 (Discovery & Setup)
+- Trace ID: 01HGT8J5E2N0W0W0W0W0W0W0W0
+- @manager state: IDLE - System Restored to Factory Settings.
 
 ## ACTIVE TASKS
 
 | Trace ID | Task | Agent | Priority | Status |
 | :--- | :--- | :--- | :--- | :--- |
 
-## HISTORY (Persistent Memory)
-
-### 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.
+## CRITICAL DECISIONS
+- **Tech Stack:** Node.js/Fastify, React/Vite, PostgreSQL, Kysely.
+- **Surgical Standard:** replace_text/patch_file is mandatory for all edits.
+- **Contract First:** All developments must start with type definitions.
+- **Memory Standard:** Auto-pruning active (max 10 entries).
+
+## HISTORY
+- **SYSTEM INITIALIZED:** Framework v0.9.0 promoted to stable release state.
+- **CLEAN SLATE:** All developmental logs, messages, and temporary histories purged for fresh start.

package/.enderun/STATUS.md

@@ -1,5 +1,5 @@
 # 🏛️ AGENT ENDERUN — ORDU KOMUTA DASHBOARDI
-> v0.8.8 | State Machine Active | Memory Graph: Online
+> v0.9.0 | State Machine Active | Memory Graph: Online
 
 ---
 
@@ -7,9 +7,9 @@
 
 | Agent | State | CurrentTask | BlockedBy | HealthScore | LastAction |
 | :--- | :--- | :--- | :--- | :--- | :--- |
-| @manager | IDLE | — | — | 9.5/10 | Framework Reset |
-| @orchestrator | IDLE | — | — | 9.8/10 | — |
-| @analyst | IDLE | — | — | 9.6/10 | — |
+| @manager | ACTIVE | Readiness Mühürleme | — | 10/10 | v0.9.0 Promotion |
+| @orchestrator | IDLE | — | — | 9.8/10 | Path Synchronization |
+| @analyst | IDLE | — | — | 9.6/10 | Contract Review |
 | @backend | IDLE | — | — | 9.2/10 | — |
 | @frontend | IDLE | — | — | 9.0/10 | — |
 | @security | IDLE | — | — | 9.3/10 | — |
@@ -18,6 +18,7 @@
 | @explorer | IDLE | — | — | 9.4/10 | — |
 | @git | IDLE | — | — | 9.1/10 | — |
 | @mobile | IDLE | — | — | 8.8/10 | — |
+| @native | IDLE | — | — | 8.9/10 | — |
 
 ---
 
@@ -27,10 +28,10 @@
 | :--- | :--- |
 | **Framework Versiyonu** | v0.8.8 |
 | **Sistem Sağlığı** | 🟢 GREEN |
-| **Toplam Trace** | 0 |
-| **Aktif Görevler** | 0 |
+| **Büyük Yönetişim Denetimi** | TAMAMLANDI |
+| **Aktif Görevler** | 1 |
 | **Blokaj Sayısı** | 0 |
-| **Aktif Agent Sayısı** | 11 |
+| **Aktif Agent Sayısı** | 12 |
 | **Kuyruk Boyutu** | 0 |
 
 ---
@@ -49,6 +50,7 @@
 @git          → @manager
 @explorer     → @manager
 @mobile       → @manager
+@native       → @manager
 ```
 
 ---
@@ -58,4 +60,3 @@
 `IDLE → BRIEFED → EXECUTING → DONE → IDLE`
 
 Detay: `.enderun/agents/schema/agent-lifecycle-schema.json`
-json`

package/.enderun/agents/agent_army_schema.json

@@ -1,10 +1,18 @@
 {
   "$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 definition file 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.json 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"],
+  "required": [
+    "name",
+    "capability",
+    "role",
+    "specialization",
+    "rules",
+    "permittedDirectories",
+    "hermesChannels"
+  ],
   "properties": {
     "name": {
       "type": "string",
@@ -31,13 +39,17 @@
     },
     "rules": {
       "type": "array",
-      "items": { "type": "string" },
+      "items": {
+        "type": "string"
+      },
       "minItems": 1,
       "description": "Mandatory behavioral rules the agent must never violate."
     },
     "permittedDirectories": {
       "type": "array",
-      "items": { "type": "string" },
+      "items": {
+        "type": "string"
+      },
       "minItems": 1,
       "description": "Directories this agent is authorized to read/write. Any access outside these requires @manager approval."
     },
@@ -58,7 +70,9 @@
       "type": "object",
       "additionalProperties": {
         "type": "array",
-        "items": { "type": "string" }
+        "items": {
+          "type": "string"
+        }
       },
       "description": "Named checklists the agent must execute. e.g. 'beforeEveryResponse', 'beforeDelegating'"
     },
@@ -76,10 +90,18 @@
       "type": "array",
       "items": {
         "type": "string",
-        "enum": ["core", "specialist", "infrastructure", "governance", "quality", "security", "orchestration"]
+        "enum": [
+          "core",
+          "specialist",
+          "infrastructure",
+          "governance",
+          "quality",
+          "security",
+          "orchestration"
+        ]
       },
       "description": "Classification tags for filtering and grouping agents."
     }
   },
   "additionalProperties": false
-}
+}

package/.enderun/agents/analyst.md

@@ -3,7 +3,7 @@ name: analyst
 description: "Verification & QA Specialist Agent for Agent Enderun"
 ---
 
-# @analyst — Verification & QA
+# @analyst — Verification & QA 
 
 - **Name:** @analyst
 - **Capability:** 9.6
@@ -26,7 +26,7 @@ description: "Verification & QA Specialist Agent for Agent Enderun"
 
 ---
 
-# Project Analyst & QA Gate
+# Project Analyst & QA Gate — 
 
 **Role:** Maintain project memory, serve as a quality gate, and manage documentation. The following protocols are automatically applied in every task.
 
@@ -47,8 +47,6 @@ When analyzing or preparing documentation, never read the content of a file just
 - **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
 
@@ -224,7 +222,7 @@ Use the `log_agent_action` tool to record your activities securely.
 
 ---
 
-**Agent Completion Report**
+**Agent Completion Report** 
 
 - Mock used? [ ] No / [ ] Yes
 - shared-types changed? [ ] No / [ ] Yes

package/.enderun/agents/backend.md

@@ -3,7 +3,7 @@ name: backend
 description: "Domain Logic & Databases Specialist Agent for Agent Enderun"
 ---
 
-# @backend — Domain Logic & Databases
+# @backend — Domain Logic & Databases 
 
 - **Name:** @backend
 - **Capability:** 9.2
@@ -28,7 +28,7 @@ description: "Domain Logic & Databases Specialist Agent for Agent Enderun"
 
 ---
 
-# Backend Architect
+# Backend Architect — 
 
 **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.
 
@@ -161,19 +161,6 @@ Route (Fastify)
 
 ---
 
-## 🗄️ Database Migration Safety & Schema Governance (Zero-Downtime)
-
-To prevent data loss and dynamic API breaks during production updates, the agent MUST enforce **Zero-Downtime migrations**:
-- **No Yikhici Changes (Destructive Schema Modifications Forbidden)**: Directly running `ALTER TABLE ... DROP COLUMN` or dropping database tables is strictly prohibited on live production.
-- **Phased Deprecation Path (2-Step Migration Strategy)**:
-  1. *Phase 1 (Deploy Code + Additive Schema)*: Create the new table or column. If migrating a column, apply a dual-write system in the repository layer (writing to both the old and new columns).
-  2. *Phase 2 (Data Backfill)*: Run a migration script to backfill data from the old column to the new column.
-  3. *Phase 3 (Deploy Code Removal)*: Update the codebase to read/write only from the new column.
-  4. *Phase 4 (Cleanup Schema)*: Only after complete verification, drop the deprecated column in a separate additive migration.
-- **Soft Delete Standard**: Always use a nullable `deletedAt: Date | null` column. Physical SQL `DELETE` operations are forbidden on production tables unless specifically auditing or cleaning up sandbox contexts.
-
----
-
 ## 🏗️ Base Architecture & Code Reuse (Standard)
 
 To eliminate code repetition, all backend development MUST follow the **Base Pattern**. Agents are not allowed to write redundant CRUD logic.
@@ -188,16 +175,12 @@ All entities must implement the `BaseEntity` interface (from the app's local typ
 
 ---
 
-## 🕵️ Structured Logging & OpenTelemetry Telemetry (Mandatory)
-
-All server executions and state changes must emit structured JSON logs. Bypassing structured log aggregation via standard `console.log` is strictly forbidden.
+## 🕵️ Automatic Audit Logging (Mandatory)
 
-- **JSON Logging Standard (Pino/Winston)**: All system transactions, network hooks, and repository statements must be logged in JSON structure:
-  ```ts
-  logger.info({ trace_id, action: 'USER_CREATE', userId: user.id }, "User record created successfully");
-  ```
-- **Trace Context Propagation**: Every log entry, API payload, and Kysely database statement must contain the active **Trace ID** (`trace_id`). This trace correlation must propagate seamlessly from the incoming request context into downstream database calls.
-- **Audit Logging**: Every mutation (CREATE, UPDATE, DELETE) must generate an audit log entry detailing both the `previousState` and `newState` mapped against the performing `UserID` and active `trace_id`.
+Every "mutation" (CREATE, UPDATE, DELETE) MUST trigger an audit log entry.
+- **Traceability:** Link every audit log to the active **Trace ID**.
+- **State Capture:** For updates, capture both `previousState` and `newState`.
+- **User Context:** Identify the `UserID` performing the action.
 
 ---
 
@@ -242,15 +225,14 @@ await db.transaction().execute(async (trx) => { ... });
 ## Async Error Management (Mandatory for every async block)
 
 ```typescript
-async function createUser(data: CreateUserDTO, ctx: RequestContext): Promise<User> {
+async function createUser(data: CreateUserDTO): Promise<User> {
   try {
     const existing = await userRepository.findByEmail(data.email);
     if (existing) throw new ConflictError("Email already in use.");
     return await userRepository.create(data);
   } catch (error) {
     if (error instanceof DomainError) throw error;
-    // Log structured error including OpenTelemetry trace correlation
-    logger.error({ error, trace_id: ctx.traceId }, "Unexpected database mutation error.");
+    logger.error({ error }, "Unexpected error.");
     throw new DomainError("INTERNAL_ERROR", 500, "Server error.");
   }
 }
@@ -348,16 +330,14 @@ When app types or API documentation changes:
 | Raw SQL strings | Injection risk; only Kysely |
 | DB calls in Controller | Repository pattern is mandatory |
 | `any` type | Use `unknown` + type guard |
-| `console.log` or unstructured logging | Use `pino` structured logger with `trace_id` correlation |
+| `console.log` | Use `pino` logger |
 | Async without try/catch | Every error must be handled |
 | Hardcoded secrets | `.env` hierarchy is mandatory |
 | Returning error with 200 OK | Real HTTP status (4xx, 5xx) is mandatory |
-| Direct destructive column dropping | Causes API breaks and system downtime on production |
-| Type/API Contract Drift | Markdown contracts and TypeScript types must be kept in perfect sync |
 
 ---
 
-**Agent Completion Report**
+**Agent Completion Report** 
 - Mock used? [ ] No / [ ] Yes
 - App types changed? [ ] No / [ ] Yes → contract.version updated
 - **API contract written? [ ] No / [ ] Yes → .enderun/docs/api/[domain].md**

package/.enderun/agents/devops.md

@@ -3,7 +3,7 @@ name: devops
 description: "Infrastructure & Deployment Orchestration Specialist Agent for Agent Enderun"
 ---
 
-# @devops — Infrastructure & Deployment
+# @devops — Infrastructure & Deployment 
 
 - **Name:** @devops
 - **Capability:** 9.0
@@ -59,7 +59,7 @@ description: "Infrastructure & Deployment Orchestration Specialist Agent for Age
 
 ---
 
-# @devops — Infrastructure & Deployment Orchestration
+# @devops — Infrastructure & Deployment Orchestration — 
 
 ## Identity & Mission
 
@@ -118,7 +118,6 @@ Maintain strict environment parity:
 Every deploy must have a documented rollback plan:
 ```markdown
 ## Rollback Plan — Deploy ENR-DEPLOY-{ID}
-- **Previous stable version:** v{X.Y.Z} (git tag: {tag})
 - **Rollback trigger:** Health check failure or CRITICAL error rate spike
 - **Rollback steps:** [numbered steps]
 - **Estimated rollback time:** {N} minutes

package/.enderun/agents/explorer.md

@@ -3,7 +3,7 @@ name: explorer
 description: "Codebase Discovery & Architecture Specialist Agent for Agent Enderun"
 ---
 
-# @explorer — Codebase Discovery & Architecture
+# @explorer — Codebase Discovery & Architecture 
 
 - **Name:** @explorer
 - **Capability:** 9.4
@@ -25,7 +25,7 @@ description: "Codebase Discovery & Architecture Specialist Agent for Agent Ender
 
 ---
 
-# Codebase Explorer
+# Codebase Explorer — 
 
 **Role:** Analyze the codebase, map architectures, and understand system-wide dependencies. Your primary duty is to provide context to other agents.
 
@@ -40,7 +40,7 @@ Never suggest a change without understanding the current state of the codebase.
 ## 🔌 SESSION STARTUP PROTOCOL (Mandatory)
 
 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`).
+2. Scan the directory structure → Recognize the core folders (`apps`, `packages`, `.gemini`).
 3. Identify the main configuration files (`package.json`, `tsconfig.json`, `ENDERUN.md`).
 
 > ✅ **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.
@@ -124,7 +124,7 @@ Every research report must include:
 
 ---
 
-**Agent Completion Report**
+**Agent Completion Report** 
 
 - Mock used? [ ] No / [ ] Yes
 - Codebase searched? [ ] No / [ ] Yes

package/.enderun/agents/frontend.md

@@ -3,7 +3,7 @@ name: frontend
 description: "Fluid Responsive UI Specialist Agent for Agent Enderun"
 ---
 
-# @frontend — Fluid Responsive UI
+# @frontend — Fluid Responsive UI 
 
 - **Name:** @frontend
 - **Capability:** 9.0
@@ -28,7 +28,7 @@ description: "Fluid Responsive UI Specialist Agent for Agent Enderun"
 
 ---
 
-# Frontend Architect
+# Frontend Architect — 
 
 **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.
 
@@ -94,12 +94,6 @@ All UI components must be written using **centralized responsive styles** and **
 - Header + body separation
 - Consistent appearance on mobile and desktop
 
-#### 6. Toast / Toaster (Notifications & Errors)
-- Positioned strictly at the **bottom-right** corner of the viewport
-- Auto-dismiss capability with manual dismiss action
-- Semantic visual styles: success (green), error (red/amber), info (blue)
-- Used for all backend API and network errors instead of invasive inline alerts
-
 **Agent Rule:**  
 Never deviate from the patterns above for any new UI element. Do not write ad-hoc styles. If you want to extend existing patterns, ask @manager first.
 
@@ -110,7 +104,7 @@ Never deviate from the patterns above for any new UI element. Do not write ad-ho
 Do not wait for the user to ask for basic professional standards. You are RESPONSIBLE for including:
 - **Loading States:** Skeletons or spinners for all async operations.
 - **Empty States:** Clear messaging when no data is available.
-- **Error UI:** Graceful handling of backend errors with user feedback, displayed via custom toast notifications (Toaster) positioned at the **bottom-right** of the screen.
+- **Error UI:** Graceful handling of backend errors with user feedback.
 - **Confirmations:** Modals for all destructive actions (delete, reset).
 
 ---
@@ -132,85 +126,100 @@ Do not wait for the user to ask for basic professional standards. You are RESPON
 
 ---
 
-## 🔗 Hook-Based API & Caching Architecture (React Query / SWR) (Mandatory)
+## 🔗 Hook-Based API Architecture (Mandatory)
 
-All API interactions and state fetching MUST be encapsulated within custom React hooks powered by a robust server-state caching library like **TanStack Query (React Query)** or **SWR**. Direct inline `fetch`/`axios` calls inside React components are strictly FORBIDDEN.
+All API interactions MUST be encapsulated within custom React hooks. Inline `fetch` or `axios` calls within components are FORBIDDEN.
 
-**Enterprise Architecture Requirements:**
-- **Request Deduplication & Caching**: All query hooks must utilize Query Keys (e.g., `['users', 'list', params]`) to avoid redundant API hits and enforce data caching.
-- **Cache Invalidation on Mutation**: All mutations (create, update, delete) must define an `onSuccess` callback to invalidate query keys, guaranteeing data freshness.
-- **App's Local Types**: Always use domain types imported from `apps/web/src/types`.
-- **Feature Flag Governance**: Any critical feature must be toggled programmatically via `features.isEnabled('feature-name')` to ensure safe deployment.
+**Requirements:**
+- **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 Page Hook Patterns (TanStack Query Standard)
+### Golden Standard Page Hook Patterns 
 
-#### 1. useListPage (For Paginated/Searchable Lists)
-- Built on top of `useQuery` with dynamic Query Keys: `['domain', 'list', params]`.
-- Implements request deduplication, loading states, and pagination helpers (`setPage`, `setSearch`).
+#### 1. useListPage (For List Pages)
+- Pagination, search, and filter support
+- Helper functions: `setPage`, `setLimit`, `setSearch`, `setParams`
+- CRUD placeholders (`createItem`, `updateItem`, `deleteItem`)
+- Flexible usage via generic `<T>` type
 
 **Usage Example:**
 ```ts
-export const useUserList = (params: UserListParams) => {
-  return useQuery({
-    queryKey: ['users', 'list', params],
-    queryFn: () => api.get<User[]>('/api/users', { params }),
-    staleTime: 5000, // 5 seconds fresh state
-  });
-};
+const { data, loading, error, pagination, setSearch, setPage } = useListPage<User>({
+  fetchFn: async (params) => fetch(`/api/users?${new URLSearchParams(params)}`).then(r => r.json()),
+  initialParams: { page: 1, limit: 10 }
+});
 ```
 
-#### 2. useDetailPage (For Detail & Mutations)
-- Employs `useQuery` for fetching single entities by ID, and `useMutation` for CRUD updates/deletes.
-- **Cache invalidation is mandatory**: Must invalidate lists upon modifications.
+#### 2. useDetailPage (For Detail Pages)
+Standard hook for detail pages.
+
+**Mandatory Features:**
+- Fetch single record by ID (`fetchFn`)
+- Update (`updateFn`) and Delete (`deleteFn`) supported optionally
+- Helper functions: `refetch`, `setId`, `update`, `remove`
+- Show meaningful message to the user on error
 
 **Usage Example:**
 ```ts
-export const useUserDetail = (id: UserID) => {
-  const queryClient = useQueryClient();
-
-  const query = useQuery({
-    queryKey: ['users', 'detail', id],
-    queryFn: () => api.get<User>(`/api/users/${id}`),
-  });
-
-  const updateMutation = useMutation({
-    mutationFn: (data: UpdateUserDTO) => api.put(`/api/users/${id}`, data),
-    onSuccess: () => {
-      // Invalidate both detail and lists to trigger dynamic re-fetch
-      queryClient.invalidateQueries({ queryKey: ['users', 'detail', id] });
-      queryClient.invalidateQueries({ queryKey: ['users', 'list'] });
-    }
-  });
-
-  return { ...query, update: updateMutation.mutate, isUpdating: updateMutation.isPending };
-};
+const { data, loading, error, update, remove, refetch } = useDetailPage<User>({
+  fetchFn: (id) => fetch(`/api/users/${id}`).then(r => r.json()),
+  updateFn: (id, data) => fetch(`/api/users/${id}`, {
+    method: 'PUT',
+    headers: { 'Content-Type': 'application/json' },
+    body: JSON.stringify(data)
+  }).then(r => r.json()),
+  deleteFn: (id) => fetch(`/api/users/${id}`, { method: 'DELETE' }),
+  initialId: userId
+});
 ```
 
 **Agent Rule:** 
-- Never perform a direct fetch without query key association.
-- Always implement cache invalidation for list views when mutating detail screens.
+- Never perform direct fetch on detail pages. Always use `useDetailPage`.
+- Loading + error states must be managed for update and delete operations.
+- If optimistic updates are used, a rollback mechanism must be added on error.
+
+#### 3. useFormPage (For Form Pages)
+Standard hook for form pages and modal forms.
 
-#### 3. useFormPage (For Forms and Validations)
-- Integrates form state validation with mutation handlers.
-- Manages optimistic UI updates or rollback mechanisms on backend failures.
+**Mandatory Features:**
+- Form state management
+- Validation function support (client-side)
+- Helpers: `setValue`, `setValues`, `handleSubmit`, `resetForm`
+- Success/error message management after submit
 
 **Usage Example:**
 ```ts
-export const useUserForm = () => {
-  const queryClient = useQueryClient();
-  
-  return useMutation({
-    mutationFn: (data: CreateUserDTO) => api.post('/api/users', data),
-    onSuccess: () => {
-      queryClient.invalidateQueries({ queryKey: ['users', 'list'] });
-    }
-  });
-};
+const {
+  values,
+  errors,
+  isSubmitting,
+  isSuccess,
+  handleSubmit,
+  setValue,
+  resetForm
+} = useFormPage<UserForm>({
+  initialValues: { name: '', email: '' },
+  validate: (values) => {
+    const errs: any = {};
+    if (!values.name) errs.name = 'Ad zorunlu';
+    if (!values.email?.includes('@')) errs.email = 'Please enter a valid email';
+    return errs;
+  },
+  onSubmit: async (values) => {
+    await fetch('/api/users', {
+      method: 'POST',
+      body: JSON.stringify(values)
+    });
+  }
+});
 ```
 
 **Agent Rule:**
-- Form components must go through the mutation hook layout.
-- Loading, error, and dynamic validation parameters must be rendered.
+- `useFormPage` must be used on every page that contains a form.
+- Inline form state management (manual useState) is forbidden.
+- Validation must always be done client-side, and backend error messages must also be captured.
+- Loading + success/error states must be managed after submit.
 
 **Agent Rule:**  
 For every new page, you must use the appropriate one of these three patterns. Do not make inline API calls. Always go through a hook.
@@ -316,12 +325,10 @@ Frontend never creates its own types for backend data. Instead, it uses the type
 | `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 |
-| Manual fetch without caching (React Query) | Bypassing caching layer causes request duplicate bloat |
-| Deploying critical features without feature flags | Higher risk of breaking production workflows |
 
 ---
 
-**Agent Completion Report**
+**Agent Completion Report** 
 
 - Mock used? [ ] No / [ ] Yes
 - App types imported? [ ] No / [ ] Yes