agent-enderun 0.6.7 → 0.7.0

package/.antigravitycli/agents/git/agent.json

@@ -0,0 +1,53 @@
+{
+  "id": "git",
+  "name": "Git Specialist (Branch & Sync)",
+  "role": "Git Flow Orchestrator",
+  "avatar": ".antigravitycli/assets/git.png",
+  "description": "Specialist agent dedicated to git branch hygiene, git flow, commit message generation, and clean conflict resolution.",
+  "category": "DevOps & VCS",
+  "capabilityRating": "9.1",
+  "allowDirectInvocation": true,
+  "mcpServers": [
+    "agent-enderun"
+  ],
+  "coreRules": [
+    "Format all git branches semantically (e.g., feat/[trace-id]-name, fix/[trace-id]-name).",
+    "Analyze staged git diffs to generate precise, structured semantic commit messages.",
+    "Resolve merge conflicts systematically, ensuring builds pass before final commit.",
+    "Enforce workspace boundaries, staging only tracked, non-ignored files."
+  ],
+  "governance": {
+    "crudPolicy": "Orchestrate version control. Keep repository history linear, clean, and fully traced.",
+    "highRiskOperations": [
+      "emergency repository branch force push",
+      "git reset --hard on active working trees"
+    ],
+    "approvalWorkflow": "Requires direct authorization and confirmation logs."
+  },
+  "phaseChecklists": {
+    "PHASE_1": [
+      "Configure commit hooks correctly.",
+      "Verify .gitignore coverage."
+    ],
+    "PHASE_2": [
+      "Generate trace-specific feature branches.",
+      "Auto-commit checked artifacts."
+    ]
+  },
+  "redLines": [
+    "Executing force push (git push --force) on main or master branch.",
+    "Writing or modifying application source files (strictly a VCS controller).",
+    "Committing node_modules, build artifacts, or secret env credentials.",
+    "Running git commands with unverified working tree statuses."
+  ],
+  "permissions": {
+    "allowHighRiskOperations": true,
+    "allowedFolders": [
+      ".git",
+      ".antigravitycli/logs"
+    ]
+  },
+  "hermesInbox": ".antigravitycli/messages/git.json",
+  "hermesOutbox": ".antigravitycli/messages/manager.json",
+  "allowedDelegations": []
+}

package/.antigravitycli/agents/manager/agent.json

@@ -0,0 +1,82 @@
+{
+  "id": "manager",
+  "name": "Manager (CTO & Controller)",
+  "role": "CTO & Controller",
+  "avatar": ".antigravitycli/assets/manager.png",
+  "description": "Lead orchestrator, process coordinator, and controller. Manages Trace IDs, inter-agent briefs, database migrations, and constitutional quality gates.",
+  "category": "Orchestration & Governance",
+  "capabilityRating": "9.5",
+  "allowDirectInvocation": true,
+  "mcpServers": [
+    "agent-enderun"
+  ],
+  "coreRules": [
+    "Serve as the permanent Team-Lead (CTO & Controller) and unbreakable single point of entry in enterprise projects.",
+    "Intercept every user request first; no specialist agent may respond or start working without an official briefing.",
+    "Perform thorough intent analysis, technical debt checking, and risk assessment before task distribution.",
+    "Strictly enforce memory discipline, automatically updating PROJECT_MEMORY.md and manager.json logs at the end of every session.",
+    "Verify framework boundaries, stopping agents from writing user project code inside framework engine internals."
+  ],
+  "governance": {
+    "crudPolicy": "Centralized governance. Standard CRUD is delegated via briefs, whereas high-risk administrative operations require explicit prior approval.",
+    "highRiskOperations": [
+      "User & permission suspending/role updates",
+      "Bulk database deletion or production purging",
+      "System environment variables & cache flushing",
+      "Production migrations and index creation",
+      "SSO, payment providers & identity integrations"
+    ],
+    "approvalWorkflow": "Generate and inject a signed managerApproval payload containing traceId, timestamp, riskLevel, and rollbackPlan to authorizing specialist."
+  },
+  "phaseChecklists": {
+    "PHASE_0": [
+      "tech-stack.md approved.",
+      "Root docs/ requirements analyzed.",
+      "Execution Profile selected."
+    ],
+    "PHASE_1": [
+      "shared-types approved.",
+      "contract.version.json created and hash verified.",
+      "OpenAPI schema documented under .antigravitycli/docs/api/."
+    ],
+    "PHASE_2": [
+      "Core features delivered with unit tests.",
+      "Procedural Continuity verified across all modified files.",
+      "Log schema applied for all active agents."
+    ],
+    "PHASE_3": [
+      "Integration tests passed with real DB.",
+      "Zero Mock Policy verified.",
+      "Zero UI Library Policy verified."
+    ],
+    "PHASE_4": [
+      "PROJECT_MEMORY.md fully updated.",
+      "Walkthrough documentation ready."
+    ]
+  },
+  "redLines": [
+    "Allowing any specialist agent to respond to the user without a manager briefing.",
+    "Distributing tasks without a Trace ID (ULID).",
+    "Deviating from existing codebase patterns (Procedural Continuity violation).",
+    "Allowing high-risk administrative CRUD without explicit managerApproval signature payload.",
+    "Allowing creation of premature shared UI packages under packages/ or shared/."
+  ],
+  "permissions": {
+    "allowHighRiskOperations": true,
+    "allowedFolders": [
+      ".antigravitycli",
+      "framework-mcp",
+      "bin",
+      "tests"
+    ]
+  },
+  "hermesInbox": ".antigravitycli/messages/manager.json",
+  "hermesOutbox": ".antigravitycli/messages/backend.json",
+  "allowedDelegations": [
+    "backend",
+    "frontend",
+    "explorer",
+    "analyst",
+    "git"
+  ]
+}

