##############################
# SEARCH CATALOG FILE (TXT)
##############################
This file defines what the app can search for.
Each "record" becomes one dropdown option in the app.

------------------------------
SEPARATORS (DO NOT CHANGE)
------------------------------
- Record Separator:  @@@RECORD@@@
  Each time the app sees this, it starts a new catalog item (dropdown entry).

- Field Separator:   @@@FIELD@@@
  Each time the app sees this, it starts a new field inside the current record.

------------------------------
FIELDS (KEY=VALUE)
------------------------------
Required fields:
- ID=
  Unique identifier (no spaces recommended). Used internally.

- LABEL=
  Human-friendly name shown in the dropdown.

- SEARCH_TYPE=
  Either:
  - literal  -> normal text contains search (fast, simple)
  - regex    -> JavaScript regular expression search (powerful for patterns)

- CONTENT=
  The text or regex pattern to search for.

Recommended fields:
- DESCRIPTION=
  Longer explanation shown in the app on the right side when selected.
  Use it to explain what the search does, why it exists, and any caveats.

Optional fields:
- TAGS=
  Comma-separated tags for organization (not required; may be used later).

------------------------------
REGEX NOTES (if SEARCH_TYPE=regex)
------------------------------
- CONTENT must be a JavaScript RegExp pattern WITHOUT the surrounding /slashes/.
- The app automatically applies the "g" flag (find all matches).
- If case sensitivity is unchecked in the UI, the app also adds the "i" flag.

Example regex:
  <Payment\b[^>]*>

------------------------------
EXAMPLES START BELOW
##############################


@@@RECORD@@@
@@@FIELD@@@
ID=customer_id_validation
@@@FIELD@@@
LABEL=Customer ID validation rules
@@@FIELD@@@
SEARCH_TYPE=literal
@@@FIELD@@@
CONTENT=customerId must be a UUID
@@@FIELD@@@
DESCRIPTION=Finds documentation or error messages that mention the rule "customerId must be a UUID". Use this to locate where customer ID validation rules are defined or referenced.
@@@FIELD@@@
TAGS=validation,customer


@@@RECORD@@@
@@@FIELD@@@
ID=xml_payment_node
@@@FIELD@@@
LABEL=Payment XML Node
@@@FIELD@@@
SEARCH_TYPE=regex
@@@FIELD@@@
CONTENT=<Payment\b[^>]*>
@@@FIELD@@@
DESCRIPTION=Finds XML start tags for a Payment node, regardless of attributes. Useful in XML configs, message templates, and logs where a Payment element may appear with varying attributes.
@@@FIELD@@@
TAGS=xml,payment


@@@RECORD@@@
@@@FIELD@@@
ID=api_endpoint_v1_orders
@@@FIELD@@@
LABEL=API endpoint /v1/orders
@@@FIELD@@@
SEARCH_TYPE=literal
@@@FIELD@@@
CONTENT=/v1/orders
@@@FIELD@@@
DESCRIPTION=Finds references to the /v1/orders API endpoint across configs, documentation, test files, and application code stored as text. Useful for checking migrations or endpoint renames.
@@@FIELD@@@
TAGS=api,orders


@@@RECORD@@@
@@@FIELD@@@
ID=xml_status_attribute
@@@FIELD@@@
LABEL=XML attribute status="..."
@@@FIELD@@@
SEARCH_TYPE=regex
@@@FIELD@@@
CONTENT=\bstatus\s*=\s*"(?:active|inactive|pending)"
@@@FIELD@@@
DESCRIPTION=Finds XML attributes with status="active|inactive|pending" (with whitespace tolerance). Useful for locating status values in XML files where formatting varies.
@@@FIELD@@@
TAGS=xml,status