chore: rename cameleer3 to cameleer

Rename Java packages from com.cameleer3 to com.cameleer, module
directories from cameleer3-* to cameleer-*, and all references
throughout workflows, Dockerfiles, docs, migrations, and pom.xml.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/superpowers/specs/2026-03-26-taps-attributes-replay-ui-design.md

@@ -2,9 +2,9 @@
 
 ## Context
 
-The Cameleer3 agent now supports camel-native data extraction taps, business attributes on executions, enhanced replay with editable payloads, per-route recording toggles, and success compression. The agent-side implementation is deployed and live.
+The Cameleer agent now supports camel-native data extraction taps, business attributes on executions, enhanced replay with editable payloads, per-route recording toggles, and success compression. The agent-side implementation is deployed and live.
 
-The shared models (`TapDefinition`, extended `ApplicationConfig` with `taps`, `tapVersion`, `routeRecording`, `compressSuccess`) exist in `cameleer3-common` (agent repo). The server already depends on this library and persists `ApplicationConfig` as JSONB in the `application_config` table. However, the server-side execution DTOs (`ExecutionDetail`, `ExecutionSummary`, `ProcessorNode`) do not yet carry `attributes` fields, and the `CommandType` enum lacks `TEST_EXPRESSION`.
+The shared models (`TapDefinition`, extended `ApplicationConfig` with `taps`, `tapVersion`, `routeRecording`, `compressSuccess`) exist in `cameleer-common` (agent repo). The server already depends on this library and persists `ApplicationConfig` as JSONB in the `application_config` table. However, the server-side execution DTOs (`ExecutionDetail`, `ExecutionSummary`, `ProcessorNode`) do not yet carry `attributes` fields, and the `CommandType` enum lacks `TEST_EXPRESSION`.
 
 This spec covers all UI surfaces and the backend changes needed to support them.
 
@@ -24,7 +24,7 @@ This spec covers all UI surfaces and the backend changes needed to support them.
 
 Before UI work can begin, the following backend changes are required:
 
-1. **Update `cameleer3-common` dependency** — ensure the server pulls a version that includes `TapDefinition`, and `ApplicationConfig` with `taps`, `tapVersion`, `routeRecording`, `compressSuccess` fields.
+1. **Update `cameleer-common` dependency** — ensure the server pulls a version that includes `TapDefinition`, and `ApplicationConfig` with `taps`, `tapVersion`, `routeRecording`, `compressSuccess` fields.
 2. **Add `attributes` to execution DTOs** — `ExecutionDetail`, `ProcessorNode`, and `ExecutionSummary` need a `Map<String, String> attributes` field. This requires changes to the PostgreSQL ingestion pipeline (store attributes from agent-submitted `RouteExecution`/`ProcessorExecution`), the detail service (reconstruct attributes), and the OpenSearch indexing (index attributes for search results).
 3. **Add `TEST_EXPRESSION` to `CommandType`** enum.
 4. **Enhance `CommandAckRequest`** — add an optional `data` field (`String`, JSON) to carry structured results (currently only `status` + `message`). The test-expression endpoint needs the result value from the ACK.
@@ -228,12 +228,12 @@ No new components required. Uses existing: Modal, DataTable, Badge, Toggle, Sele
 - `pages/Admin/AppConfigDetailPage.tsx` — restructure to 3 sections, traces & taps merged table, route recording table, compress success badge
 - `pages/Admin/AppConfigDetailPage.module.css` — updated section styles
 
-### Backend (cameleer3-server-app/)
+### Backend (cameleer-server-app/)
 - `controller/ApplicationConfigController.java` — add test-expression endpoint
 - `dto/CommandAckRequest.java` — add optional `data` field
 - `controller/AgentCommandController.java` — support CompletableFuture-based ACK for test-expression
 
-### Backend (cameleer3-server-core/)
+### Backend (cameleer-server-core/)
 - `agent/CommandType.java` — add TEST_EXPRESSION
 - `detail/ExecutionDetail.java` — add attributes field
 - `detail/ProcessorNode.java` — add attributes field