Lookup Company Uid

What the register says about one UID — also the endpoint's wire shape.

One type rather than a client dataclass plus a response model: the endpoint is a pass-through, so a second shape would only be the first one retyped.

status:

• found — the register knows it; the remaining fields describe the entry.
• not_found — the query ran and matched nothing.
• invalid — the input does not read as a Swiss UID. Not an error: the column legitimately holds foreign VAT numbers, so the register simply has no opinion, and the UI renders nothing. No request is made.
• unavailable — transport failure, a non-200, or a body this cannot parse.

Only parsed fields are carried. The upstream body and its error text are logged (truncated) and dropped rather than returned — a caller is a tenant-facing endpoint, and there is no reason for a federal endpoint's response text to cross that boundary. It has to reach the log, though: a persistent unavailable is otherwise undiagnosable, and "the SPARQL no longer parses against a reshaped graph" and "the host is down" look identical from the outside.

⚠️ This docstring is published — it becomes the RegisterLookup schema description in openapi.json and the generated TS client's type docs. Keep it a statement about the wire contract; internal constant names do not belong in it.