agent-enderun 0.7.1 → 0.7.5

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

@@ -1,53 +0,0 @@
-{
-  "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

@@ -1,82 +0,0 @@
-{
-  "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

@@ -1,52 +0,0 @@
-{
-  "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

@@ -1,56 +0,0 @@
-{
-  "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/.antigravitycli/blueprints/README.md

@@ -1,82 +0,0 @@
-# Blueprints
-
-This directory stores **Gold Standard** reusable patterns and architectural capabilities for Agent Enderun.
-
-## Purpose
-
-Blueprints allow agents to store and reuse high-quality, repeatable architectural patterns, error systems, UI components, or business logic structures.
-
-Goals:
-- Standardize recurring high-quality solutions
-- Enable agents to work from proven patterns instead of starting from scratch
-- Raise quality at the framework level, not just per-project
-
-## How It Works
-
-Agents use the following tools to work with blueprints:
-
-- `list_blueprints` → Lists all available blueprints
-- `instantiate_blueprint` → Copies a blueprint into the user's project
-- `save_as_blueprint` → Saves a new high-quality solution as a blueprint
-
-## Recommended Folder Structure
-
-For a clean and maintainable structure, the following format is recommended:
-
-```
-blueprints/
-├── backend/
-│   ├── errors/
-│   │   ├── config/
-│   │   │   └── meta.json          # Blueprint metadata
-│   │   └── domain-error.ts        # Source code
-│   └── ...
-├── frontend/
-│   └── ...
-├── general/
-│   └── ...
-└── README.md
-```
-
-**Mandatory Discipline Rule:**  
-Categories without actual content **must not** create folders on disk. Empty folders are only listed as plans in this README. When a new blueprint is added, the relevant folder + `config/meta.json` + source code are added together.
-
-Each blueprint folder contains:
-- `config/meta.json` → Blueprint metadata (description, category, version, recommendedPath, etc.)
-- Relevant source code files (at least 1 file)
-
-## Maintenance and Discipline Rules (When Content Is Low)
-
-This folder must **always** be kept clean and professional. Even with low content, clutter or empty folders are not allowed.
-
-- Only blueprints that have actually been added and are working exist as folders on disk.
-- Planned categories (middleware, repositories, frontend/components, etc.) are **only listed as plans in this README**; no folders are created on disk.
-- Every time a new blueprint is added, this README and related knowledge documents are updated.
-- Empty folders are cleaned up or never created (structure governance rule).
-
-## Current Blueprints
-
-Currently there is only 1 mature example:
-
-- `backend/errors/` → DomainError-based error system (Gold Standard)
-  - `config/meta.json`
-  - `domain-error.ts`
-
-Other categories (middleware, repositories, frontend, general) do not yet have content, so no folders exist on disk.
-
-## Rules for Adding New Blueprints
-
-1. Only truly high-quality and repeatable solutions should be saved as blueprints.
-2. Every blueprint must have a short description inside `config/meta.json`.
-3. Blueprints should be as framework-agnostic as possible (easy to adapt when copied).
-4. Before adding a new blueprint, check with `list_blueprints` whether something similar already exists.
-5. **When adding a new blueprint, the folder + config/meta.json + at least one source code file must be added together.** Empty folders are not created.
-
-## Related Documents
-
-- `.antigravitycli/knowledge/blueprint_driven_construction.md` (Blueprint usage philosophy)
-- `framework-mcp/src/tools/scaffold.ts` (Technical implementation)
-
----
-
-**Note:** This folder must be dynamically grown by the agents. Even with low content, it must be kept **organized, documented, and disciplined** at all times (structure governance rule 2026-05-24 item 2).

package/.antigravitycli/blueprints/backend/errors/config/meta.json

@@ -1,16 +0,0 @@
-{
-  "name": "backend/errors/domain-error",
-  "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"
-  ],
-  "recommendedPath": "apps/backend/src/errors/domain-error.ts",
-  "dependencies": [],
-  "createdAt": "2026-05-23",
-  "author": "@backend"
-}

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

@@ -1,64 +0,0 @@
-/**
- * GOLD STANDARD BLUEPRINT
- * Category: backend/errors
- * Name: DomainError Hierarchy
- * Version: 1.0.0
- * Description: Standardized, typed error system for all backend services.
- * 
- * Usage:
- *   1. Copy this file to apps/backend/src/errors/domain-error.ts
- *   2. Create index.ts to re-export all error classes
- *   3. Import and use in controllers/services (never throw raw Error)
- */
-
-export abstract class DomainError extends Error {
-  public readonly statusCode: number;
-  public readonly code: string;
-
-  constructor(message: string, statusCode: number, code: string) {
-    super(message);
-    this.name = this.constructor.name;
-    this.statusCode = statusCode;
-    this.code = code;
-    Error.captureStackTrace(this, this.constructor);
-  }
-}
-
-export class NotFoundError extends DomainError {
-  constructor(resource: string) {
-    super(`${resource} not found`, 404, 'NOT_FOUND');
-  }
-}
-
-export class ValidationError extends DomainError {
-  public readonly details?: Record<string, unknown>;
-
-  constructor(message: string, details?: Record<string, unknown>) {
-    super(message, 400, 'VALIDATION_ERROR');
-    this.details = details;
-  }
-}
-
-export class UnauthorizedError extends DomainError {
-  constructor(message = 'Unauthorized') {
-    super(message, 401, 'UNAUTHORIZED');
-  }
-}
-
-export class ForbiddenError extends DomainError {
-  constructor(message = 'Forbidden') {
-    super(message, 403, 'FORBIDDEN');
-  }
-}
-
-export class ConflictError extends DomainError {
-  constructor(message: string) {
-    super(message, 409, 'CONFLICT');
-  }
-}
-
-export class InternalServerError extends DomainError {
-  constructor(message = 'Internal server error') {
-    super(message, 500, 'INTERNAL_ERROR');
-  }
-}

package/.antigravitycli/knowledge/README.md

@@ -1,22 +0,0 @@
-# Knowledge Base
-
-This directory is the **permanent enterprise knowledge** repository for Agent Enderun agents.
-
-## Content Rules
-- File names **must** be in kebab-case (`hermes-protocol.md`, `enterprise-project-adaptation.md`).
-- Every file must contain a clear title and "Version / Owner / Last Updated" metadata.
-- Knowledge should be as **practical and actionable** as possible (not just theory).
-
-## Important Files
-- `enterprise_project_adaptation.md` → Enterprise project entry protocol (EPDP)
-- `enterprise_frontend_adaptation.md` → Enterprise adaptation rules for frontend
-- `hermes_protocol.md` → Inter-agent communication standard
-- `manager_authority_audit_enforcement.md` → @manager authority audit rules
-- `hermes_live_test_guidelines.md` → Hermes test program
-
-## Usage
-Agents must search this directory first when conducting research or making decisions (using the `search_knowledge_base` tool).
-
-Newly discovered important patterns or rules must be written here.
-
-**Last Updated:** 24 May 2026

package/.antigravitycli/knowledge/database_governance_guidelines.md

@@ -1,118 +0,0 @@
-# Enterprise Database Governance and Performance Guidelines (DBA SOP)
-
-**Version:** v0.6.5 | **Ownership:** @backend & @dba Security Framework
-
-This document is the constitutional database ruleset establishing **Zero-Downtime DDL (schema migrations)**, **maximum query performance (Index Tuning)**, and **deadlock prevention strategies (Lock Management)** in applications running under the PostgreSQL + Kysely architecture. `@backend` executes these rules with 0 error tolerance when writing code, and `@analyst` actively audits them during code review.
-
----
-
-## ⚡ 1. INDEX OPTIMIZATION LAWS (INDEX TUNING)
-
-To ensure that queries do not exhaust the database and can respond to thousands of requests per second, index design cannot be left to chance.
-
-### 1.1 Foreign Key Index Obligation
-*   **Rule:** For every Foreign Key (FK) column defined, **it is mandatory to create a corresponding index**.
-*   **Rationale:** Prevents sequential scans on the target table during `JOIN` operations and when deleting data from the parent table (`ON DELETE CASCADE`).
-*   **Kysely/SQL Pattern:**
-    ```typescript
-    // Inside the migration file
-    await db.schema.createIndex('idx_orders_user_id')
-      .on('orders')
-      .column('user_id')
-      .execute();
-    ```
-
-### 1.2 Concurrent Indexing
-*   **Rule:** All indexes created on production databases **must be created using the `CONCURRENTLY` keyword**.
-*   **Rationale:** Standard index creation locks the target table completely for write operations (`ShareLock`). `CONCURRENTLY` builds the index in the background without locking the table.
-*   **Migration Rule:** When creating indexes concurrently, the migration process must run outside of a database transaction. In Kysely, this operation must be run `transaction-free`.
-
-### 1.3 Partial & Composite Indexes
-*   **Rule:** **Partial Indexes** must be used on tables using soft deletes (`deleted_at IS NOT NULL`) or when queries filter by a specific status.
-*   **Kysely Pattern:**
-    ```typescript
-    // An extremely fast and small index that scans only active records
-    await db.schema.createIndex('idx_active_users_email')
-      .on('users')
-      .column('email')
-      .where(sql`deleted_at IS NULL`)
-      .execute();
-    ```
-*   **Rule 2:** When creating composite indexes for multi-column searches like `WHERE a = x AND b = y`, the **column with the highest selectivity (high cardinality) must be placed on the far left**.
-
----
-
-## 🔒 2. DATABASE LOCK MANAGEMENT (LOCK MANAGEMENT)
-
-Incorrect lock management leads to connection pool exhaustion within seconds, causing a complete system crash (cascading failure).
-
-### 2.1 Transaction Boundaries and Golden Rules
-1.  **Zero Network Inside TX:** While a database transaction (`db.transaction()`) is active, **external API calls, sending emails, or file read/write operations are strictly forbidden**. A 1-second network latency causes locks in the database to be held for that second, clogging the entire system.
-2.  **Keep it Short Principle:** Transactions must only contain database write operations and must be `committed` as quickly as possible.
-
-### 2.2 Deadlock Prevention and Smart Query Design
-*   **Rule:** The use of `SELECT ... FOR UPDATE` (Row Lock) is forbidden except in high-urgency scenarios. When its use is mandatory, the query must be restricted with **`NOWAIT`** or **`SKIP LOCKED`** parameters to avoid entering the queue and causing deadlocks.
-*   **Kysely Pattern:**
-    ```typescript
-    // Instead of waiting in a queue and locking the system, throw an error or skip if locked
-    const job = await db.selectFrom('jobs')
-      .selectAll()
-      .where('status', '=', 'PENDING')
-      .limit(1)
-      .forUpdate()
-      .skipLocked() // OR .noWait()
-      .executeTakeFirst();
-    ```
-
-### 2.3 Timeout Safety
-Lock timeout parameters must be set before every session or heavy migration. This ensures that if a lock accumulation occurs in the background, the transaction cancels itself instead of locking up the system.
-```sql
-SET statement_timeout = '15s';
-SET lock_timeout = '5s';
-```
-
----
-
-## 🛡️ 3. SAFE SCHEMA TRANSITION LAWS (SAFE MIGRATIONS - DDL)
-
-To ensure zero-downtime during schema migrations on production environments, the following templates must be applied:
-
-### 3.1 NOT NULL Column Addition Procedure
-Adding a column containing a `NOT NULL` constraint directly to a production table causes PostgreSQL to lock the entire table. The safe procedure is:
-1.  Add the column as **nullable**.
-2.  Update the data in the background with default values (in batches).
-3.  Add the `NOT NULL` constraint to the column (this operation no longer creates a lock).
-
-### 3.2 Breaking Column/Table Changes - "Expand & Contract"
-Renaming a column or changing its data type directly on a live system is strictly forbidden. Instead, follow these 5 steps:
-```
-[Deployment 1 - EXPAND]
-Add the new column. Start dual-writing in the codebase (write to both old and new columns).
-
-[Deployment 2 - BACKFILL]
-Migrate legacy data from the old column to the new column in the background (Batch Update).
-
-[Deployment 3 - READ SWITCH]
-Redirect all read requests in the codebase to the new column.
-
-[Deployment 4 - STOP DUAL-WRITE]
-Completely stop writing to the old column.
-
-[Deployment 5 - CONTRACT]
-Delete the old column from the database (Drop Column).
-```
-
-### 3.3 Adding Constraints Safely
-To prevent table locks when adding `CHECK` or `FOREIGN KEY` constraints to large tables:
-1.  Add the constraint as `NOT VALID` (bypasses scanning legacy data, returns immediately).
-2.  Then, validate the constraint in the background by running the `VALIDATE CONSTRAINT` command concurrently.
-
----
-
-## 🕵️ 4. AUTOMATED QA GATE CHECKLIST
-
-`@analyst` scans the database schema and queries automatically during code review against these rules:
-*   [ ] For every new `table.foreign()` definition, is a corresponding `createIndex()` defined?
-*   [ ] Is `.forUpdate()` used in any `selectFrom` query without `.skipLocked()` or `.noWait()` written next to it?
-*   [ ] Is there any `alterTable().renameColumn()` or direct destructive `dropColumn()` in migration files? (Expand/Contract audit).
-*   [ ] Is `CONCURRENTLY` used in index additions on large tables?