Archive & delete lifecycle surfaces

The row menu is Edit · Archive/Restore — no Delete (participant-label-row-actions.tsx). Durable references mean a label is retired by archiving, never destroyed.

The catalogue table gains a Where it is used column showing the split as two prose lines — recorded on matters (durable references) and attached to matter types (detachable options) — read straight from the generated list item (recordedOnMatters / attachedToMatterTypes), never computed client-side.

Both tabs use one column set (AC #4, per the design): Matter type · Participant labels (pills +N) · In use · Reference · kebab. The In-use badge carries the count (amber when in use), and an uncurated type shows a Not set — all labels badge.

participant-label-archive-dialog.tsx reads useAppGetParticipantLabelArchiveImpact to name every matter type that stops offering the label and flag any last client-side option (intake then falls back to the firm catalogue).

Restore is a direct, optimistic unarchive; the backend re-attaches the label everywhere it was offered and the exact counts reconcile on invalidate.

matter-type-catalog-delete-dialog.tsx lists the participant-label attachments that will be removed and states the labels themselves survive — only the attachment is removed.

The kebab’s disabled Delete drops its tooltip (matter-type-catalog-row-actions.tsx); the reason a type can’t be deleted is carried by the In use column.

useAppListParticipantLabels (where-used split), useAppGetParticipantLabelArchiveImpact (archive preview), useAppListMatterTypes, useAppListMatterTypeParticipantLabels (delete cascade).

useAppArchiveParticipantLabel, useAppUnarchiveParticipantLabel, useAppDeleteMatterType.

Archive-impact gains a browser→server proxy (…/participant-labels/[participantLabelId]/archive-impact/route.ts) and a gateway method that parses upstream JSON through participantLabelArchiveImpactResponseSchema (HR-21). Round-trip covered by archive-impact.test.ts.