# Agents Update Summary - Translate Press Zone

## Updated: 2026-01-16

This document summarizes the changes made to adapt the agentic layer from the Comments Press Zone plugin to the Translate Press Zone plugin.

## Changes Made

### 1. Core Agent Updates

#### admin-panel-expert.md
- Changed plugin name from "Comments Press Zone" to "Translate Press Zone"
- Updated primary files to include WPML integration classes:
  - `includes/class-tpz-service-registrar.php`
  - `includes/class-tpz-job-sender.php`
  - `includes/class-tpz-job-receiver.php`
- Updated namespace from `presszone-comments/v1` to `translate-press-zone/v1`
- Updated all CSS/JS naming conventions from `presszone-comments-*` to `translate-presszone-*`

#### database-expert.md
- Changed plugin name to "Translate Press Zone"
- Updated table prefix from `presszone_comments_*` to `presszone_translate_*`
- Updated primary files to focus on translation job storage
- Removed comment-specific query references

#### frontend-js-expert.md
- Changed plugin name to "Translate Press Zone"
- Updated primary files to include admin panel JavaScript
- Removed comment-specific components (Editor, Modal, Confetti, EmojiPicker)

#### frontend-php-expert.md
- Changed plugin name to "Translate Press Zone"
- Updated namespace from `PresszoneComments` to `TranslatePresszone`
- Updated text domain to `'translate-press-zone'`
- Changed focus from comment templates to WPML connector
- Updated primary files to WPML integration classes

#### frontend-styling-expert.md
- Changed plugin name to "Translate Press Zone"
- Added admin panel styles reference

### 2. Renamed Agents

#### engagement-expert.md → api-integration-expert.md
- Completely rewritten for API integration focus
- Changed from voting/reporting to translation API communication
- Updated to handle WPML hooks and job management
- New namespace: `TranslatePresszone`
- New API endpoint: `https://api.translate.press.zone/v1/`

#### moderation-expert.md → settings-expert.md
- Completely rewritten for settings management
- Changed from moderation to API key validation and model selection
- Updated storage to use WordPress Options: `presszone_translate_api_key`, `presszone_translate_model_tier`, `presszone_translate_tone`
- New namespace: `TranslatePresszone`

### 3. Orchestrator Updates

#### orchestrator.md
- Updated sub-agent roster to reflect new agents
- Removed: `moderation-expert`, `engagement-expert`
- Added: `settings-expert`, `api-integration-expert`
- Updated domain detection rules for translation-specific keywords

#### gemini-orchestrator.md
- Updated available agents list
- Changed agent commands to match new agent names
- Updated workflow examples to translation-specific scenarios

### 4. Documentation Updates

#### create-wordpress-readme.md
- Updated plugin name examples to "Translate Press Zone"
- Changed keyword focus from comments to translation
- Updated pricing examples to reflect translation costs ($0.50/1M tokens)
- Changed tags from comment-related to translation-related
- Updated emojis to translation-appropriate ones (🌐, 🚀, 💰)

#### plugin-reviewer.md
- Updated approved prefixes to `translate_presszone_`, `translatepresszone_` (4+ characters required)
- **REMOVED** `tpz_` as it violates the 4-character minimum rule
- Changed text domain to `'translate-press-zone'`
- Updated database option examples to `translate_presszone_api_key`

### 5. Users & Permissions

#### users-permissions-expert.md
- Changed plugin name to "Translate Press Zone"
- Updated API namespace to `translate-press-zone/v1`
- Removed moderation-specific capability checks
- Added WPML integration permissions reference

## Agents Not Modified

The following agents remain generic and don't require plugin-specific updates:
- `ui-designer.md` - Generic UI design agent
- `ux-researcher.md` - Generic UX research agent
- `visual-storyteller.md` - Generic storytelling agent
- `whimsy-injector.md` - Generic whimsy agent
- `wordpress-security.md` - Generic WordPress security agent
- `wordpress-plugin-security-audit.md` - Generic security audit agent
- `vulnerabilities.json` - Generic vulnerability database

## Key Naming Conventions (WordPress.org Compliant)

### PHP
- Namespace: `TranslatePresszone`
- Function/Variable Prefix: `presszone_translate_`
- Text Domain: `'translate-press-zone'`

### JavaScript
- Global: `window.translatePresszoneAdmin`
- Classes: `TranslatePresszoneApp`

### CSS/SCSS
- Prefix: `translate-presszone-*`
- Variables: `$translate-presszone-*`

### Database
- Table Prefix: `{$wpdb->prefix}presszone_translate_*`
- Options: `presszone_translate_api_key`, `presszone_translate_model_tier`, `presszone_translate_tone`

### REST API
- Namespace: `translate-press-zone/v1`

## WordPress.org Compliance Notes

**CRITICAL:** All prefixes must be 4+ characters to pass WordPress.org review:
- ✅ `presszone_translate_` (19 characters)
- ✅ `presszone_comments_` (18 characters)
- ❌ `tpz_` (3 characters - FORBIDDEN)
- ❌ `tp_` (2 characters - FORBIDDEN)

## Plugin Focus Areas

The updated agents now focus on:
1. WPML integration and service registration
2. Translation API communication
3. Job management (sending/receiving translations)
4. Settings management (API keys, model selection)
5. Admin panel for configuration
6. WordPress.org compliance for translation plugins