Mirror run 4 on Azure DevOps under a new Feature

Question

How does this map appear on the client's board?

Why it exists

The client has no GitHub access and the daily runs off Azure DevOps. Run 3 mirrored its map under Feature
42975; this map needs the same, and not under 42975, which is run 3's Feature and would never close
if run 4 hung off it.

What resolving this produces

• A new Feature under the Consumer's area path dxp\DXP - ZRH\DS - Design System.
• One User Story per ticket on this map that is real work, carrying title, a link to its GitHub issue,
  points and state — never a copy of the body. Nothing is duplicated, so nothing can drift.
• A table in this map's § Notes mapping each GitHub ticket to its ADO id, which is the only place the
  edge exists.

What does not move

Tasks 43100, 43101 and 43102 stay where they are, under 43039 and 43037. They are Consumer work, and two
of them belong to #495, which this map rules out
of scope. 43036 is #439's existing mirror under
42975 — decide whether it moves to the new Feature or stays, and record which.

The residue, which is not a defect

No tracker expresses the GitHub-to-ADO edge. It is hand-maintained, and a wayfinder group shrinks that
prose residue without removing it. Two other cross-tracker edges already survive only as prose
(#446, #449).

Not decided

• Whether the eight fix tickets each get a User Story, or one Story covers the six preconditions. Run 3
  gave each real-work ticket its own, with points estimated when the shape was known.
• Who estimates the points, and when. Run 3 raised two estimates after their grillings closed.

Start by reviewing Run 3's Azure DevOps Feature 42975 and the linked issues #495 and #439, then check the cross-tracker notes in #446 and #449. Done means creating a separate Feature under the specified area path, mirroring each in-scope real-work ticket as a User Story, and recording every GitHub-to-ADO mapping in this map's Notes, with the unresolved story grouping and estimation decisions documented.