build-game-map-editor

Derive a versioned editor document from production placements, render a paused director scene reusing the production world builder, and add selection, drag-and-snap, and inspector controls. Keep drafts isolated and export validated JSON proposals rather than mutating gameplay data.

Treat the editor document as an isolated draft stored locally, and export it only as a validated proposal. Integration happens through a separate reviewed workflow that maps changes back to authoritative source, runs tests, and releases normally.

Render the route dynamically with noindex, fail closed when configuration is missing, apply an exact IP allowlist from the trusted edge header, and issue short-lived HMAC-signed sessions bound to the client IP in a secure HTTP-only cookie.

Require an exact schema and version, cap document size and entity counts, reject duplicate IDs, non-finite values, unknown kinds, and out-of-range coordinates. For flat-world games, enforce Y equals zero and require the imported entity manifest to match production.

Yes, the inspector can expose settings with clear gameplay contracts such as aggro radius, target-loss timing, patrol modes, waypoints, and leash bounds, with world-space overlays. Source-owned settings stay read-only unless a validated write-back path exists.