Land a rendering component on develop, so the client sees the walk's output

Rewritten 2026-09-03 by the #373 orchestrator. Four of this ticket's five original criteria
were met, twice, by runs 1 and 2; the fifth was not, and it is the one the client can see. The
original body — "Walk /specs → /tickets → /build once in DXP-DesignSystem and deliver the first
slices" — is in this issue's revision history. What follows is the remainder.

Question

Two full walks of the main line have run in DXP-DesignSystem. Neither left a component on
develop. Does a measurement run's output ever get merged, or does delivery need a pass of its own?

What is already done, and what is not

origin/develop carries three contract.generated.md / screenshot.generated.png pairs,
index.ts, lib/utils.ts and styles.css. No component source and no story. Both builds live
on branches abandoned on purpose — 5e683a7 and a71e19f — because a run's output is a measured
artefact, and fixing it would destroy the baseline the next run is compared against.

That reasoning is sound and it has now held for two runs. The consequence is that the deliverable and
the measurement are the same task, and only the measurement happens.

The decision this ticket makes

Whether a run's output is ever merged, and if not, what delivers instead. Two shapes, and this ticket
picks one:

• The run delivers. A run's branch is reviewed and merged like any other, and the baseline for
  the next comparison is a tag or a commit rather than the absence of code. Cheapest in effort;
  changes what every future run means.
• Delivery is its own pass. A separate slice, built from the run's output by hand or by a fresh
  /build, lands on develop. Keeps the runs clean; costs a build that the client already paid for
  once.

Acceptance criteria

• The decision above is recorded — which shape, and why the other was refused.
• origin/develop in DXP-DesignSystem carries at least one component source file and at least one
  story that the Storybook vitest project renders.
• The component is one the Figma profile-card page names, so the client recognises it.
• The five mechanism checks 43020–43024 act on it rather than passing vacuously: each check has
  something in the tree to inspect.
• Whatever baseline run 3 is compared against is named as a commit, not as "develop is empty".

Why this is still p0

It is the only criterion of the original ticket that a client can see, and after two runs it is the
oldest unmet promise on this map.

Start by reading the run findings and inspecting origin/develop plus branches 5e683a7 and a71e19f in DXP-DesignSystem. Decide how delivery relates to measurement, then use the existing index.ts, lib/utils.ts, styles.css, and generated artefacts as context. Done means develop has a Figma profile-card component and Storybook story, checks 43020–43024 inspect them, and run 3 names a commit baseline.