Task: Draw the tile glyphs from the icon reference and label the home runs

The tile glyphs were drawn from a second icon set while the application already has one: the Fluent assets behind ui/Icon.tsx, with an icon reference that every concept is supposed to be added to before a screen uses it. Draw them from the reference instead, and label the home screen's runs the way the review did, so the places a person can go and the places that are coming are two runs and not one grid.

• The tiles draw their glyphs from ui/Icon.tsx, and no second icon set is a dependency.
• The home screen carries an Active Modules run and an Upcoming Modules / Roadmap Preview run, each under its own rule.
• The web check passes.

Look for the icon set before importing one. The application has a reference with 68 assets and a rule that says a concept is added to it before a screen uses it, and the review drew with a different set. The work is to map the concepts the tiles need onto the ones the reference already carries, which is twenty-three, and to add nothing.

The run labels are the review's own words, so they are strings the review already settled rather than ones to invent.

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

The tiles draw from the reference, there is one icon set, and the home screen carries the two labelled runs the review drew.

The glyphs came from the review's set first, and that was wrong. The application already has an icon system with a written rule — a concept goes into ui/Icon.tsx and into the icon reference before a screen uses it — and importing a second set quietly broke it. The correction cost less than the mistake: every concept the tiles needed already had an asset and a reference entry, so nothing was added and one dependency came out.

The footer arrow the review drew is not carried over. There is no right arrow in the reference, and the guidelines say an icon that loses no meaning when removed should be removed: the whole tile is the link, and the hover already says so.

The two runs are separated by the rule the review used, so a screen with tiles above and below it reads as two runs and not as one grid with a stray line through it.