Please address the comments from this code review:

## Overall Comments
- The HQL constants for bulk profiles mix entity field names and column names (e.g. `LOAD_ALL_ENABLED_BULK_PROFILES` and `DELETE_BULK_PROFILE_BY_NAME` use `profile_name` instead of the `KruizeBulkProfileEntry` field `profileName`), which will break the queries; they should consistently use entity property names in JPQL.
- The `BulkProfile.description` field is not mapped to `KruizeBulkProfileEntry` or the `kruize_bulk_profile` table, so descriptions will be silently dropped on persistence and reload; add a column and mapping if description is meant to round-trip.
- The DB migration defines `recommendation_settings JSONB NOT NULL`, but `BulkProfileService` does not validate that `recommendation_settings` is present and `KruizeBulkProfileEntry.fromBulkProfile` only sets it when non-null, so inserts/updates can violate the NOT NULL constraint; either relax the schema or enforce/normalize a non-null value in the service layer.

## Individual Comments

### Comment 1
<location path="src/main/java/com/autotune/analyzer/services/BulkProfileService.java" line_range="41-50" />
<code_context>
+        this.updatedAt = updatedAt;
+    }
+
+    /**
+     * Cluster configuration within a bulk profile
+     */
</code_context>
<issue_to_address>
**suggestion (typo):** REST path documentation does not match the registered servlet context

The Javadoc mentions `/bulkProfile`, but `ServerContext.BULK_PROFILE_SERVICE` is registered at `ROOT_CONTEXT + "bulkProfiles"` (plural). Please align the documented path with the actual servlet mapping.

Suggested implementation:

```java
 * REST path: {@code /bulkProfiles}

```

If the Javadoc mentions `/bulkProfile` in multiple places (e.g., examples, descriptions, or method-level documentation), apply the same string replacement there as well to ensure all documented paths consistently use `/bulkProfiles`, matching `ServerContext.BULK_PROFILE_SERVICE` at `ROOT_CONTEXT + "bulkProfiles"`.
</issue_to_address>