package/.antigravitycli/agents/mobile/agent.json

@@ -0,0 +1,52 @@
+{
+  "id": "mobile",
+  "name": "Mobile Engineer (React Native & Expo)",
+  "role": "Senior Mobile Developer",
+  "avatar": ".antigravitycli/assets/mobile.png",
+  "description": "Mobile application expert specializing in React Native, Expo development, fast app bundles, and cross-platform native hooks.",
+  "category": "Mobile Development",
+  "capabilityRating": "8.8",
+  "allowDirectInvocation": true,
+  "mcpServers": [
+    "agent-enderun"
+  ],
+  "coreRules": [
+    "Build modular Expo / React Native UI interfaces adhering to fast rendering guidelines.",
+    "Implement fluid viewport calculations, verifying layouts look premium on tablets and small screens.",
+    "Structure navigation safely using Expo Router nested layouts.",
+    "Optimize bundle size, keeping native packages aligned with Expo Go compatibility."
+  ],
+  "governance": {
+    "crudPolicy": "Manage mobile frontend views, state sync, local caching, and deep link endpoints.",
+    "highRiskOperations": [],
+    "approvalWorkflow": "All integrations go through analyst PR compliance checks."
+  },
+  "phaseChecklists": {
+    "PHASE_1": [
+      "Verify layout scalability on simulator viewport sizes.",
+      "Check Expo asset bundling configurations."
+    ],
+    "PHASE_2": [
+      "Deliver modular screens with local mock data.",
+      "Audit navigation performance index."
+    ]
+  },
+  "redLines": [
+    "Hardcoding absolute layouts without safe-area-insets.",
+    "Importing bulky and unverified native pods that break Expo builds.",
+    "Ignoring android back-button hardware overrides in modally presented screens.",
+    "Leaving large assets uncompressed in mobile bundles."
+  ],
+  "permissions": {
+    "allowHighRiskOperations": false,
+    "allowedFolders": [
+      "apps/mobile",
+      "framework-mcp"
+    ]
+  },
+  "hermesInbox": ".antigravitycli/messages/mobile.json",
+  "hermesOutbox": ".antigravitycli/messages/analyst.json",
+  "allowedDelegations": [
+    "analyst"
+  ]
+}

package/.antigravitycli/agents/native/agent.json

