OpIcon

A manufacturing-operation icon. It takes the drawing from the operation library, the ink from the process category and the key from the database — it invents nothing.

When to use it

You are showing an operation the process has stored in icon_key — in the cart, on a process card, in a technology overview.
The icon sits next to the operation name. That is its normal shape; on its own it is shorthand, not a label.

When not to use it

It is an interface icon — upload, search, trash. IngotIcon.
An opdot, the category colour dot, is already showing next to it. The dot and the icon say the same thing and contradict each other side by side — pick one.
You would build the key from the operation name or slug. The admin picks the icon by hand; there is no slug→icon matching in this repo and guessing one shows the wrong technology.
Your technology is missing. Add an icon to the operation library — never an emoji.

Properties

token: string | null | undefined — The stored icon_key, shaped <key>, <key>:black or <key>:white. Opaque to the backend — do not translate or compose it. An unknown token renders null so the caller can fall back.
size: number — Square edge in px, default 20. The operation set is set at 18–22 — it is denser than the interface set and falls apart smaller.
categoryColor: string | null — The process's operation_category_color. Applies only to the suffix-less variant; :black and :white carry their own ink.
title: string — The operation name for a screen reader. Only for a width-critical row where the icon has no visible label.
className: string — Extra classes on the wrapper. No border or tile here — chrome belongs to the caller.
testId: string — data-testid of the element.