docs: remove cursorrules file and refocus workstation guide explicitly on agy

.cursorrules

@@ -1,17 +0,0 @@
-# Custom Rules for AI Agents (Antigravity, Claude, Cursor)
-
-# 1. Styling Guidelines
-- Only write Vanilla CSS. Do not use TailwindCSS or utility libraries unless specifically asked.
-- Put styling in Component-level CSS Modules (`*.module.css`) and import it locally (e.g. `import styles from './Button.module.css'`).
-- Always use variables from [globals.css](file:///home/gabogg/Proyects/semillero-special-hotel/styles/globals.css) for spacing, colors, fonts, border radii, shadows, and animations.
-- Implement smooth hover transitions and card lifts for interactive states (micro-animations).
-
-# 2. Architecture & decoupled design
-- Next.js acts as the user interface and database state layer.
-- Offload heavy operations, calculations, scheduling, and LLM evaluations to the external **n8n** engine by invoking webhook endpoints.
-- Ensure the application is decoupled: read all connection strings, URLs, and secrets from environment variables (`process.env.DATABASE_URL`, `process.env.N8N_WEBHOOK_URL`).
-
-# 3. Auditing & DB operations
-- Do not build custom audit logging tables or log triggers from scratch.
-- Use the `@explita/prisma-audit-log` Prisma Client Extension. Let it automatically intercept database modifications and log snapshots to the `AuditLog` table.
-- Always run `npx prisma generate` after modifying `schema.prisma`.

docs/AI_DEVELOPER_WORKSTATION.md

@@ -84,17 +84,17 @@ N8N_WEBHOOK_SECRET="prod_shared_signature_to_verify_n8n_callbacks"
 
 ---
 
-## 2. Optimizing the Workspace for AI Agents (Antigravity / agy)
+## 2. Optimizing the Workspace for the Antigravity Agent (agy)
 
-To make this codebase highly friendly for AI pair-programming, automated bug-fixing, and system changes, we recommend configuring the following Model Context Protocol (MCP) integrations.
+To make this codebase highly friendly for the **Antigravity agent (`agy`)**, you can configure the following Model Context Protocol (MCP) servers. Once registered in the agent's active configuration, `agy` is equipped to inspect database schemas, view live query states, and debug migrations during the development phase.
 
-### 2.1. Recommended MCP Servers
+### 2.1. Recommended MCP Servers for agy
 
 #### A. Prisma Postgres MCP Server (`@prisma/mcp`)
-Exposes tools allowing AI agents to interact directly with the database using type-safe schemas.
+Exposes tools allowing `agy` to interact with the database using type-safe schemas.
-* **Why use it**: Allows the AI agent to run natural language questions (e.g., "Show me the top 5 calculation rules in draft state" or "Run a dry-run check on the user goals schema").
+* **Use Case**: Allows `agy` to run schema checks, dry-run validations on schemas, and automatically inspect tables during development.
-* **Key capabilities exposed**: `ListDatabases`, `ExecuteSqlQuery`, `IntrospectSchema`, and `ExecuteRawSql`.
+* **Available Tools**: `ListDatabases`, `ExecuteSqlQuery`, `IntrospectSchema`, and `ExecuteRawSql`.
-* **Configuration snippet (`mcp.json`)**:
+* **Harness Registration**: Add this to the active MCP server list for the `agy` agent session:
   ```json
   "prisma-postgres": {
     "command": "npx",
@@ -106,9 +106,9 @@ Exposes tools allowing AI agents to interact directly with the database using ty
   ```
 
 #### B. PostgreSQL MCP Server (`@modelcontextprotocol/server-postgres`)
-Provides raw, high-performance database connectivity tools.
+Provides raw PostgreSQL connection and querying tools.
-* **Why use it**: Useful when running migrations or validating raw database logs directly through the AI chat context.
+* **Use Case**: Enables `agy` to query migration status, seed verification, and raw audit log verification directly.
-* **Configuration snippet (`mcp.json`)**:
+* **Harness Registration**:
   ```json
   "postgres": {
     "command": "npx",