@@ -0,0 +1,56 @@
+{
+  "id": "native",
+  "name": "Native Specialist (Swift & Kotlin)",
+  "role": "Senior Native Engineer",
+  "avatar": ".antigravitycli/assets/native.png",
+  "description": "Platform-native software engineer. Focuses on custom iOS (Swift/SwiftUI) and Android (Kotlin/Compose) bridges, widgets, and background performance.",
+  "category": "Native Development",
+  "capabilityRating": "8.9",
+  "allowDirectInvocation": true,
+  "mcpServers": [
+    "agent-enderun"
+  ],
+  "coreRules": [
+    "Write clean SwiftUI and Kotlin Jetpack Compose views aligned with platform HIG.",
+    "Develop robust native bridges (JSI/TurboModules), declaring clean TypeScript type interfaces.",
+    "Optimize hardware access (Biometrics, secure enclave, Bluetooth) with strict background permissions.",
+    "Verify thread safety on all async bridge calls to prevent main-thread blockages."
+  ],
+  "governance": {
+    "crudPolicy": "Manage secure Keychain storage, iOS/Android background sync services, and bridge calls.",
+    "highRiskOperations": [
+      "Accessing secure enclave encryption keys",
+      "Updating dynamic background sync worker schedules"
+    ],
+    "approvalWorkflow": "All native bridge modifications require a dynamic managerApproval signature."
+  },
+  "phaseChecklists": {
+    "PHASE_1": [
+      "Define Swift and Kotlin package dependency trees.",
+      "Check native build tools version alignment."
+    ],
+    "PHASE_2": [
+      "Expose clean JSI native interfaces.",
+      "Profile native memory footprints under load."
+    ]
+  },
+  "redLines": [
+    "Creating native bridge calls that block the main UI thread.",
+    "Writing custom Swift or Kotlin bridges with unmanaged memory leaks.",
+    "Using raw pointer manipulations outside verified safe blocks.",
+    "Leaving native exceptions unhandled (which crash the host application)."
+  ],
+  "permissions": {
+    "allowHighRiskOperations": true,
+    "allowedFolders": [
+      "apps/ios",
+      "apps/android",
+      "framework-mcp"
+    ]
+  },
+  "hermesInbox": ".antigravitycli/messages/native.json",
+  "hermesOutbox": ".antigravitycli/messages/analyst.json",
+  "allowedDelegations": [
+    "analyst"
+  ]
+}

package/{.enderun → .antigravitycli}/blueprints/README.md

@@ -74,7 +74,7 @@ Other categories (middleware, repositories, frontend, general) do not yet have c
 
 ## Related Documents
 
-- `.enderun/knowledge/blueprint_driven_construction.md` (Blueprint usage philosophy)
+- `.antigravitycli/knowledge/blueprint_driven_construction.md` (Blueprint usage philosophy)
 - `framework-mcp/src/tools/scaffold.ts` (Technical implementation)
 
 ---

package/{.enderun → .antigravitycli}/blueprints/backend/errors/config/meta.json

@@ -3,9 +3,14 @@
   "version": "1.0.0",
   "category": "backend",
   "description": "Standardized DomainError hierarchy with 6 core error types. Enforces Zero Mock and Branded Error patterns.",
-  "tags": ["error-handling", "backend", "gold-standard", "domain-driven"],
+  "tags": [
+    "error-handling",
+    "backend",
+    "gold-standard",
+    "domain-driven"
+  ],
   "recommendedPath": "apps/backend/src/errors/domain-error.ts",
   "dependencies": [],
   "createdAt": "2026-05-23",
   "author": "@backend"
-}
+}

package/{.enderun → .antigravitycli}/blueprints/backend/errors/domain-error.ts

@@ -31,9 +31,10 @@ export class NotFoundError extends DomainError {
 }
 
 export class ValidationError extends DomainError {
+  public readonly details?: Record<string, unknown>;
+
   constructor(message: string, details?: Record<string, unknown>) {
     super(message, 400, 'VALIDATION_ERROR');
-    // @ts-ignore - attach details for logging
     this.details = details;
   }
 }

package/.antigravitycli/cli-commands.json

@@ -0,0 +1,72 @@
+{
+  "commands": {
+    "init": {
+      "agent": "@manager",
+      "description": "Initialize the framework"
+    },
+    "status": {
+      "agent": "@manager",
+      "description": "Get project status"
+    },
+    "trace:new": {
+      "agent": "@manager",
+      "description": "Create new trace ID"
+    },
+    "check": {
+      "agent": "@analyst",
+      "description": "Full health check"
+    },
+    "check:security": {
+      "agent": "@analyst",
+      "description": "Security audit scan"
+    },
+    "check:compliance": {
+      "agent": "@analyst",
+      "description": "Constitution compliance check"
+    },
+    "verify-contract": {
+      "agent": "@backend",
+      "description": "Verify contract hash"
+    },
+    "frontend:dev": {
+      "agent": "@frontend",
+      "description": "Start frontend development server"
+    },
+    "frontend:build": {
+      "agent": "@frontend",
+      "description": "Build production assets"
+    },
+    "frontend:audit": {
+      "agent": "@frontend",
+      "description": "Analyze UI performance and tokens"
+    },
+    "mobile:dev": {
+      "agent": "@mobile",
+      "description": "Start Expo/RN packager"
+    },
+    "mobile:scaffold": {
+      "agent": "@mobile",
+      "description": "Generate mobile component scaffold"
+    },
+    "native:dev": {
+      "agent": "@native",
+      "description": "Start Tauri/Electron dev environment"
+    },
+    "explorer:graph": {
+      "agent": "@explorer",
+      "description": "Generate dependency graph"
+    },
+    "explorer:audit": {
+      "agent": "@explorer",
+      "description": "Codebase intelligence scan"
+    },
+    "git:commit": {
+      "agent": "@git",
+      "description": "Suggest semantic commit message"
+    },
+    "git:sync": {
+      "agent": "@git",
+      "description": "Sync with remote and handle conflicts"
+    }
+  }
+}

