Agent Directive: Global ERO Naming Enforcement

Objective

Perform a repository-wide validation and refactor to enforce the final Event Route Optimiser naming conventions. All legacy references (ClashRoute, ClashRouteOptimiser, CPRO, CFRO) must be eradicated.

Naming Standards Matrix

The agent must apply the following exact string formats based on the context:

• kebab-case: event-route-optimiser (Used for package.json names, Wrangler names, repository URLs, directory paths).
• lowercase alias: ero (Used for short identifiers, CLI commands, prefixes like ero-edge).
• PascalCase: EventRouteOptimiser (Used for the Azure DevOps ADO_PROJECT_NAME, TypeScript interfaces, or database names).
• UPPERCASE: ERO (Used for UI display text, README titles, and documentation headers).
• UPPER_SNAKE_CASE Prefix: SKNX_ERO_ (Strictly used as the prefix for all environment variables in settings files, excluding Terraform's native CLOUDFLARE_API_TOKEN).

Execution Sequence

1. Scrub Configuration Files

• Read api/package.json and app/package.json. Ensure "name" is "event-route-optimiser-api" and "event-route-optimiser-app" respectively.
• Read api/wrangler.toml. Ensure the name is "event-route-optimiser-edge".

2. Scrub Settings Directory

• Read settings/.env.local and settings/.dev.vars.
• Verify that all custom environment variables use the SKNX_ERO_ prefix (e.g., SKNX_ERO_ADO_PROJECT_NAME="EventRouteOptimiser").

3. Scrub Master Documentation

• Read README.md and SYSTEM_BUILDER.md.
• Ensure all titles read ERO (Event Route Optimiser).
• Ensure all terminal instructions reference the event-route-optimiser directory.

4. Scrub Execution Reports & Artefacts

• Scan the docs/ folder. Replace any lingering instances of ClashRoute, CPRO, or CFRO in the text with ERO or Event Route Optimiser.

5. Update System Builder Index

• Add docs/17-enforce-ero-naming-standard.md to the Artefact Index in SYSTEM_BUILDER.md.
• Append this execution step to the end of Phase 0.