Add Main Street Tutorial scenario, non-interactive overlays, smoke test, and fix build

[Copilot]

Implements the "Scenario: Tutorial" Game Selector entry for Main Street with non-interactive tutorial overlays, a deterministic headless smoke test, and fixes a pre-existing build failure.

New files

• MainStreetTutorialScene — subclass of MainStreetScene with scene key 'MainStreetTutorialScene', Easy difficulty hardcoded, auto-shows tutorial overlays on first load, adds [?] Tutorial HUD toggle button
• MainStreetTutorialOverlayManager — 7-step non-interactive overlay sequence (Welcome → Market → Incidents → Street Grid → Hand → Action Controls → Scoring). Each step renders a green highlight rect around the relevant UI region + a tooltip with Prev/Next/Dismiss navigation. Never blocks gameplay input.
• tests/main-street/smoke-scenario.test.ts — 8 headless unit tests using canonical seed "smoke-1": run completion, required summary fields, determinism, Easy-difficulty baseline, and 4 regression seeds

Modified files

• MainStreetScene constructor now accepts Partial<Phaser.Types.Scenes.SettingsConfig> so subclasses can supply a different Phaser scene key without forking the class
• main.ts — registers MainStreetTutorialScene and adds "Scenario: Tutorial" Game Selector entry
• docs/main-street/playtest-scenarios.md — adds Scenario 0 "Tutorial Smoke" documenting the smoke-1 seed, expected outcome, and a guide for authoring/updating tutorial copy
• README.md — adds Tutorial scenario to the example games table and smoke test commands

Build fix

Removed two unused imports (highestUnlockedTier, CARD_TEMPLATE_NAMES) in tests/main-street/meta-progression.test.ts that were emitting TS6133 errors and causing npm run build to exit non-zero.

[SorraTheOrc]

@copilot the CI tests failed. Fix them

[Copilot]

@copilot the CI tests failed. Fix them

Fixed in commit 3d1ba81.

Root cause: refreshHud() was calling hudContainer.removeAll(true) on every game refresh, which destroyed the persistent HelpPanel.container and SettingsPanel.container that were added to hudContainer during scene creation. After the first refresh, container.parentContainer became undefined, so the assertion expect(helpParent).toBe(scene.hudContainer) failed and Vitest crashed with RangeError: Invalid string length trying to serialize the Phaser Container in the failure message.

The fix replaces removeAll(true) with a targeted loop that only destroys children tagged _hudTransient = true. The four transient HUD elements (background strip, coin/rep/score texts) are now tagged via a new typed markHudTransient<T>() helper. Persistent overlay objects (HelpPanel, SettingsPanel, buttons) are never tagged and therefore survive every HUD refresh.