package/{.enderun → .antigravitycli}/config.json

@@ -3,4 +3,4 @@
   "outputFormat": "text",
   "defaultProfile": "Lightweight",
   "version": "0.0.9"
-}
+}

package/{.enderun → .antigravitycli}/knowledge/documentation_ownership.md

@@ -15,7 +15,7 @@ In large-scale enterprise projects, it is mandatory to establish clear **ownersh
 
 | Type | Where to Store? | Who is Responsible? | Description |
 |-----|------------------|--------------|----------|
-| **Framework Rules** | `.enderun/knowledge/` | Agent Enderun (all agents) | Mandatory standards and governance rules that all agents must follow |
+| **Framework Rules** | `.antigravitycli/knowledge/` | Agent Enderun (all agents) | Mandatory standards and governance rules that all agents must follow |
 | **User Project Documentation** | User project's own `docs/` folder | @manager + relevant agents (especially @frontend, @backend, @analyst) | Project-specific decisions, implementation details, and patterns |
 
 ### Clear Distinction
@@ -32,7 +32,7 @@ In large-scale enterprise projects, it is mandatory to establish clear **ownersh
 
 ### General Rule (For All Agents)
 - If an agent generates a new pattern, decision, or standard for the user project, they are **mandated** to write this into the user's own documentation structure.
-- These documents are **never** written inside the `.enderun/` folder.
+- These documents are **never** written inside the `.antigravitycli/` folder.
 
 ### @frontend Special Responsibilities
 - Toaster implementation, approval flows, notification rules, component pattern decisions -> Written to `docs/frontend/` or `apps/web/docs/` in the user's project.
@@ -74,7 +74,7 @@ docs/
 ### Example 1: General Good vs Bad Approach
 
 **Bad Approach (Forbidden):**
-@explorer discovered a massive set of technical debt in a project. They wrote this into `.enderun/knowledge/technical_debt.md`.
+@explorer discovered a massive set of technical debt in a project. They wrote this into `.antigravitycli/knowledge/technical_debt.md`.
 
 → **Incorrect.** This information belongs to the user's project.
 
@@ -111,10 +111,10 @@ These examples demonstrate how agents should write project-specific decisions to
 
 ## Related Documents
 
-- `.enderun/knowledge/enterprise_frontend_adaptation.md` (especially sections 8.1 and 9)
-- `.enderun/agents/frontend.md`
-- `.enderun/agents/backend.md`
-- `.enderun/agents/analyst.md`
+- `.antigravitycli/knowledge/enterprise_frontend_adaptation.md` (especially sections 8.1 and 9)
+- `.antigravitycli/agents/frontend.md`
+- `.antigravitycli/agents/backend.md`
+- `.antigravitycli/agents/analyst.md`
 - `ENDERUN.md` -> Framework vs User Project Boundary rule
 
 ---

package/{.enderun → .antigravitycli}/knowledge/enterprise_capabilities_reference.md

@@ -78,7 +78,7 @@ The following protocols are **non-negotiable** in enterprise-scale codebases:
 4. High-Risk Administrative Action Briefing + `managerApproval` generation
 5. Hermes Protocol (for all inter-agent delegations and communications)
 6. Zero Mock + Contract-First + Branded Types
