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>

.planning/PROJECT.md

@@ -1,8 +1,8 @@
-# Cameleer3 Server
+# Cameleer Server
 
 ## What This Is
 
-An observability server that receives, stores, and serves Apache Camel route execution data from distributed Cameleer3 agents. Think njams Server (by Integration Matters) — but built incrementally, API-first, with a modern stack. Users can search through millions of recorded transactions by state, time, duration, full text, and correlate executions across multiple Camel instances. The server also pushes configuration, tracing controls, and ad-hoc commands to agents via SSE.
+An observability server that receives, stores, and serves Apache Camel route execution data from distributed Cameleer agents. Think njams Server (by Integration Matters) — but built incrementally, API-first, with a modern stack. Users can search through millions of recorded transactions by state, time, duration, full text, and correlate executions across multiple Camel instances. The server also pushes configuration, tracing controls, and ad-hoc commands to agents via SSE.
 
 ## Core Value
 
@@ -16,7 +16,7 @@ Users can reliably search and find any transaction across all connected Camel in
 
 ### Active
 
-- [ ] Receive and ingest transaction/activity data from Cameleer3 agents via HTTP POST
+- [ ] Receive and ingest transaction/activity data from Cameleer agents via HTTP POST
 - [ ] Store transactions in a high-volume, horizontally scalable data store with 30-day retention
 - [ ] Search transactions by state, execution date/time, duration, and full-text content
 - [ ] Correlate activities across multiple routes and Camel instances within a single transaction
@@ -38,8 +38,8 @@ Users can reliably search and find any transaction across all connected Camel in
 
 ## Context
 
-- **Agent side**: cameleer3 agent (`https://gitea.siegeln.net/cameleer/cameleer3`) is under active development; already supports creating diagrams and capturing executions
-- **Shared library**: `com.cameleer3:cameleer3-common` contains shared models and the graph API; protocol defined in `cameleer3-common/PROTOCOL.md`
+- **Agent side**: cameleer agent (`https://gitea.siegeln.net/cameleer/cameleer`) is under active development; already supports creating diagrams and capturing executions
+- **Shared library**: `com.cameleer:cameleer-common` contains shared models and the graph API; protocol defined in `cameleer-common/PROTOCOL.md`
 - **Data model**: Hierarchical — a **transaction** represents a message's full journey, containing **activities** per route execution. Transactions can span multiple Camel instances (e.g., route A calls route B on another instance via endpoint)
 - **Scale target**: Millions of transactions per day, 50+ connected agents, 30-day data retention
 - **Query pattern**: Incident-driven — mostly recent data queries, with deep historical dives during incidents
@@ -49,7 +49,7 @@ Users can reliably search and find any transaction across all connected Camel in
 ## Constraints
 
 - **Tech stack**: Java 17+, Spring Boot 3.4.3, Maven multi-module — already established
-- **Dependency**: Must consume `com.cameleer3:cameleer3-common` from Gitea Maven registry
+- **Dependency**: Must consume `com.cameleer:cameleer-common` from Gitea Maven registry
 - **Protocol**: Agent protocol is still evolving — server must adapt as it stabilizes
 - **Incremental delivery**: Build step by step; storage and search first, then layer features on top