Clarify technical-info docs and ship pending owner/color fixes.

Document that product specs need /technical-info for labels, auto-verify admin-created business owners, and expand category color presets with Farsi aliases.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/website-api/AI_PROMPT.md

@@ -27,6 +27,7 @@ You are building a **Meshkee business website (storefront)**. You must use the M
 5. Cell numbers are E.164 (`+98912...`).
 6. Do not call dashboard/CMS routes (`/businesses/.../products` write APIs, media upload, domain-admin, etc.).
 7. **Partner SMS** (`POST /public/sms/send`) is for external partner backends with an issued `X-Api-Key` only — not for normal storefront UI. See https://api.meshkee.com/docs/website/SMS.md
+8. **Technical details (labels + values):** Product/user-product detail responses may include `technicalValues` with **values only** (`fieldId` + `textValue` / `optionId` / `optionIds` — **no field labels**). To render a label→value specs table you **must** call the matching `.../technical-info` endpoint and join `form.fields[].id` ↔ `values[].fieldId`. Never invent a separate “variation fields” or “category fields” public route — those do not exist on the website API.
 
 ### Typical bootstrap sequence
 1. `GET /tenants/{domain}` → branding + `businessId` + `specialProductsSource` (`product` or `store_item`)
@@ -50,10 +51,28 @@ You are building a **Meshkee business website (storefront)**. You must use the M
 ### User products (customer listings)
 Public marketplace listings owned by customers — not catalog `products`.
 - `GET /tenants/{domain}/user-products` — list published (`name`/`q`, `categoryId`, `cityId`, `countryId`, `condition`, `promoted`, pagination)
-- `GET /tenants/{domain}/user-products/{slug}` — details + gallery
-- `GET /tenants/{domain}/user-products/{slug}/technical-info` — category form + values
+- `GET /tenants/{domain}/user-products/{slug}` — details + gallery (`technicalValues` = values only, no labels)
+- `GET /tenants/{domain}/user-products/{slug}/technical-info` — **required for specs UI**: `{ form: { fields: [{ id, label, key, type, ... }] }, values: [...] }`
 Use product categories from `GET /tenants/{domain}/categories?entityType=product` for filters. Creating/editing listings is customer-dashboard only (`/businesses/.../my-user-products`), not website-facing.
 
+### Technical details / specs table (catalog products + user products)
+**Do not** render only `technicalValues` from the detail endpoint — users will see bare values (e.g. `SAMP`, `1992`) with no labels.
+
+| Detail page | Specs endpoint (labels + values) |
+|-------------|----------------------------------|
+| `GET .../products/{slug}` or `.../products/by-id/{id}` | `GET .../products/{slug}/technical-info` or `.../products/by-id/{id}/technical-info` |
+| `GET .../user-products/{slug}` | `GET .../user-products/{slug}/technical-info` |
+
+**How to render:**
+1. Call `technical-info` (same slug/id as the detail page).
+2. For each `values[]` entry, find `form.fields` where `field.id === value.fieldId`.
+3. Show `field.label` (or localized label if the site uses FA/EN) next to the value (`textValue`, or resolve option labels from `field.options` when `optionId` / `optionIds` are set).
+4. Follow `form.fields` `sortOrder` for display order.
+5. If `form` is null/empty or `values` is empty, hide the technical section.
+
+**Wrong:** `GET .../product-category-variation-fields?categoryId=…` (does not exist → 404).  
+**Wrong:** expecting `fieldName` / `fieldNameFa` on each `technicalValues` item in the product detail response.
+
 ### Analytics (dashboard charts)
 Page views are recorded **automatically** when the website calls the normal public list/detail APIs (blogs, products, portfolios, videos, store-items, and homepage sliders). No extra website code is required for those.