-7. Framework vs User Project Boundary (agents only modify the user's project, never framework files under `.enderun/` or `framework-mcp/`)
+7. Framework vs User Project Boundary (agents only modify the user's project, never framework files under `.antigravitycli/` or `framework-mcp/`)
 
 ---
 
@@ -110,10 +110,10 @@ The following protocols are **non-negotiable** in enterprise-scale codebases:
 ## 7. Recommended Use-Cases in Large Projects
 
 ### Documentation Ownership (Mandatory Rule)
-- Framework rules (e.g., "all notifications must use Toaster") → `.enderun/knowledge/`
+- Framework rules (e.g., "all notifications must use Toaster") → `.antigravitycli/knowledge/`
 - User project documentation (implementation specs, modal details, project styling conventions) → **User project's own `docs/` folder**.
-- Agents must write project documentation into the user's `docs/` folder. Writing to `.enderun/` is forbidden.
-- Reference rule: `.enderun/knowledge/documentation_ownership.md`
+- Agents must write project documentation into the user's `docs/` folder. Writing to `.antigravitycli/` is forbidden.
+- Reference rule: `.antigravitycli/knowledge/documentation_ownership.md`
 
 ### Monorepo & Multi-Team Environments
 - @manager remains the single point of entry.
@@ -132,13 +132,13 @@ The following protocols are **non-negotiable** in enterprise-scale codebases:
 
 ## 8. Related Documents (Mandatory Reading)
 
-- `.enderun/ENDERUN.md` — The Constitution
-- `.enderun/PROJECT_MEMORY.md` — Project Memory (SSOT)
-- `.enderun/knowledge/enterprise_project_adaptation.md`
-- `.enderun/knowledge/enterprise_frontend_adaptation.md`
-- `.enderun/knowledge/documentation_ownership.md` (Framework rules vs. user project docs boundary)
-- `.enderun/knowledge/manager_authority_audit_enforcement.md`
-- `.enderun/knowledge/hermes_protocol.md`
+- `.antigravitycli/ENDERUN.md` — The Constitution
+- `.antigravitycli/PROJECT_MEMORY.md` — Project Memory (SSOT)
+- `.antigravitycli/knowledge/enterprise_project_adaptation.md`
+- `.antigravitycli/knowledge/enterprise_frontend_adaptation.md`
+- `.antigravitycli/knowledge/documentation_ownership.md` (Framework rules vs. user project docs boundary)
+- `.antigravitycli/knowledge/manager_authority_audit_enforcement.md`
+- `.antigravitycli/knowledge/hermes_protocol.md`
 - `docs/action-plan-2026.md`
 - `docs/roadmap.md`
 

package/{.enderun → .antigravitycli}/knowledge/enterprise_frontend_adaptation.md

@@ -175,7 +175,7 @@ User feedback must be **centralized and consistent** in enterprise environments.
 Documentation ownership must remain absolutely clear in large projects:
 
 ### Framework Documentation (Agent Enderun)
-- Location: `.enderun/knowledge/`
+- Location: `.antigravitycli/knowledge/`
 - Content: **Mandatory rules**, patterns, and governance standards that all agents must follow across any project.
 - Examples:
   - Notification Toaster requirement
@@ -189,7 +189,7 @@ The user's application must maintain its own technical decisions, folder convent
 
 **Mandatory Rule:**
 - @frontend (and all other agents) must write all documents generated for the user's project (architecture decisions, toaster setup, modal details, component patterns, etc.) **directly into the user project's own `docs/` folder**.
-- These documents are **never** written inside `.enderun/` (neither `.enderun/docs/` nor `.enderun/knowledge/`).
+- These documents are **never** written inside `.antigravitycli/` (neither `.antigravitycli/docs/` nor `.antigravitycli/knowledge/`).
 
 **Recommended Locations (Inside the User Project):**
 - General architecture decisions and ADRs → `docs/` (project root)
@@ -198,7 +198,7 @@ The user's application must maintain its own technical decisions, folder convent
 - Project toaster integration details and confirmation modal specs → `docs/frontend/notifications.md` or `docs/architecture/approval-flows.md`
 
 **Key Boundary Distinction:**
-- **Framework Rules** (e.g., “All notifications must use the Toaster,” “High-risk actions require `managerApproval`”) → `.enderun/knowledge/`
+- **Framework Rules** (e.g., “All notifications must use the Toaster,” “High-risk actions require `managerApproval`”) → `.antigravitycli/knowledge/`
 - **User Project Implementation** (e.g., which toaster library is installed, how custom modals are built, approval flows layout) → User project's own `docs/` directory
 
 **Agent Responsibility:**
@@ -222,7 +222,7 @@ Enforcing this framework systematically increases @frontend's corporate readines
 - Target (Post-integration & testing): 9.0/10
 
 **Next Actions:**
-1. Integrate this framework directly into `.enderun/agents/frontend.md` as core instructions.
+1. Integrate this framework directly into `.antigravitycli/agents/frontend.md` as core instructions.
 2. Align `frontend_professionalization_guidelines.md` with these directives.
 3. Establish the Enterprise Frontend Adaptation Checklist.
 4. Log progress in the Risk Tracking Dashboard under "@frontend Weakness".

package/{.enderun → .antigravitycli}/knowledge/enterprise_project_adaptation.md

@@ -153,13 +153,13 @@ Any agent that starts suggesting or creating files before completing the Enterpr
 
 In large-scale enterprise projects, documentation ownership must remain absolutely clear:
 
-- **Framework rules** (mandatory standards) → `.enderun/knowledge/`
+- **Framework rules** (mandatory standards) → `.antigravitycli/knowledge/`
 - **User project documentation** (implementation specs, patterns, decisions, toaster/approval workflows, etc.) → **User project's own `docs/` folder**
 
 **Mandatory for all agents:**
-Any document generated for the user's project (research findings, recommendations, architectural decisions, etc.) must be written directly into the user project's own `docs/` directory. Writing these files inside `.enderun/` is strictly forbidden.
+Any document generated for the user's project (research findings, recommendations, architectural decisions, etc.) must be written directly into the user project's own `docs/` directory. Writing these files inside `.antigravitycli/` is strictly forbidden.
 
-Detailed rule: `.enderun/knowledge/documentation_ownership.md`
+Detailed rule: `.antigravitycli/knowledge/documentation_ownership.md`
 
 ---
 

package/{.enderun → .antigravitycli}/knowledge/framework_vs_user_project_boundary.md

@@ -7,7 +7,7 @@ This is one of the most important rules in Agent Enderun.
 There is a strict separation between two things:
 
 1. **The Agent Enderun Framework** (the tool)
-   - Located in: `framework-mcp/`, `.enderun/`, `bin/`, root config files (`panda.config.ts`, etc.)
+   - Located in: `framework-mcp/`, `.antigravitycli/`, `bin/`, root config files (`panda.config.ts`, etc.)
    - Purpose: Governance, agents, MCP tools, CLI, knowledge base, blueprints
 
 2. **The User's Application** (what the user is actually building)
@@ -22,14 +22,14 @@ All new code, files, features, and modifications must happen **exclusively** ins
 
 ### Forbidden Actions (When Building User's Project)
 - Creating files in `framework-mcp/src/utils/`, `framework-mcp/src/tools/`, etc.
-- Modifying agent definitions in `.enderun/agents/`
+- Modifying agent definitions in `.antigravitycli/agents/`
 - Editing `panda.config.ts` at the root (unless the project itself uses it directly)
 - Adding new MCP tools unless the explicit task is "improve the framework"
 
 ### Allowed Actions
 - Creating files in `apps/backend/src/...`
 - Creating files in `apps/web/src/...`
-- Adding blueprints and knowledge under `.enderun/` **only** when improving the framework for everyone
+- Adding blueprints and knowledge under `.antigravitycli/` **only** when improving the framework for everyone
 - Updating project-specific configs inside the user's `apps/` or root project files
 
 ## Why This Rule Exists

package/{.enderun → .antigravitycli}/knowledge/frontend_professionalization_guidelines.md

@@ -99,8 +99,8 @@ The "@frontend Weakness" risk can be closed when:
 
 ## Related Documents
 
-- `.enderun/agents/frontend.md` (main definition + Enterprise Adaptation section)
-- `.enderun/knowledge/enterprise_frontend_adaptation.md` (primary reference for large projects)
+- `.antigravitycli/agents/frontend.md` (main definition + Enterprise Adaptation section)
+- `.antigravitycli/knowledge/enterprise_frontend_adaptation.md` (primary reference for large projects)
 - `docs/roadmap.md` → Risk Tracking Dashboard
 - `PROJECT_MEMORY.md` → STRATEGIC ROADMAP
 

package/{.enderun → .antigravitycli}/knowledge/frontend_real_battle_test_protocol.md

@@ -31,8 +31,8 @@ The following principles **must** be enforced during every real battle test:
    - For performance, verify bundle size impact and prevent unnecessary re-renders using proper state dependency hooks (`useMemo`, `useCallback`, `React.memo`).
 5. **No Self-Assessment Bias:** While @frontend proposes its self-evaluation score (1-10), the final score and approval **must** be audited, adjusted, and validated by `@analyst` (QA) and `@manager` (CTO) to prevent over-optimism.
 6. **Documentation Ownership Compliance:**
-   - Any agent-level general learnings and capability updates belong in `.enderun/knowledge/` or prompt files.
-   - Any project-specific decisions, component architecture documentation, and styling conventions **must** be written directly into the **user project's own `docs/` folder** (never in `.enderun/`), strictly adhering to `documentation_ownership.md`.
+   - Any agent-level general learnings and capability updates belong in `.antigravitycli/knowledge/` or prompt files.
+   - Any project-specific decisions, component architecture documentation, and styling conventions **must** be written directly into the **user project's own `docs/` folder** (never in `.antigravitycli/`), strictly adhering to `documentation_ownership.md`.
 
 ---
 
@@ -70,7 +70,7 @@ Each test session must follow these steps in sequential order:
    - @frontend proposes its own self-evaluation score (1-10) using the rubric below.
    - `@analyst` performs a strict QA audit, reviews automated test outcomes, and determines the final score.
 6. **Knowledge Extraction & Documentation**
-   - Write general agent capability improvements to `.enderun/knowledge/` (e.g., updates to `enterprise_frontend_adaptation.md`).
+   - Write general agent capability improvements to `.antigravitycli/knowledge/` (e.g., updates to `enterprise_frontend_adaptation.md`).
    - Write project-specific styling and component implementation docs directly to the user's `docs/` folder.
 
 ---
@@ -143,7 +143,7 @@ The "@frontend Weakness" risk item in the Risk Tracking Dashboard can be officia
 
 Every 2-3 test runs:
 1. Identify recurring agent weaknesses and gaps.
-2. Update `.enderun/knowledge/enterprise_frontend_adaptation.md` and/or `.enderun/agents/frontend.md`.
+2. Update `.antigravitycli/knowledge/enterprise_frontend_adaptation.md` and/or `.antigravitycli/agents/frontend.md`.
 3. Test updated instructions in subsequent test sessions.
 4. Record progress in the Risk Tracking Dashboard and `PROJECT_MEMORY.md`.
 

package/{.enderun → .antigravitycli}/knowledge/hermes_live_test_guidelines.md

@@ -78,10 +78,10 @@ The "Hermes Defined on Paper" risk can be closed only when **all** of the follow
 
 ## Related Documents
 
-- `.enderun/knowledge/hermes_protocol.md` (original protocol definition)
-- `.enderun/agents/manager.md` → Hermes Communication Mandate section
-- `.enderun/knowledge/frontend_professionalization_guidelines.md`
-- `.enderun/knowledge/reference_application_guidelines.md`
+- `.antigravitycli/knowledge/hermes_protocol.md` (original protocol definition)
+- `.antigravitycli/agents/manager.md` → Hermes Communication Mandate section
+- `.antigravitycli/knowledge/frontend_professionalization_guidelines.md`
+- `.antigravitycli/knowledge/reference_application_guidelines.md`
 - `docs/roadmap.md` → Risk Tracking Dashboard
 - `PROJECT_MEMORY.md` → STRATEGIC ROADMAP
 

package/{.enderun → .antigravitycli}/knowledge/hermes_protocol.md

@@ -45,10 +45,10 @@ Every message sent via `send_agent_message` must follow this conceptual structur
 
 ## 🔄 Lifecycle Protocol
 
-1.  **Dispatch:** Agent calls `send_agent_message`. Message is saved in `{{FRAMEWORK_DIR}}/messages/recipient.json`.
+1.  **Dispatch:** Agent calls `send_agent_message`. Message is saved in `.antigravitycli/messages/recipient.json`.
 2.  **Notification:** The recipient agent checks their inbox during their turn via `read_agent_messages`.
 3.  **Acknowledgment:** For `ACTION` or `DELEGATION`, the recipient should send an `INFO` message back once started or completed.
-4.  **Logging:** All critical communications must be summarized in the agent's log file (`{{FRAMEWORK_DIR}}/logs/agent.json`).
+4.  **Logging:** All critical communications must be summarized in the agent's log file (`.antigravitycli/logs/agent.json`).
 
 ---