PageHeader

The screen header: a title, a sentence under it, actions on the right. One home for the type spec, and it drags no router along.

When to use it

The screen has a title. That is nearly every screen — which is why this primitive owns a spec that would otherwise be copied around.
The title comes with actions (add, export, filter). actions aligns them right and lets them wrap when they do not fit.
The name comes with a state — a badge, a count, a label. That is titleAdornment, not text glued into the title.

When not to use it

It is a section heading inside a screen, not the screen's title. Use IngotSection; two <h1> elements break the outline a screen reader reads.
You need breadcrumbs. It deliberately cannot do them: breadcrumbs know about routing, and this module stays free of a router dependency. Compose them one level up — the trail above the header, the header from this primitive.

Properties

title: ReactNode — The screen title. Detail routes pass the record name, not the nav label.
description: ReactNode — One sentence: what the reader finds here.
actions: ReactNode — The right-aligned action cluster.
titleAdornment: ReactNode — A badge beside the title — state, count, label.
testId: string — data-testid of the header.