ui/phase-14: rename planet end-to-end + order read-back

Wires the first end-to-end command through the full pipeline:
inspector rename action → local order draft → user.games.order
submit → optimistic overlay on map / inspector → server hydration
on cache miss via the new user.games.order.get message type.

Backend: GET /api/v1/user/games/{id}/orders forwards to engine
GET /api/v1/order. Gateway parses the engine PUT response into the
extended UserGamesOrderResponse FBS envelope and adds
executeUserGamesOrderGet for the read-back path. Frontend ports
ValidateTypeName to TS, lands the inline rename editor + Submit
button, and exposes a renderedReport context so consumers see the
overlay-applied snapshot.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

pkg/schema/fbs/README.md

@@ -2,8 +2,15 @@
 
 ## Generating sources
 
-Given a `.fbs` file, source code can be generated using `flatc` command:
+Given a `.fbs` file, source code can be generated using `flatc` from
+this directory:
 
 ```shell
-flatc --go {file}.fbs
+flatc --go --go-module-name galaxy/schema/fbs {file}.fbs
 ```
+
+The `--go-module-name` flag rewrites cross-namespace imports to the
+fully-qualified module path (e.g. `common "galaxy/schema/fbs/common"`)
+so the generated code links inside this Go module without local
+replace directives. Omitting the flag yields imports such as
+`common "common"` which fail to resolve.