Rebuild the map chrome against the Star Citizen starmap

Until now this was built from memory — the reference site is blocked by this
environment's egress policy, so the resemblance was asserted rather than
checked. Five screenshots of the real thing arrived, and this is what
comparing against them changed.

Labels say what a thing is, not just what it is called. Every label is now
two lines: the name, then its type in smaller, wider-tracked, dimmer
capitals. This is the single most characteristic element of the reference
and it appears in every frame of it. It also settles a real ambiguity — in a
map that mixes scales, "Orion" is an arm, a nebula and a constellation, and
nothing about a bare name said which one a label pointed at.

For stars the type line distinguishes "System" from "Star", which is the one
thing it can say that the map could not otherwise show: which points are
somewhere you can actually go.

The system view had no body labels at all, where the reference labels every
planet. It does now, which turned out to need two supporting changes. The
overlay had only ever added and removed labels, never moved them, because
stars do not move; planets do, so an existing label is now repositioned
rather than left where the body used to be. And the inner four planets
printed on top of each other in exactly the clump the star labels were
already spread to avoid — so that logic is now shared rather than
duplicated, with system bodies ordered outermost-first. Closing in reverses
it by itself: the outer orbits leave the frame, their labels drop, and the
inner planets take the space.

The chrome follows the reference's layout. The scale ladder is a row of
chamfered tabs at the top left rather than a vertical list of diamonds at
the middle left, and a nameplate across the top centre says what the view is
holding. The centre reticle is a hexagon, which is how the reference locks
onto a body, and stays distinct from the rectangular panel chrome.

Not copied: the ARK/RSI logos, wordmarks, and the bottom-right tool tabs.
The first two are someone else's brand, and the third would be four tabs
opening features this app does not have.

Two e2e assertions moved off bare text matches onto the readout panel's own
title. The nameplate names the same thing the panel does, so "is 'Local
Stars' on screen" became ambiguous — the assertion, not the design, was what
had to give.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WaySiNst4HhDXBHnMy8p5G

e2e/galaxy-view.spec.ts

@@ -12,7 +12,9 @@ test.describe('Galaxy view', () => {
     await expect(page.getByTestId('scene-canvas')).toBeVisible();
     await expect(page.getByPlaceholder('Search stars, planets, exoplanets…')).toBeVisible();
     await expect(backButtonLocator(page)).toHaveCount(0);
-    await expect(page.getByText('Local Stars')).toBeVisible();
+    // The readout panel's own title, not just the text anywhere on screen: the selected-object
+    // banner across the top names the same thing, so a bare text match is ambiguous.
+    await expect(page.getByTestId('hud-title')).toHaveText('Local Stars');
   });
 
   test('the scale ladder flies out to the whole Galaxy and back to the solar neighbourhood', async ({ page }) => {
@@ -32,6 +34,6 @@ test.describe('Galaxy view', () => {
     await expect(page.getByRole('button', { name: 'Milky Way' })).toHaveCount(0);
 
     await page.getByRole('button', { name: 'Solar Neighbourhood' }).click();
-    await expect(page.getByText('Local Stars')).toBeVisible({ timeout: 15_000 });
+    await expect(page.getByTestId('hud-title')).toHaveText('Local Stars', { timeout: 15_000 });
   });
 });