PURPOSE

A vestigial placeholder screen. The legacy planet-boss test runtime has been removed and replaced by the boss-as-enemies system in engine/boss/encounter.ts. This component now renders a static notice card directing developers to the ship playground or to __dev.sandboxSpawnBoss(id, tier) for testing individual encounters.

OWNS

  • A single default-exported React function component, BossTestScreen.
  • Inline-styled DOM markup: a full-viewport container with a centered card containing a title (Legacy Boss Test Removed) and a body paragraph pointing at the new path.
  • No state, no refs, no effects.

READS FROM

  • Nothing. The component takes no props and reads no stores, contexts, or modules. The only import is React.

PUSHES TO

  • Nothing. No store mutations, no events, no navigation, no telemetry, no side effects.

DOES NOT

  • Does not spawn a boss, mount any engine, or wire any canvas.
  • Does not handle input, routing, or lifecycle events.
  • Does not invoke __dev.sandboxSpawnBoss itself — it only mentions the helper in copy.
  • Does not load assets or styles from external files (styling is fully inline).
  • Does not reference the metagame shell, Zustand stores, or any engine module.

Signals

None. The component is fully static and emits no signals.

Entry points

  • Default export: BossTestScreen (React function component).
  • Imported by whatever route still references the legacy /boss-test slot in the metagame shell. The file itself defines no routing.

Pattern notes

  • This is a tombstone component — a minimal UI left behind after removing a feature, kept so existing routes/links do not 404 and so a human landing here is redirected to the replacement workflow.
  • All styling is inline (style={{ ... }}) rather than via a stylesheet or Tailwind utilities. Colors and radii are hard-coded magic values, which is acceptable for a deprecation placeholder but would not be appropriate for live UI.
  • The body copy references runtime symbols (engine/boss/encounter.ts, __dev.sandboxSpawnBoss) directly so a developer who lands on the screen knows where the live boss system now lives.
  • Safe to delete once all callers of the legacy route are removed.