fix: use category name instead of uuid generated by llm (CM-889)

[ulemons]

PR: Stricter prompt + double validation for category UUIDs

Summary

This PR hardens LLM category selection by:

• Increasing prompt rigidity to reduce category/id drift.
• Applying a double validation step to ensure the returned UUID is both well-formed and present in the DB.
• Falling back to DB-backed resolution using the category name when the UUID is missing/invalid/not found.

What changed

• Prompt

  • Reinforced “closed set” constraints: categories must be copied verbatim from the authoritative JSON list.
  • Added stricter self-check requirements to minimize mismatches.

• Post-processing / Validation

  • Step 1: Accept category only if id matches UUID format and exists in categories (DB list).
  • Step 2: If id fails (missing/invalid/not in DB), try resolving by name (case-insensitive) and use the DB id.
  • Step 3: If neither id nor name resolves to a DB category, skip the entry and warn.

Why

LLM outputs can return:

• Correct names but wrong UUIDs
• Correct UUID format that doesn’t exist in DB
• New/modified category names or invented IDs

This ensures output is always DB-consistent, prevents silent data corruption, and keeps categorization within the authoritative category set.

---

Note

Medium Risk
Moderate risk because it changes production categorization behavior and introduces filtering/correction logic that could drop or alter LLM-selected categories if matching fails.

Overview
Tightens the LLM category-classification flow by switching the category list in the prompt from grouped text to an authoritative closed-set JSON array and adding strict output constraints/self-check instructions to reduce name/id drift.

Adds post-processing in findCategoriesWithLLM to handle null LLM responses and to ensure returned category IDs are DB-consistent: accept only IDs that are valid UUIDs and exist in the fetched category list, otherwise resolve by case-insensitive name and replace with the DB UUID, skipping unknown categories with warnings.

^{Written by Cursor Bugbot for commit 0f8d57e. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.