Run request analysis on demand on the VPS

docs/kb/systems/launcher-home.md

@@ -0,0 +1,42 @@
+# Launcher Home
+
+## What It Does
+
+The launcher is the public-facing entry point for Worldshaper. It presents the hero card, opens the editor in its own floating window, links to the repo, and hosts the News and Requests tabs.
+
+## Key Files
+
+- `src/WorldshaperLauncher.tsx`
+- `src/index.css`
+- `src/worldshaperStudio/windowing.ts`
+
+## Endpoints It Uses
+
+- `GET /api/world-default`
+- `GET /api/launcher-requests`
+
+## Important State
+
+- launch state: ready, opening, opened, blocked, error
+- active board tab: news or requests
+- request list, filters, and expanded request rows
+- resolved default world id
+
+## Invariants And Constraints
+
+- The editor is intended to open in a separate popup-style window.
+- The launcher should still work if the default world lookup fails by falling back to `overworld`.
+- Browser popup blocking is a real failure mode and must be surfaced to the user.
+
+## Common Request Themes
+
+- page styling and presentation
+- launch flow and popup behavior
+- repo button or external links
+- tab layout and launcher information architecture
+
+## Triage Questions
+
+- Is this about the launcher page itself, or the studio window after launch?
+- Does it affect only presentation, or also request API behavior?
+- Does it depend on popup/window behavior?