(v1.0) LS Central hospitality API (1.0.0)

Read-only projection of the item lines of a KOT (Kitchen Order Ticket), replacing the line detail returned by the legacy GetKotStatus SOAP operation. Reached nested under the kots entity via $expand=kotLines, and independently via $filter=kotNo eq ''...'' on this entity set. Mutation is not available through this entity.

Exposes Kitchen Order Ticket (KOT) status data as a read-only OData v4 entity, replacing the legacy GetKotStatus SOAP operation for read scenarios. GetKotStatus (and the GetKotStatusUtils/GetKotStatusXML objects behind it) remain available unchanged for the duration of the coexistence window. This release is GET-only; no write verbs are exposed. Scope: this entity is NOT restaurant-scoped as an enforced filter - KOT data is inherently restaurant-owned (every KOT has a real Restaurant No.), but legacy GetKotStatus never applies that as a filter (it only checks that the passed store exists), so restaurantNo is deliberately not exposed here and consumers must not assume tenant/restaurant isolation from this endpoint; the separate GetKOTStatusAll legacy operation, which does filter by restaurant, is out of scope. statusMessage is computed per record at read time from the order''s hospitality type and matching service flow line; it is blank whenever the order, hospitality type, or matching service flow line cannot be resolved, or when that flow line''s Send LS Commerce Message is false - blank is a normal result, not an error. Lines are reached via kots({id})?$expand=kotLines (note: kotLines, the part''s entity set name - not "lines", the control name) and independently via the kotLines entity set with $filter=kotNo eq ''...''. Performance note: statusMessage costs up to three extra table reads per row, so an unfiltered GET kots over a large KOT table is expensive - filter by receiptNo or kotNo.