feat(ui): Phase 30 ship-class calculator with goal-seek and reach circles

Fuse the standalone ship-class designer (Phases 17/18) into a sidebar calculator: live mass/speed/attack/defence/bombing results, a planet build-rate readout, single-target goal-seek, a modernization-cost mode, and auto reach circles on the map for the selected planet.

pkg/calc becomes the single source for the new math (no mirroring): extract BombingPower from the engine model and the per-turn ship-production loop from controller.ProduceShip into pkg/calc (engine now delegates), and add inverse goal-seek solvers in pkg/calc/solve.go. Thin-bridge the combat, planet-build, and solver functions through ui/core/calc + ui/wasm and rebuild core.wasm.

Remove the standalone designer view/route; the ship-classes table and the view/bottom menus open the calculator via a shared request store.

Docs: rewrite ui/PLAN.md Phase 30, adjust Phase 34 (realistic forecast + CAP/COL ownership), add ui/docs/calculator-ux.md, extend calc-bridge.md, fix navigation.md; remove ui/CALCULATOR.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

ui/frontend/tests/galaxy-client.test.ts

@@ -25,6 +25,7 @@ import type {
 	RequestSigningFields,
 	ResponseSigningFields,
 } from "../src/platform/core/index";
+import { makeFakeCore } from "./fake-core";
 
 const FIXED_REQUEST_ID = "req-test-1";
 const FIXED_TIMESTAMP = 1_700_000_000_000n;
@@ -204,19 +205,13 @@ function mockCore(opts: MockCoreOptions): Core & {
 	verifyEvent: ReturnType<typeof vi.fn>;
 } {
 	return {
+		// `GalaxyClient` does not exercise the calc bridge, so the calc
+		// methods come from the shared fake; only the signing/verify
+		// methods need spies for the orchestration-order assertions.
+		...makeFakeCore(),
 		signRequest: vi.fn(opts.signRequestImpl),
 		verifyResponse: vi.fn(opts.verifyResponseImpl),
 		verifyEvent: vi.fn(() => true),
 		verifyPayloadHash: vi.fn(opts.verifyPayloadHashImpl),
-		// `GalaxyClient` does not exercise the Phase 18 calc bridge,
-		// so these stubs only need to satisfy the `Core` interface.
-		driveEffective: () => 0,
-		emptyMass: () => 0,
-		weaponsBlockMass: () => 0,
-		fullMass: () => 0,
-		speed: () => 0,
-		cargoCapacity: () => 0,
-		carryingMass: () => 0,
-		blockUpgradeCost: () => 0,
 	};
 }